Re:OpenBSD forks, prunes, fixes OpenSSL
by uuid_to_string on Monday April 21, 2014 @09:38PM
(#7625251)
For per packet encryption.
For authentication, there is CurveCP.
People seem confident with OpenSSH's authentication
mechanism. Why not use that?
At some point one has to trust that the IP address
one is sending/retrieving data to/from is the correct
one. That's easier said than done if some host wants
to keep changing its IP address every few days.
The SSL PKI scheme (the SSL approach to authentication),
as implemented for public websites, is not much of a
confidence-builder, IMO. Opinions may differ.
If websites maintained consistent IP addresses and we
could authenticate these machines using OpenSSH keys,
I would be more willing to believe we could verify
their "authenticity".
Re:OpenBSD forks, prunes, fixes OpenSSL
by leccine on Tuesday April 22, 2014 @10:59AM
(#7628026)
Exactly. The problem with SSL/TLS that it relies on a broken promise with the CAs, and as we have seen several times it is extremely easy to exploit. Hello rogue CAs.
For authentication, there is CurveCP.
People seem confident with OpenSSH's authentication mechanism. Why not use that?
At some point one has to trust that the IP address one is sending/retrieving data to/from is the correct one. That's easier said than done if some host wants to keep changing its IP address every few days.
The SSL PKI scheme (the SSL approach to authentication), as implemented for public websites, is not much of a confidence-builder, IMO. Opinions may differ.
If websites maintained consistent IP addresses and we could authenticate these machines using OpenSSH keys, I would be more willing to believe we could verify their "authenticity".