Re:Show HN: Inlets 2.0 – expose your local endpoints to the ...
by alexellisuk on Thursday July 11, 2019 @12:03PM
(#20412611)
Ngrok is closed source, I do explain the differences in the post. Ngrok is also almost always banned..
Re:Show HN: Inlets 2.0 – expose your local endpoints to the ...
by pknopf on Thursday July 11, 2019 @12:54PM
(#20413148)
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.
Re:Show HN: Inlets 2.0 – expose your local endpoints to the ...
by kevin_nisbet on Thursday July 11, 2019 @02:40PM
(#20414182)
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.
Re:Show HN: Inlets 2.0 – expose your local endpoints to the ...
by iampims on Thursday July 11, 2019 @11:17AM
(#20412175)
Can you share more details about this? Sounds very interesting!
Re:Show HN: Inlets 2.0 – expose your local endpoints to the ...
by pknopf on Thursday July 11, 2019 @11:37AM
(#20412365)
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.
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.