Replies: 1 comment
|
I found an additional reference: section 2.5 of the BC-FJA 2.1.1 User Guide lists exactly the HMAC you obtained: This conflicts with the I couldn’t establish from these documents why the values differ. Confirmation from Bouncy Castle is still needed on which artifact corresponds to certificate #4943. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I'm trying to find the latest certified version of bc-fips to use. https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/4943 suggests that 2.1.1 is the latest certified version, cool. I look into the certification pdf - https://csrc.nist.gov/CSRC/media/projects/cryptographic-module-validation-program/documents/security-policies/140sp4943.pdf - and therein I find validation information: that running
java -cp bc-fips-2.1.1.jar org.bouncycastle.util.DumpInfoshould provide me with verification info, specificallyModule SHA2-256 HMAC: d231036b466c2216d352c4c1ee9df602bc6e05514817bdfea2eab8a376566e90Now, I tried downloading that artifact from two different maven repositories - maven-central-apache and maven-central-repo1. Both produce the same artifact, byte-identical. But when I run the given command using the downloaded artifact I get the following:
So a completely different HMAC. What gives? The artifact fingerprint (7B121B76A7ED6CE6E60AD51784E913A8E3A748C0) matches the one published on Bouncy Castle site, so it doesn't look like an attack, just a discrepancy. But it makes me worry if using it in my program will pass FIPS certification
All reactions