Any ideas why MD5CryptoServiceProvider isn't throwing a FIPS compliance error. I'm using Win7 and the 3.5 framework. The MS documentation says its not FIPS compliant, but I'm not getting an exception like I was with some of the other algorithms.
--Update--
I get the FIPS exception from a console app, but not my ASP.Net app
Perhaps the web site has disabled the FIPS checking using something like this in web.config:
<configuration>
<runtime>
<enforceFIPSPolicy enabled="false"/>
</runtime>
</configuration>
Do you have the same behaviour when you run the app in the ASP.NET development web server vs. IIS?
This guy had the opposite problem: enforceFIPSPolicy flag in web.config doesn't seem to working for web application
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With