3 ms·
It's not clear to me that this really solves any of the UI and management problems associated with VPNs. I'm sure the new crypto-design is interesting, but exch
by XorNot 10y ago
It's not clear to me that this really solves any of the UI and management problems associated with VPNs. I'm sure the new crypto-design is interesting, but exchanging SSH public keys is actually a huge logistical hassle which scales very poorly.
The other thing is "container-ready" ... well it just isn't. I can use OpenVPN to do the same interface migration trick with a container today. That's not the challenge - the challenge is things like managing what happens when the VPN interface goes down and I need to recycle and reconfigure that interface (at which point you end up back at "allocate a private address space, stick the VPN container in a new address space, play with IPTables there to make sure losing the VPN routes doesn't mean you start routing over the regular NIC".
- baby 10y ago> but exchanging SSH public keys is actually a huge logistical hassle which scales very poorly. How do current solutions tackle this? It seems that at some point, if you want something to be two-way authenticated then you need to exchange some public keys.
- XorNot 10y agoWell that's the thing: SSH has recently gained support for signed public keys - i.e. x.509 style certificate authorities. Outside of that you have things like monkeysphere doing the same with GPG, or simpler things like LDAP scripts which just check the key against LDAP (Hashicorp Vault does something similar). But it's why I'm skeptical the UI is substantially improved: the simplest UI for VPN tends to be pre-shared keys - because everything more complicated simplifies to that interface "somehow everyone needs to agree who's allowed in" - and differs to SSH because SSH has more of a one-way contract "let this connection in, but I can't make the same connection back".
- baby 10y ago> the simplest UI for VPN tends to be pre-shared keys that's what wireguard is doing.
- aseipp 10y agoI believe they meant to say "symmetric key without any public key exchange protocol", e.g. like spiped, more than SSH. ("Pre-shared" is a bit more confusing in this particular context, admittedly.)
- baby 10y agoOh ok. Yeah sure it makes the protocol simpler. You lose a bunch of security properties though (forward secrecy on the top of my head).