Hacker News new | past | comments | ask | show | jobs | submit login

> 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.




Well 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".


> the simplest UI for VPN tends to be pre-shared keys

that's what wireguard is doing.


I 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.)


Oh ok. Yeah sure it makes the protocol simpler. You lose a bunch of security properties though (forward secrecy on the top of my head).




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: