Bug 35782 - SetSite failed This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms
Summary: SetSite failed This implementation is not part of the Windows Platform FIPS v...
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: General ()
Version: 3.11 (C5)
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2015-11-11 09:05 UTC by John Miller [MSFT]
Modified: 2016-05-19 15:33 UTC (History)
3 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 on Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description John Miller [MSFT] 2015-11-11 09:05:24 UTC

   XVS won't load on Windows when FIPS compliant hashing and signing is enforced. The ActivityLog.xml shows an error. 

**Steps to Reproduce:**

   1. Enable FIPS compliance: http://blogs.msdn.com/b/shawnfa/archive/2005/05/16/417975.aspx
   2. Launch VS with XVS installed

**Actual Results:**

   XVS does not load. 

   SetSite failed for package [XamarinShellPackage]
   This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.

**Expected Results:**

   No issue loading.

** Additional Information **

Similar to this: https://bugzilla.xamarin.com/show_bug.cgi?id=15219
Comment 1 Daniel Cazzulino 2016-05-19 14:38:38 UTC
This doesn't repro anymore with with the latest (master) builds, so resolving fixed.

Please reopen if you see this again.
Comment 2 Daniel Cazzulino 2016-05-19 15:33:22 UTC
Following the instructions at https://blogs.msdn.microsoft.com/shawnfa/2005/05/16/enforcing-fips-certified-cryptography/, it's not even possible to compile in Visual Studio 2015 a regular console app:

1>------ Rebuild All started: Project: ConsoleApplication4, Configuration: Debug Any CPU ------
1>C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.CSharp.Core.targets(67,5): error MSB3883: Unexpected exception: 
1>C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.CSharp.Core.targets(67,5): error : System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
1>C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.CSharp.Core.targets(67,5): error : at System.Security.Cryptography.SHA256Managed..ctor()
1>C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.CSharp.Core.targets(67,5): error : --- End of inner exception stack trace ---
1>C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.CSharp.Core.targets(67,5): error : at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
1>C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.CSharp.Core.targets(67,5): error : at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
1>C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.CSharp.Core.targets(67,5): error : at System.Security.Cryptography.CryptoConfig.CreateFromName(String name, Object[] args)
1>C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.CSharp.Core.targets(67,5): error : at System.Security.Cryptography.SHA256.Create()
1>C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.CSharp.Core.targets(67,5): error : at Microsoft.CodeAnalysis.CommandLine.DesktopBuildClient.GetBasePipeName(String compilerExeDirectory)
1>C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.CSharp.Core.targets(67,5): error : at Microsoft.CodeAnalysis.CommandLine.DesktopBuildClient.GetPipeNameForPath(String compilerExeDirectory)
1>C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.CSharp.Core.targets(67,5): error : at Microsoft.CodeAnalysis.CommandLine.DesktopBuildClient.RunServerCompilation(RequestLanguage language, List`1 arguments, BuildPaths buildPaths, String keepAlive, String libEnvVariable, CancellationToken cancellationToken)
1>C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.CSharp.Core.targets(67,5): error : at Microsoft.CodeAnalysis.BuildTasks.ManagedCompiler.ExecuteTool(String pathToTool, String responseFileCommands, String commandLineCommands)
========== Rebuild All: 0 succeeded, 1 failed, 0 skipped ==========

So I'm guessing it goes way deeper than our own stuff anyway...