https://support.microsoft.com/en-us/kb/2862973

Microsoft Security Advisory: Update for deprecation of MD5 hashing algorithm for Microsoft root certificate program: August 13, 2013

More information

    The referenced change for February 2014 that is discussed in Advisory 2862973 applies only to certificates that are used for the following:
        server authentication
        code signing
        time stamping
    Other certificate usages of the MD5 signature hash algorithm will not be blocked.
    In regards to code signing, we will allow signed binaries that were signed before March 2009 to continue to work, even if the signing cert used MD5 signature hash algorithm

----
https://technet.microsoft.com/library/security/2862973

----

Nobody is probably going to argue that Microsoft does not strictly follow U.S. government cryptography security standards.

A timeline.

1) As of 2012 MD5 is accepted for some pretty secure applications as per government standards.

2) May 2012, the Flame malware is discovered in Iran. The malware seems to have been a collaborative effort of several intelligence agencies.

3) The online image of md5, including Wikipedia pages and various other sites is changed to suggest that there was no official backing for md5. It is almost like the government never heard of it.

4) Sha is now the public face of U.S. cryptography. A next gen option of Keccak is being discussed but anyone who uses a search engine can find that it seems to have been built with deliberate flaws.

-----

I'm not against spies stealing from other spies.

I'm against mafia gangster scum who say "Here is a reliable unbroken security system bacfked by the government", knowing full well it is broken.