The MD5 encryption implementation class is not part of a cryptographic algorithm that is validated by the Federal Information Processing standard under Windows platform

In a. NET application, MD5CryptoServiceProvider is instantiated, causing this implementation to be not a part of the Windows Platform FIPS validated cryptogr Aphic algorithms exception. That means md5cryptoserviceprovider. This cryptographic implementation class is not part of the cryptographic algorithm that is validated by the Federal Information Processing standard under the Windows platform.

This problem was not encountered on most machines and was suddenly encountered on a machine today.

The solution to this problem is to modify the registry to change the value of Hkey_local_machine\system\currentcontrolset\control\lsa\fipsalgorithmpolicy from 1 to 0. Restart the application pool. This means that FIPS-compliant cryptographic algorithm policies are not enabled.

Looks like. NET program is really controlled by the system Platform security Policy.

Original link: MD5 Encryption implementation class is not part of a cryptographic algorithm that is validated by the Federal Information Processing standard under Windows platform

The MD5 encryption implementation class is not part of a cryptographic algorithm that is validated by the Federal Information Processing standard under Windows platform