inlets-archived VS chisel

This appears to be a very old version of the project before it was eventually forked to a repo that belonged to the inlets org on GitHub. That's why when Alex deleted the github.com/inlets/inlets-archived repo yesterday (a fork he controlled, where all the work since late 2018 was done), this repo under the-cc-dev now appears as the root repo of all the forks that exist right now, including my fork (https://github.com/mattwelke/inlets-archived).

Also if you're looking to self host something checkout inlets: https://docs.inlets.dev/#/

I've used Hamachi (vpn.net), that worked pretty well. You could also try Inlets (https://github.com/inlets/inlets).

Did you check https://github.com/inlets/inlets ? It’s an opensource alternative to cloudfared. Never use it myself but creator has a good track-record of developing nice oss solutions (were raspberry is usually first-class citizen)

I found some of them that are related to this topic, it might be useful for you too: * inlets * kt-connect * shuttle * ngrook

You could build something similar to HCM yourself. For instance you can use Inlets but you'd have to maintain the server yourself and pay for it. Plus, HCM is a breeze to set up and can be automated with the Azure CLI

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

Have a look at setting up this at home or cheap VPS on port 443, then tunnel using it. https://github.com/jpillora/chisel