IntenseWebs/boringproxy
3
0
Fork 0
mirror of https://github.com/boringproxy/boringproxy.git synced 2025-02-25 18:55:29 -06:00
Code Issues Packages Projects Releases Wiki Activity

Update notes and todo

Browse Source
This commit is contained in:
Anders Pitman 2020-10-18 10:48:23 -06:00
parent 44e3cc7d2c
commit 0df20b2e1e
2 changed files with 15 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
notes.md
View File

@ -8,15 +8,25 @@
setups. setups.
* libdns integration * libdns integration
* Add 3rd-party tokens for controlling DNS * Add 3rd-party tokens for controlling DNS
* Maybe add a DNS/Domains page and require users to add domains there before
they can use them for tunnels. This creates a natural place to explain what
is wrong when domain stuff breaks.
* Built-in static file hosting * Built-in static file hosting
* Client determines which directories are exposed * Client determines which directories are exposed
* Password-protected tunnels * Password-protected tunnels
* TCP tunnels
* Allow client to specify binding to addresses other than 127.0.0.1.
* IPv6
# Potential features # Potential features
* Built-in GemDrive * Built-in GemDrive
* Allows web UI to browse files on the clients * Allows web UI to browse files on the clients
* WireGuard hub
* Create tunnels by full URL; not just domains. Allows things like sharing
specific files and having multiple servers behind a single domain.
* Allow multiple upstreams for load balancing/HA.
# Tunnel variations # Tunnel variations

16
todo.md
View File

@ -1,16 +1,10 @@
* I don't think it's properly closing connections. Browser are hanging on
some requests, possibly because it's HTTP/1.1 and hitting the max concurrent
requests.
* Implement a custom SSH server in Go and connect the sockets directly?
* Use HTML redirects for showing errors then refreshing. Maybe for polling
after login and submitting a new tunnel too.
* Save next port in db
* On unknown page, redirect to referer if possible * On unknown page, redirect to referer if possible
* Properly pick unused ports for tunnels
* Apparently multiple tunnels can bind to a single server port. Looks like * Apparently multiple tunnels can bind to a single server port. Looks like
maybe only the first one is used to actually tunnel to the clients? maybe only the first one is used to actually tunnel to the clients?
* Maybe add a DNS/Domains page and require users to add domains their before
they can use them for tunnels. This creates a natural place to explain what
is wrong when domain stuff breaks.
* Responses to unauthorized requests are leaking information about the current * Responses to unauthorized requests are leaking information about the current
tunnels through the genereated CSS. tunnels through the genereated CSS.
* CSS-only delete buttons don't show up as targets for links like Vimium
* Wrapping labels in buttons and adding a bit of CSS seems to do the trick.
* Eh buttons aren't actually doing anything apparently (when hit by
keyboard).
* Set Cache-Control Max-Age