Re:Teleport 4.3: Modern Replacement for OpenSSH
by lucb1e on Thursday July 09, 2020 @05:34PM
(#23785484)
> devices without public IPs (or a vpn) can connect to your bastion server
How does it punch through NAT? Or does the NATted device connect similarly to using ssh -R 1234:localhost:22 (just like CAs and session recording work with SSH as well, but I guess this project might make it more integrated and user-friendly with a nice GUI)?
Re:Teleport 4.3: Modern Replacement for OpenSSH
by cronos on Thursday July 09, 2020 @07:05PM
(#23786306)
The NATted device dials out to the bastion (a.k.a. proxy) and maintains a persistent tunnel.
The proxy then sends all the connections to this device inside that tunnel.
How does it punch through NAT? Or does the NATted device connect similarly to using ssh -R 1234:localhost:22 (just like CAs and session recording work with SSH as well, but I guess this project might make it more integrated and user-friendly with a nice GUI)?