Windows 10: SHA-1 deprecation countdown

Source: SHA-1 deprecation countdown | Microsoft Edge Dev Blog

:)

 

Can't view SSL certificates on websites visited using EDGE in Windows 10

Although Microsoft does something in the scope of certificates in Edge browser:
SHA-1 deprecation countdown - Microsoft Edge Dev Blog
but still does not take into consideration enabling to view full details of HTTPS website certificate (like IE and all other web browsers do)!

 

Downloading file.exe

Since this only recently started with your other Windows 10 system, I suspect that Microsoft only just finally enabled the detection of these SHA-1 signed files, quite possibly in the recent Windows 10 Anniversary update or at least the IE11 updates that
were included within it.

So if you had installed the update on one system and not the Surface Pro 4, this might explain the difference, since my own system I was using to test here is actually running Windows 8.1 and apparently has also received an update which generates that same
corrupt or invalid message you received.

Looking around, I just found another Web Developer blog article that discusses the SHA-1 deprecation roadmap. Though this doesn't specifically mention how files containing digital signatures will be handled, I suspect that the effects on SSL certificates
using SHA-1 and those for file downloads when using IE11 would be quite similar.

An update to our SHA-1 deprecation roadmap

From the comments in this and another earlier blog article I can see that even the more technically knowledgeable web developers in these discussions have questions and see potential problems with this deprecation. One of these is that older Windows XP
and Server 2003 systems don't support the new SHA-2 or other algorithms, so these will permanently break when software or web pages containing these are accessed.

So this migration from SHA-1 to SHA-2 may be far more disruptive then Microsoft expected for those with outdated software, servers and client systems.

Rob