-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve output length checking for FIPS indicators in AES/HMAC code #138
Conversation
For what it's worth, if you're ever thinking about certifying KMAC, OpenSSL < 3.4 doesn't have a check. OpenSSL 3.4+ should have a check. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only nits, otherwise this looks good to me, any reason why it is still in draft ?
Signed-off-by: Jakub Jelen <jjelen@redhat.com>
Signed-off-by: Jakub Jelen <jjelen@redhat.com>
The check_mac_fips_indicators() won't do anything for the CMACs, as the cmac implementation in FIPS provider does not implement this parameter. The AES key with SIGN/VERIFY flags was also not marked correctly as FIPS valid so any CMAC operation on that given key caused the FIPS indicator failure. Signed-off-by: Jakub Jelen <jjelen@redhat.com>
Signed-off-by: Jakub Jelen <jjelen@redhat.com>
Looks good, feel free to push once tests pass |
All green. Merged. |
There were several issues:
check_mac_fips_indicators()
won't do anything for the CMACs, as the cmac implementation in FIPS provider does not implement the fips indicator OSSL_PARAM.I am still not sure about the GCM as the specs are vague. Putting 64b for now.