6 ms·
I was just reading through Adam Langley's description of the bug and this jumped out at me: > The code will always jump to the end from that second goto, err w
by higherpurpose 13y ago
I was just reading through Adam Langley's description of the bug and this jumped out at me:
> The code will always jump to the end from that second goto, err will contain a successful value because the SHA1 update operation was successful and so the signature verification will never fail.
Wait, Apple still uses SHA1? Are they aware it's banned from use (by NIST, no less) starting with this year?
http://www.zdnet.com/nist-makes-a-hash-of-sha-1-ban-7000025980/ http://www.zdnet.com/nist-makes-a-hash-of-sha-1-ban-70000259...
Maybe they'd want to take this opportunity to fix that, too...
- praseodym 13y agoIf a certificate uses SHA1, Apple (or any other vendor) can't help but use that for verification…
- RexRollman 13y agoThey can't refuse to use it? It seems to me that SHA1 should be depracated.
- tptacek 13y agoAs in, refuse to allow their browser to talk to sites on the Internet?
- stephen_g 13y agoI don't think you understand what the code is doing. This is verifying certificates for HTTPS connections - not creating them. If they removed the SHA1 verification, you can no longer visit hundreds of millions of sites that haven't updated their certificates yet. It's the people still using certificates with SHA1 hashes that need to upgrade.
- RexRollman 13y agoBut if browser makers decided not to support the hashes, the website owners would have to upgrade. Why allow them to continue to use weak hashes?
- lawnchair_larry 13y agoBecause there isn't an attack that affects them.
- cantfindmypass 13y agoThe percentage of sites using SHA256 certificate is tiny, and most CAs are still SHA1 based.