This project has moved. For the latest updates, please go here.

Error: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.

Topics: Support Requests
Nov 1, 2012 at 9:25 PM
Edited Nov 1, 2012 at 9:26 PM

I keep getting the "This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms." when trying to connect to a CM12 client. Is the code using MD5 hashing algorithm because it is not FIPs certified?

Coordinator
Dec 1, 2012 at 4:30 PM

Can you connect a remote client with Powershell ? "Enter-PSSession <Hostname>" ... Do you also get an Error ?

Developer
Jun 27, 2013 at 1:52 PM
Hi Roger,

We have the same problem and its because we use the Microsoft security templates from the SCM 3.0 tool which sets the FIPS setting as default.

I think the problem might be due to the use of the MD5CryptoServiceProvider in sccmclictr.automation project because that is not FIPS compliant:
http://sccmclictrlib.codeplex.com/SourceControl/latest#sccmclictr.automation/Common.cs
(Maybe there is more places where this is used but i havnt search all of the code).

See this blog:
http://blog.aggregatedintelligence.com/2007/10/fips-validated-cryptographic-algorithms.html

If possible try to switch from MD5CryptoServiceProvider to SHA1CryptoServiceProvider since that is FIPS compliant.

Regards
Matt
Coordinator
Jun 27, 2013 at 2:19 PM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.