3 ms·
Exactly why Google moved to an "aggressive" timeline to deprecate SHA-1. Schneier predicted the cost of SHA-1 collisions years ago and said criminal groups will
by mtgx 11y ago
Exactly why Google moved to an "aggressive" timeline to deprecate SHA-1. Schneier predicted the cost of SHA-1 collisions years ago and said criminal groups will be able to create collisions by 2018 - which means you needed to start pushing for killing SHA-1 support years earlier.
But when Google did that everyone jumped on them for "trying to control the Internet" or something (because obviously trying to make the Internet adopt stronger security is a power tripping thing). I hope at least now they've seen the error in their ways.
Oh, and it turns out Schneier was actually too optimistic about the costs of SHA-1 collissions - by about an order of magnitude:
> 211 * 28.4 = 219.4 ~ $700K by 2015
https://www.schneier.com/blog/archives/2012/10/when_will_we_se.html https://www.schneier.com/blog/archives/2012/10/when_will_we_...
- danudey 11y agoAnd Google's push to deprecate SHA-1 to try to drag the internet into modern security practices pales in comparison to Apple's ATS implementation, which has a brutally modern set of minimum requirements (TLS1.2, 256-bit elliptic curve, SHA-256, 2048-bit RSA key). And given Apple's extremely vocal stance on privacy and security, and their 'sudden' addition of ATS, it wouldn't surprise me if ATS became a hard requirement in iOS 10.
- yuhong 11y agoATS has nothing to do with web browsing though.