News for hackers. Stuff that matters.
Re:Why Google is Hurrying the Web to Kill SHA-1 by tptacek on Monday September 08, 2014 @12:10PM (#8285560)
Vulnerable to what? Perhaps better to say, "everyone would be vulnerable".
[deleted]
Re:Why Google is Hurrying the Web to Kill SHA-1 by tptacek on Monday September 08, 2014 @12:14PM (#8285584)
Someone on HN knows this subject much better than I do, but as I understand it, there's no attack in the literature that takes a good certificate request and $2MM as an input and spits out a validating certificate as an output.

This is different than the situation with MD5, where the components needed for a successful attack were known to the literature, and the real work was (a) scaling the attack so that it could perform within the time windows needed to forge a TLS certificate and (b) putting all the pieces together.

(But see upthread with 'pbsd, who is one of those people on HN who knows the subject much better than me).

Re:Why Google is Hurrying the Web to Kill SHA-1 by xkiwi on Monday September 08, 2014 @12:22PM (#8285623)
Https is to prevent wiretapping and man-in-the-middle attacks.

The problem now is even you established HTTPS connection, the weak SHA-1 encryption will not protect you.

Re:Why Google is Hurrying the Web to Kill SHA-1 by tptacek on Monday September 08, 2014 @12:32PM (#8285674)
The SHA1 vulnerability being contemplated here affects only the establishment of an HTTPS connection; the attack scenario involves obtaining a forged certificate.
Re:Why Google is Hurrying the Web to Kill SHA-1 by rictic on Monday September 08, 2014 @01:15PM (#8285925)
That's an especially pedantic correction, as it does not impact the meaning of the statement.

s/the weak SHA-1 encryption/the weakened SHA-1 hash used to verify the certificate that's used to authenticate the encrypted connection/

Re:Why Google is Hurrying the Web to Kill SHA-1 by tptacek on Monday September 08, 2014 @01:23PM (#8285983)
It is, you're right. It's a hobbyhorse of mine, though, because SHA1 (and MD5) appear in TLS ciphersuites as MAC components, and those uses are not known to be vulnerable at all.