6 ms·
Never forget: when Facebook, Twitter, and Cloudflare tried to slow-down SHA-1 deprecation: https://www.facebook.com/notes/alex-stamos/the-sha-1-sunset/10153782
by mtgx 10y ago
Never forget: when Facebook, Twitter, and Cloudflare tried to slow-down SHA-1 deprecation:
https://www.facebook.com/notes/alex-stamos/the-sha-1-sunset/10153782990367929 https://www.facebook.com/notes/alex-stamos/the-sha-1-sunset/...
https://blog.twitter.com/2015/sunsetting-sha-1 https://blog.twitter.com/2015/sunsetting-sha-1
https://blog.cloudflare.com/sha-1-deprecation-no-browser-left-behind/ https://blog.cloudflare.com/sha-1-deprecation-no-browser-lef...
I think Microsoft tried to do it too early on, but eventually agreed to a more aggressive timeline.
- pfg 10y agoWorth noting that Facebook stopped offering SHA-1 back in November[1]. Cloudflare still offers SHA-1 for paying customers (via a root certificate pulled from trust stores, i.e. which are only supported on outdated devices/browsers). Not sure about Twitter. [1]: https://www.facebook.com/notes/protect-the-graph/retiring-sha-1-certificates/1814716098768533 https://www.facebook.com/notes/protect-the-graph/retiring-sh...