chisel VS SOCKS5-proxy-actions

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

View on GitHub