Beacon service is not FIPS compliant
jsm2000 opened this issue · comments
Hello,
Looks like Beacon service is calling a version of SHA256 that is not FIPS compliant.
See thread I started in forums
http://www.dnnsoftware.com/forums/forumid/200/threadid/535732/scope/posts
.
Looks like the code in BeaconService.cs is calling SHA256Managed which is not FIPS compliant. I see other code in DNN calling SHA256CryptoServiceProvider which is FIPS compliant.
Thanks
John
Sorry, eneterd this bug in the wrong location.