Anders Pitman f39d9be54f Implement DNS record verification
Checks to make sure DNS indicates an A/AAAA record matching the
public IP address of the server before allowing the domain name
to be added.

Uses a random host to verify wildcard domains.

Might be more robust to actually communicate with the
authoritative servers, or check from multiple geo locations, but
this is probably fine for now and maybe forever.
2022-03-07 13:10:11 -07:00
2022-02-24 11:38:57 -07:00
2022-02-23 12:33:36 +02:00
2021-02-07 07:57:03 -05:00
2021-12-14 15:04:34 -07:00
2022-02-20 14:44:25 +02:00
2022-03-07 13:10:11 -07:00
2022-03-04 14:00:04 -07:00
2022-02-21 11:26:11 -07:00
2022-02-24 14:51:28 -07:00
2022-02-18 14:30:12 +02:00
2022-02-23 12:33:36 +02:00
2020-11-04 07:55:43 -07:00
2020-10-21 09:50:12 -06:00
2020-10-22 10:08:20 -06:00
2020-10-26 11:11:14 -06:00
2022-01-14 15:28:19 -07:00
2021-12-14 15:43:06 -07:00
2022-02-24 14:12:09 -07:00
2020-11-24 19:21:59 -07:00
2021-02-22 23:04:43 -07:00

boringproxy development is sponsored by TakingNames.io. boringproxy offers full integration with TakingNames.io, providing the simplest way to get up and running with your own domain. More information here, and a demo video of boringproxy working with TakingNames.io here.

Getting Help

If you run into problems running boringproxy, the best place to ask for help is over at the IndieBits community, where we have a dedicated section for boringproxy support. If you think you've found a bug, or want to discuss development, please open an issue.

What is boringproxy?

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.

NOTE: For information on downloading and running boringproxy, it's best to start on the website, boringproxy.io. The information in this README is just for building from source.

Building

git clone https://github.com/boringproxy/boringproxy
cd boringproxy

If you don't already have golang installed:

./install_go.sh
source $HOME/.bashrc

Make the logo image file. It gets baked into the executable so it needs to be available at build time. Note that you don't have to use the official logo for the build. Any PNG will do. It's currently just used for the favicon.

./scripts/generate_logo.sh
cd cmd/boringproxy
go build

To build with version information:

go build -ldflags "-X main.Version=$(git describe --tags)"

Give the executable permission to bind low ports (ie 80/443):

sudo setcap cap_net_bind_service=+ep boringproxy

Running

Server

./boringproxy server

Client

./boringproxy client -server bpdemo.brng.pro -token fKFIjefKDFLEFijKDFJKELJF -client-name demo-client -user demo-user
Description
Simple tunneling reverse proxy with a fast web UI and auto HTTPS. Designed for self-hosters.
Readme 640 KiB
Languages
Go 88.2%
Shell 10.6%
Dockerfile 1.2%