News for hackers. Stuff that matters.
Re:Moving forward on improving HTTP's security by ams6110 on Wednesday November 13, 2013 @08:33AM (#6725032)
SSH keys work exactly like self-signed certificates. On first connection you get the "whoah, this isn't trusted, do you want to proceed" warning, and if you accept, you are not warned in the future unless the key changes.

If browsers would make it easier to "permanently accept" a self-signed certificate (right now it's usually a multi-step process with blood-red warning messages at every step) we'd have the same situation as SSH keys.

Re:Moving forward on improving HTTP's security by peterwwillis on Wednesday November 13, 2013 @09:49AM (#6725453)
HTTPS involves multiple servers that are interchanged regularly and commonly use different keys. The keys change regularly. There'd be no way to know if the key changing is part of regular operation or a man in the middle.
Re:Moving forward on improving HTTP's security by bnr on Wednesday November 13, 2013 @10:06AM (#6725543)
Note that there's a difference between SSH fingerprints and (self-signed) SSL certificates. Multiple servers can easily share a certificate.
Re:Moving forward on improving HTTP's security by peterwwillis on Thursday November 14, 2013 @12:40AM (#6730776)
It would be unwise to do so. In any case, phasing out old servers and certs for new ones is common practice. Using one cert everywhere (which would mean using one set of keys everywhere, which is a horrible idea) would require more downtime for maintenance of the certificates. It's not gonna happen.