Bug 15219 - Xamarin Studio is broken on Windows systems that enforce FIPS compliant hashing
Summary: Xamarin Studio is broken on Windows systems that enforce FIPS compliant hashing
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: Trunk
Hardware: PC Mac OS
: Normal major
Target Milestone: master
Assignee: Bugzilla
Depends on:
Reported: 2013-10-04 18:32 UTC by Mikayla Hutchinson [MSFT]
Modified: 2017-07-20 20:37 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report for Bug 15219 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Mikayla Hutchinson [MSFT] 2013-10-04 18:32:08 UTC
Xamarin Studio breaks on Window systems that enforce FIPS compliant hashing (http://blogs.msdn.com/b/shawnfa/archive/2005/05/16/417975.aspx). System.Security.Cryptography.MD5.Create throws an exception, since MD5 is not FIPS compliant.


We should make these features degrade gracefully, or bundle Mono's MD5 implementation.
Comment 1 Mikayla Hutchinson [MSFT] 2013-10-21 09:20:03 UTC
Also, IKVM.Reflection is broken since it uses SHA1Managed, and this causes much more serious problems.

It may be possible to fix that by using SHA1CryptoServiceProvider.