Comments
3 comments
-
Hello tyoungman,
It is.. however we are presently tracking a bug where under certain circumstances one of the encryption algorithms incorrectly switches to a deprecated cipher, which is only meant to happen on assemblies targetting very old .Net versions. -
Thanks @Peter_Laws,
Our assemblies currently utilize .NET frameworks 4-4.8, I assume this would fall under "very old".
Might be a good time for us to upgrade!
I'll do some investigating with this in mind. Thanks again for your response. -
Coming back to comment that SmartAssembly fails when Error reporting and the FIPS compliance setting is turned on for my builds.
I've submitted the crash report that appears within the SmartAssembly tool, but for now I will have to go without error reporting.
Add comment
Please sign in to leave a comment.
I am seeing errors when then running these assemblies built using SmartAssembly that I am not seeing with local builds (with the FIPS setting enabled on my machine)
I am looking for confirmation whether or not SmartAssembly is FIPS compliant.
Thank you!