hera VS chisel

The last thing I'll say is that I'm not thrilled with having to manually create a config file or run the curl API commands to create the necessary DNS records to facilitate all of this. I can live with it if I can get the above working since my stack is fairly static, but I think Traefik reverse proxy spoiled me in its use of labels to dynamically create rules and such. I also found a cloudflare blog post about creating tunnels via Terraform, which I could do since I use TF at work so it's good practice, but then I run into the fact that I'd still have to create all of the TF code to provision the DNS records and tunnels manually (somewhat shortcutted if I use a module) but then I still run into how to automate doing a plan and apply and creating the tunnels at the same time as running the containers. If anyone has any thoughts on how to dynamically build tunnels along with the rest of my container servers as a sort of all in one type package, that'd be sweet. I found this project, but it requires granting access to docker socket and I have specifically tried to go out of my way to avoid doing that for security reasons, plus it hasn't been updated in a few years so not actively maintained either.

chisel - SSH under the hood, but still uses a custom client binary. Supports auto certs from LetsEncrypt. Written in Go.

Looking at the perf https://github.com/jpillora/chisel/blob/master/test/bench/pe... it looks not too bad!

I have a few TCP based utilities. I was thinking I need to make websocket equivalents for it to work on the web, but happy to see this project, I will be evaluating this soon, it should save me some time.

Thanks for sharing!

Personally I use https://github.com/jpillora/chisel as a reverse Proxy through nginx, then connect through it using OpenVPN to bypass a similarly restrictive firewall. But this discussion is filled with other, similar hacks, I may have to try some of them.

To keep everything secure, each chisel client has a separate TLS private key. That lets my reverse proxy authenticate the client before allowing a connection to the Chisel backend service. And on the Chisel backend service side, the --auth= part allows that particular client to bind to the specific XXX port within that Docker container. https://github.com/jpillora/chisel/blob/master/example/users.json

I love it in the context of hacking actually. When working on HackTheBox machines or other CTFs you sometimes need to deploy tools onto the machine like these:

* https://github.com/jpillora/chisel

rclone and chisel. rclone is a high quality swiss-army knife for selfhosting. It does a lot of things and it does all of those things surprisingly well. chisel provides an TCP/UDP tunnel over websockets. When heroku used to be free, I had a couple of chisel instances running on Heroku, which I would use, occasionally, to quickly access any of my locally hosted apps or servers.

GitHub - jpillora/chisel: A fast TCP/UDP tunnel over HTTP

You should try Chisel https://github.com/jpillora/chisel