Add support for running pkcs11 provider in FIPS Mode #498
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When OpenSSL runs in FIPS Mode, it will not use any providers that do not provide a property fips=yes, rendering the pkcs11 provider unusable in FIPS Mode. This is a regression and for many users that need to have smart cards working in FIPS Mode. Unfortunately, proper signalization from pkcs11 modules regarding the tokens FIPS certification status is not standardized yet, this will be left up to the user to decide if the pkcs11 modules talk to FIPS certified token or not. This involves adjusting the algorithm lists to contain dynamic properties based on this configuration option, where we previously had hardcoded just provider=pkcs11. Fixes: latchset#469, latchset#164 Signed-off-by: Jakub Jelen <[email protected]>
Jakuje
force-pushed
the
fips
branch
2 times, most recently
from
38c7334 to
29e0bab
Compare
Signed-off-by: Jakub Jelen <[email protected]>
Signed-off-by: Jakub Jelen <[email protected]>
Signed-off-by: Jakub Jelen <[email protected]>
Signed-off-by: Jakub Jelen <[email protected]>
Signed-off-by: Jakub Jelen <[email protected]>
simo5
approved these changes
Jan 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
When OpenSSL runs in FIPS Mode, it will not use any providers
that do not provide a property
fips=yes, rendering the pkcs11provider unusable in FIPS Mode. This is a regression and for
many users that need to have smart cards working in FIPS Mode.
Unfortunately, proper signalization from pkcs11 modules regarding
the tokens FIPS certification status is not standardized yet,
this will be left up to the user to decide if the pkcs11 modules
talk to FIPS certified token or not.
This involves adjusting the algorithm lists to contain dynamic
properties based on this configuration option, where we previously
had hardcoded just
provider=pkcs11.Fixes: #469
Checklist
Reviewer's checklist: