News for hackers. Stuff that matters.
Re:Show HN: Inlets – Expose your local endpoints to the Inte... by adnanh on Tuesday February 19, 2019 @04:38AM (#19197785)
Why wouldn't one use SSH tunnels instead of this/ngrok?
Re:Show HN: Inlets – Expose your local endpoints to the Inte... by nijave on Tuesday February 19, 2019 @08:52AM (#19198907)
There's this little gem that uses websocket tunnels for all those times only http is allowed. https://github.com/jpillora/chisel

A lot of modern websites rely on websockets for push notifications so they're usually open. It works wonderfully for things like public WiFi where all traffic is sent through an HTTP proxy and everything else blocked

Re:Show HN: Inlets – Expose your local endpoints to the Inte... by omegabravo on Tuesday February 19, 2019 @04:58AM (#19197872)
my glorious corporate firewall doesn't allow any traffic other than on ports 80,443
Re:Show HN: Inlets – Expose your local endpoints to the Inte... by adnanh on Tuesday February 19, 2019 @05:12AM (#19197931)
inbound, outbound, or both?
Re:Show HN: Inlets – Expose your local endpoints to the Inte... by omegabravo on Tuesday February 19, 2019 @05:27AM (#19197976)
only outbound connections permitted
Re:Show HN: Inlets – Expose your local endpoints to the Inte... by x0x0 on Tuesday February 19, 2019 @05:35AM (#19198000)
I'd ask for approval in writing from my boss to play this game. If received, you could perfectly well set up a $6 digital ocean box and ask sshd to listen to 443. Then...

   ssh -R 443:localhost:3000 -N my_remote-server
is a perfectly good outbound connection?

Obviously, you'll want some iptables on the remote end or for your local box not to have anything valuable on it, but it will let you test webhooks.

Re:Show HN: Inlets – Expose your local endpoints to the Inte... by wut42 on Tuesday February 19, 2019 @01:59PM (#19201721)
I run an sshd on 443 for this reason. Helped me bypass some corporate firewalls in the past, very useful when you go onsite.