The Bouncy Castle .Net FIPS assembly is not strong name signed

[ContentsMayVary]

The Bouncy Castle .Net FIPS assembly (bc-fips-1.0.1.dll) is not strong name signed. This makes it impossible to use with signed assemblies.

Normally you would be able to sign a DLL by disassembling it, then reassembling and signing it. However that won't work for two reasons: (1) The hash of the assembly will change, and the FIPS validation will be therefore violated, and (2) trying to use the signed version will throw an exception because it has been modified and the hash has changed.