3 ms·
Postponing the Retirement of SHA-1
- ryanlol 11y agoNo better way to make people migrate than breaking things.
- Strom 11y agoThis isn't really about developed countries and grumpy corporate device policies, it's more about very poor people and their really old second hand feature phones. These are people who use the same device for 5, even 10 years and don't really have the resources to replace them more frequently.
- paulddraper 11y agoExactly. They'll have a less secure experience, but that what they choose. You and your iPhone 7S can have a super secure one.
- ryanlol 11y agoI hope facebook at least displays a big red constantly visible warning banner to those users.
- colejohnson66 11y agoExcept the problem is when Chrome/Firefox/Safari prevent access to their favorite website that still uses SHA-1 or whatever, people don't blame the website, they blame Google/Mozilla/Apple. When a website is hacked and your data leaked, it's not the website's fault for leaving it on a publicly accessibly page, it's the hacker's. Sure, the hacker was wrong for doing so, but the website failed to enact _basic_ security practices; something people should be up in arms about, but aren't.
- jvehent 11y agoRyan Sleevi, of the Chrome PKI team, has written a much more detailed analysis of the Cloudflare proposal and its caveats. I recommend you read them before voicing an opinion on this topic, because it is a complex one. 1. https://medium.com/@sleevi_/a-history-of-hard-choices-c1e1cc9bb089#.mdfi0lung https://medium.com/@sleevi_/a-history-of-hard-choices-c1e1cc... 2. https://medium.com/@sleevi_/legacy-verified-legacy-solutions-15eb688716e4#.uioly27l9 https://medium.com/@sleevi_/legacy-verified-legacy-solutions... Today is the last day to get SHA-1 certs issued. We, at Mozilla, stocked up on SHA-1 certs that expire 39 months from now, so we can keep serving old clients up until March 2019 using cert switching technology. Most organizations that want to keep supporting old clients have done similar things. Smaller companies typically don't care about old clients, and most likely already broke compatibility with them by using various modern web stacks.
- yuhong 11y agoChrome BTW plans to remove pre-Win7 support in early 2016. I was pushing for Firefox to at least remove XP SP2 support in 2016.
- colejohnson66 11y agoWhy not pre-Vista? Besides the bad rap because driver developers took advantage of undocumented features (among other reasons), how is it different architecturally from 7? Internally, Vista and up are all NT 6.x releases (XP was 5.x): Vista was 6.0, 7 was 6.1, 8 was 6.2, etc.
- yuhong 11y agoWin7 does have plenty of API changes too, and Vista never had much of a market share.
- toast0 11y agoWindows Vista has fewer users than XP, so if you're OK with the consequences of dropping support for XP to simplify your life, you should be ok dropping Vista too. Same thing with dropping IE7 at the same time as IE6. Added: yes, you could use this argument to say you don't need to support Windows 10 either, but Windows 10 is probably going to get more users over time, as opposed to Vista. Windows 8.0 is also less than XP, but since 7 and 8.1 are big, it's probably not a great idea to leave a hole in your supported os chart.
- RaleyField 11y ago> so if you're OK with the consequences of dropping support for XP to simplify your life XP is EOL, Vista is not. XP users ought not to connect to the internet.
- Laforet 11y agoWindows 7 added a number of APIs on top of Vista so implementing backward compatibility means a lot of additional complexity with minimal benefit. A prime example is the windows build of Electron (https://github.com/atom/electron https://github.com/atom/electron) that uses some touch control and notification APIs that are only available in Windows 7 and later. People have been asking for a long time for Windows XP compatibility and the answer has always been a firm NO.