Problem with FIPS Validated Cryptographic Algorithms

c# .net wpf windows-xp fips
Dave picture Dave · Jan 20, 2010 · Viewed 21.9k times · Source

I am running Visual Studio 2008 Version 9.0.30729.1 SP with .NET 3.5 SP 1 under Windows XP Pro Version 2002 SP 3 with an Intel Core 2 Duo E8400 3 GHz processor.

I am developing a C# WPF application that uses the Microsoft Patterns & Practices group's Composite Application Library (CAL).

I am getting the following compliation error in XAML:

"MC1000: This implementation is not part of the Windows platform FIPS validated cryptographic algorithms."

I have found a hotfix that is supposed to fix this in Microsoft Knowledge Base aritcle 935434. However, the installer for this hotfix reports the following error:

"The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch."

The page for the hotfix lists .NET 3.0 as a prerequisite. Though I'm working with .Net 3.5, my machine does have .NET 3.0 installed as well. I would therefore expect this hotfix to install. It was my hope that even though the hotfix is targeted at .NET 3.0, it would nonetheless solve my problem.

In any event, I cannot install the hotfix. Does anybody have any alternate suggestions on how I can get past the "This implementation is not part of..." compilation error I'm seeing?

Thanks, Dave

Answer

Raj Rao picture Raj Rao · Feb 10, 2010

I wonder if FIPS compliance checking is turned on on your machine. Here is a post that I had written a while back that talks about turning it off and why you might be getting this error messages. Basically FIPS is a US federal government standard for security and encryption. Based on it, some encryption algorithms will not run on your machine, if your machine is running in FIPS compliance mode. Easy fix in that case is to turn off FIPS compliance checking. The right fix is to pick the correct encryption algorithm.

Here is my post: http://blog.aggregatedintelligence.com/2007/10/fips-validated-cryptographic-algorithms.html and this one: http://blog.aggregatedintelligence.com/2009/08/cryptographic-algorithms-and-net.html

Related questions

Environment.CurrentDirectory is yielding unexpected results when running installed app

Background: I built an installer for my app, and all my dll's and content files are getting correctly copied to the C:\Program Files\MyCompany\MyApp directory. When I run my app from Visual Studio, everything works great. When I …

Read More
Metadata file '.dll' could not be found

I am working on a WPF, C# 3.0 project, and I get this error: Error 1 Metadata file 'WORK=- \Tools\VersionManagementSystem\BusinessLogicLayer\bin\Debug \BusinessLogicLayer.dll' could not be found C:\-=WORK=- \Tools \VersionManagementSystem\VersionManagementSystem\CSC VersionManagementSystem This is …

Read More
Setting WPF image source in code

I'm trying to set a WPF image's source in code. The image is embedded as a resource in the project. By looking at examples I've come up with the below code. For some reason it doesn't work - the image …

Read More