Postponing the Retirement of SHA-1
infoq.com
infoq.com
1. https://medium.com/@sleevi_/a-history-of-hard-choices-c1e1cc...
2. 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.
A prime example is the windows build of 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.
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.
XP is EOL, Vista is not. XP users ought not to connect to the internet.
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.