Good progress by @trailofbits on resolving the MITM threat model gap in algo VPN. http://bit.ly/2iuRPNb
I think you're misreading, that issue has to do with a server being compromised and its keys being stolen. You're f'd either way.
-
-
i thought it had to do with the server certs being registered as root CAs in keychain
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
then if the server private key is compromised you're screwed. Never storing the private key seems promising
-
Compromising the server private key requires compromising the entire server. Even if you protect the key, you're still fucked.
-
does the server use the private key? If it does then i get it
-
It's only needed to gen certs for new users. Today: if you don't use that feature, then it'll never be decrypted and exposed.
-
that's what I thought re being used for user creation. I'd say having a compromised root CA is worse than someone controlling VPS
-
bad CA means non-pinned certs can now be faked. Arguably you shouldn't trust your VPS too much anyway since 3rd party controls it
-
But you do trust your VPS, it serves all your traffic through the VPN. It's an easy hop from VPS to Desktop RCE even w/o HTTPS.
-
agree completely. That applied to any VPN software you use though. The CA issue was unexpected. Glad to see it being addressed.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.