2 ms·
In a general sense, yes. It would suck to lose your private PGP key and have someone send fake messages. Probably more so than losing any one (or few) encrypted
by tedunangst 12y ago
In a general sense, yes. It would suck to lose your private PGP key and have someone send fake messages. Probably more so than losing any one (or few) encrypted messages.
HTTPS is a little different. You need to verify you're talking to the real paypal.com, but that's so you know you're not sending your password to a stranger. paypal doesn't send signed emails, for instance. (maybe they should, but not with the website key, for sure). Stealing passwords and cookies is pretty much the end game for https private key theft.
Is anyone willing to say that a bug which only leaks passwords and cookies is a minor issue?
wrt heartbleed, there seems to be a gap between the "could happen" and "did happen" consequences. Besides the one test server pummeled with millions of requests, were any private keys actually compromised? On the other hand, we know yahoo passwords were compromised because people were doing it within hours of the heartbleed announcement. I'm more concerned with the latter.
Yes, if I'm writing a sort function for vulnerabilities, "read arbitrary memory" is worse than "read some memory", but there should be some accounting for degree of difficulty as well.