I copied this request from the original post on the mRemoteNG Atlassian bug/feature tickets site. Our environment for security reasons must have the FIPS windows setting set to Enabled. I can use Windows Remote Desktop to any of our servers fine (I have the latest RDP version 8.1 installed), but when launching the latest version of mRemoteNG (Prerelease 1.75 Alpha 3) I get the following message:

The Windows security setting, "System cryptography: Use FIPS compliant algorithms for encryption, hashing and signing", is enabled. This setting is not compatible with mRemoteNG.

See the Microsoft Support article at http://support.microsoft.com/kb/811833 for more information.

mRemoteNG will now close.

In most applications, if an application is not FIPS compatible, it can be used by creating a .config file and putting the following in:

<runtime>
<enforceFIPSPolicy enabled="false"/>
</runtime>

However, when putting this in the proper format, the application still does not run due to FIPS and then closes. FIPS check is hard coded in. The check should be soft coded as the .config file will allow the use of non Fips crypto's, even if Windows as a whole does not allow it.