Re:We need a “/heartbleed.txt” standard, and we need it ASAP
by mh8h on Wednesday April 09, 2014 @11:26AM
(#7559857)
Doesn't heartbleed let an attacker hijack the keys? Then they can man-in-the-middle the connection, and spoof the file so that the website appear to be not vulnerable to the attack.
[ Parent
| on HN ]
Re:We need a “/heartbleed.txt” standard, and we need it ASAP
by jik on Wednesday April 09, 2014 @11:31AM
(#7559896)
MITM attacks require far more sophistication and many more moving parts than just stealing data from a web server's memory. Just because you have the SSL cert's key doesn't mean you have the ability to use it to MITM a site.
I'm not saying what you propose is impossible; I'm just saying it's quite unlikely. Security is all about layers. You don't throw away a layer that could be effective at increasing security in the majority of cases just because there are some cases where it wouldn't work.
Re:We need a “/heartbleed.txt” standard, and we need it ASAP
by mh8h on Wednesday April 09, 2014 @11:54AM
(#7560068)
Of course. You can't MITM all the traffic to the site. But if hackers are targeting a certain security-conscious user, this standard will give them another tool!
This new layer will make the security better for the average user, but it will enable attackers to make a website look falsely patched in a MITM attack.
Re:We need a “/heartbleed.txt” standard, and we need it ASAP
by maxerickson on Wednesday April 09, 2014 @11:36AM
(#7559939)
There can be a useful communication of "passwords older than X should be changed" to the user. Blocking that doesn't make the user any worse off than simply not having it.
(That leaves the question of how useful it is to users; I guess it is nice for a service like lastpass, but the truly paranoid probably aren't relying on cues from services)