Re:Why Google is Hurrying the Web to Kill SHA-1
by cbhl on Monday September 08, 2014 @12:37PM
(#8285712)
Windows XP SP 2 (SP 3 is fine) and early Android, I believe, are the clients that don't support certs later than SHA-1.
[ Parent
| on HN ]
Re:Why Google is Hurrying the Web to Kill SHA-1
by drdaeman on Monday September 08, 2014 @04:54PM
(#8287186)
Just curious — does X.509 support multiple signatures, so both SHA-1 and SHA-2-based sigs could be included, one for legacy user-agents and one for modern ones?
Re:Why Google is Hurrying the Web to Kill SHA-1
by cwyers on Monday September 08, 2014 @06:38PM
(#8287718)
It has to be so frustrating to Google that the people responsible for Android make it so hard for users to upgrade to versions that support SHA-2.
Re:Why Google is Hurrying the Web to Kill SHA-1
by GeneralMayhem on Monday September 08, 2014 @10:15PM
(#8288425)
It's not Google's fault the telecoms cripple every phone they sell.
Re:Why Google is Hurrying the Web to Kill SHA-1
by teddyh on Tuesday September 09, 2014 @05:15AM
(#8289302)
Well, Google knew it would happen, and allowed them to do it.
Re:Why Google is Hurrying the Web to Kill SHA-1
by Someone1234 on Monday September 08, 2014 @01:33PM
(#8286050)
There are also other (mostly unsupported) mobile devices which don't. Like old ebook readers which have browsers for some reason.