SHA1 certificates for secure SSL/TLS communications are deprecated due to known computational vulnerabilities. To ensure secure communications, a forced deprecation sounds reasonable (i.e. refuse to connect to these). That has the side effect that it will lock out many users who are unable to use stronger hashes such as SHA256. However, if a fallback to SHA1 is provided (as Facebook is proposing), everyone will be vulnerable to SHA1 downgrade man-in-the-middle attacks.
What to do?
(Score: 1, Insightful) by Anonymous Coward on Friday December 11 2015, @05:55PM
Why not simply have browsers deny any connection with SHA1? This will protect users of modern browsers from forced downgrading (because the browser won't accept the downgrade), but not block the users of outdated browsers (because those will, of course, not refuse to use SHA1).
(Score: 3, Funny) by dyingtolive on Friday December 11 2015, @06:09PM
Are... are you really advocating a new version of software as a solution to issues caused by people not upgrading to new versions of software?
Don't blame me, I voted for moose wang!
(Score: 2) by Lunix Nutcase on Friday December 11 2015, @06:13PM
Why not simply have browsers deny any connection with SHA1?
Because that doesn't actually help here. The entire point this is an issue is due to people who can't upgrade their browser and your solution wold require... updating the browser.