On our workstations which test or develop FIPS-140-2 products (not production, obviously), this is a painful limitation.
Reproduce:
1. Enable FIPS-140-2 mode (secpol.msc => Local Policies => Security Option => System Cryptography: Use FIPS compliant algorithms for encryption, hashing and signing = Enabled)
2. Open VS2012 => open any project
3. Try to add a NuGet package
4. Enjoy the error
Reproduce:
1. Enable FIPS-140-2 mode (secpol.msc => Local Policies => Security Option => System Cryptography: Use FIPS compliant algorithms for encryption, hashing and signing = Enabled)
2. Open VS2012 => open any project
3. Try to add a NuGet package
4. Enjoy the error
