Teleport 4.3: Modern Replacement for OpenSSH

Re:Teleport 4.3: Modern Replacement for OpenSSH by mcpherrinm on Thursday July 09, 2020 @05:52PM (#23785668)

Just extra pieces to manage. With a VPN, now you need to start worrying about firewall rules (do you isolate clients? What internal resources do they get access to?), IP assignment (now you need to run a DHCP server, or handle static IP allocations). What subnets do you use for your VPN, and what happens if they conflict with the network at some of your locations? Or maybe buy a VPN appliance to do that for you. Then you need to handle VPN authentication...

Lots of that is largely un-needed effort. If you just want to be able to SSH into computers, it's simpler to just have your ssh server connect back.

At small scale, where an ops team can keep track of all the computers individually? yeah, VPN is probably fine, especially if you've already got one. But I think these days, a lot of people are looking at avoiding VPNs outright.

[ Parent | on HN ]

Re:Teleport 4.3: Modern Replacement for OpenSSH by jon-wood on Friday July 10, 2020 @06:59AM (#23790201)

These complications are particularly relevant if you're managing a fleet of devices on networks you don't control, such as on-prem versions of SaaS systems, or consumer IoT devices. In that situation you definitely don't want the device to be sitting around with a back door into your network, and subnet conflicts are often impossible to resolve.

[ Parent | on HN ]