IntenseWebs/boringproxy

mirror of https://github.com/boringproxy/boringproxy.git synced 2025-02-25 18:55:29 -06:00

Go to file

Anders Pitman 2ca7800ca6 Replace email login with direct token login

2020-10-11 15:18:33 -06:00

Replace email login with direct token login

2020-10-11 15:18:33 -06:00

api.go

Rename sessions to tokens/tokenData

2020-10-11 14:27:32 -06:00

auth.go

Replace email login with direct token login

2020-10-11 15:18:33 -06:00

boringproxy.go

Move web ui into separate struct and rename file

2020-10-11 13:45:46 -06:00

client.go

Move web ui into separate struct and rename file

2020-10-11 13:45:46 -06:00

database.go

Rename sessions to tokens/tokenData

2020-10-11 14:27:32 -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 remote-controlled clients

2020-10-09 10:05:31 -06:00

README.md

Remove SirTunnel stuff from readme

2020-09-29 15:53:10 -06:00

todo.md

Start implementing remote-controlled clients

2020-10-09 10:05:31 -06:00

tunnel_manager.go

Move web ui into separate struct and rename file

2020-10-11 13:45:46 -06:00

tunnel.sh

Start implementing remote-controlled clients

2020-10-09 10:05:31 -06:00

utils.go

Run go fmt

2020-09-29 20:12:54 -06:00

webui_handler.go

Replace email login with direct token login

2020-10-11 15:18:33 -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.