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
Simple tunneling reverse proxy with a fast web UI and auto HTTPS. Designed for self-hosters.
38 Commits 31 Branches 14 Tags 682 KiB
Go 88.2%
Shell 10.6%
Dockerfile 1.2%
59c824bfca
Go to file
Anders Pitman 59c824bfca Start implementing custom ssh server 
Turns out SSH has robust semantics for opening generic channels.
Looks like I'll be able to set up tunnels without ever needing to
forward ports on the server, since I can connect the channels with
a custom protocol.

Of course I'll eventually want to support generic SSH clients, but
this makes starting much easier.
2020-10-01 17:22:54 -06:00
webui Implement add/delete tunnels from UI 2020-09-29 23:10:06 -06:00
admin_listener.go Run go fmt 2020-09-29 20:12:54 -06:00
auth.go Modify login for browser forms instead of API 2020-09-29 22:03:34 -06:00
boringproxy.go Start implementing custom ssh server 2020-10-01 17:22:54 -06:00
client.go Start implementing custom ssh server 2020-10-01 17:22:54 -06:00
go.mod Start implementing custom client 2020-09-30 23:49:03 -06:00
go.sum Start implementing custom client 2020-09-30 23:49:03 -06:00
main.go Start implementing custom client 2020-09-30 23:49:03 -06:00
README.md Remove SirTunnel stuff from readme 2020-09-29 15:53:10 -06:00
ssh_server.go Start implementing custom ssh server 2020-10-01 17:22:54 -06:00
todo.md Start implementing custom client 2020-09-30 23:49:03 -06:00
tunnel_manager.go Add error handling for cert failure 2020-09-29 23:24:22 -06:00
utils.go Run go fmt 2020-09-29 20:12:54 -06:00

README.md

What is it?

If you have a webserver running on one computer (say your development laptop), and you want to expose it securely (ie HTTPS) via a public URL, boringproxy allows you to easily do that.