FIPS settings are conflicting with Measurement Studio

[afl3]

I have a VB.net application that uses some LED and thermometer controls from the measurement studio package, but if I try to install it on a system that has the system security setting System cryptography: Use FIPS compliant algorithms for encryption, hashing and signing set to true, I can't run the program. Anyone have a workaround for this that doesn't involve disabling that?(Isn't really an option) Thanks!

[EadieU]

What operating system are you running?  What versions of Visual Studio and Measurement Studio are you using?

[jdarlington]

I am having exactly the same problem, so I hope a resolution is forthcoming.

I am using WIndows XP Professional with Measurement Studio 2008. The complaining component appears to be in a National Instruments assembly version 8.5.35.220, although I'm not sure if it's Common, UI, or WindowsForms. My application uses the WaveformGraph control.

There is a registry setting under key HKLM\System\CurrentControlSet\Control\LSA\FIPSAlgorithmPolicy\Enabled. The FIPS security system sets this to 1 (true). If I set it to 0 (false) no error occurs. This hack is helping me during troubleshooting, but I need to remove it in order to comply with my government contract. Please help.

Thanks!

James

[nickb]

Hello all,

After investigating this issue, it looks like the cause of this is the fact that during our licensing operations, we make use of an encryption algorithm that is not FIPS compliant.  Because the registry settting James has pointed out instructs .NET to ensure that all encryption algorithms are FIPS compliant, our licensing operations fail.  This is the same licensing operation we have been performing for many years now, and this is the first time we have heard of this being an issue.

As a result of our preliminary investigation, it does not appear that there is a workaround immediately available, other than flipping this registry flag.  We will continue to look into this issue however, and we will keep you up to date on the status of our investigation.  This issue has been reported for investigation with Bug ID 154249.

NickB

National Instruments 

[nickb]

James and afl3,

What version of Visual Studio are you using to do your development?  This will be fixed for both versions of Visual Studio eventually, but because fixing this issue in Visual Studio 2005/.NET 2.0 is considerably more difficult than in Visual Studio 2008/.NET 3.0, we would like to prioritize our fixes based upon what versions of Visual Studio are being used.

Thanks,

NickB

National Instruments

[jdarlington]

I am using Visual Studio 2008 with .NET Framework 2.0.

[afl3]

I'm using Visual Studio 2008 with .net 3.5

[jdarlington]

I received my 2nd Quarter 2009 NI Developer Suite update and installed Measurement Studio 8.6.1. The problem appears to be fixed. As mentioned in a previous post, the Bug ID is 154249, and is listed as fixed in "Measurement Studio 8.6.1 Bug Fix Information". (http://zone.ni.com/devzone/cda/tut/p/id/9132)

Thanks to the NI team for getting this done so quickly!

James