Hacker News Reader

Comment by Svoka | Hacker News Reader

Seems like https://ngrok.com/ with extra steps

Except ngrok supports ssh.

These projects really need to consider plain TCP connections. It's a deal breaker for me.

My company installs ngrok on our embedded devices. When there is an issue, they connect it to the internet, type a keystroke, and I'm in.

Ngrok is closed source, I do explain the differences in the post. Ngrok is also almost always banned..

I haven't run into a single hospital network where it is banned, so far.

You can also use ngrok1, which you can host yourself. It's got the features you'd need. This would get around firewalls.

For remote access, Teleport for IOT supports a similar use case using SSH, where an agent can be run on an embedded device, optionally or always enabled that phones home, and allows SSH connections to be reverse tunneled back to the device behind a firewall. https://gravitational.com/blog/iot_security_teleport/

Disclaimer: I work for gravitational but not on teleport.

Can you share more details about this? Sounds very interesting!

I have an X11 key listener. When someone reports a problem and they have access to the internet, I have them type "__medxremotedebug". An ngrok process is started, the machine beeps to notify the user that the backdoor is open. I then login to ngrok.com, see the tunnel and connect to it. All the units have a public ssh key and only I have the private key.

This has saved me and my customers so many times.

Bro. TMI

Hmm? He asked.

Or my personal favourite: http://localhost.run/

https://serveo.net is similar.

If it’s this simple to host an arbitrary TCP reverse proxy, why would inlets make it a “non-goal”?

Surprising that a site like this operates on http.

https://localhost.run/ works (and when you use their tunnel, both http and https work).

Or https://sshreach.me

Reply on news.ycombinator.com