Skip to content
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

Provider FIPS property management #164

Open
beldmit opened this issue Jan 5, 2023 · 0 comments
Open

Provider FIPS property management #164

beldmit opened this issue Jan 5, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@beldmit
Copy link
Collaborator

beldmit commented Jan 5, 2023

Describe the feature
PKCS11 provider may provide the same algorithms with or without FIPS property. It depends on the underlying token certification status. Algorithm properties should be manageable via config.

Expected behavior

  • Minimal requirement: if we have smth like "fips=1" in the configuration section, all the algorithms provided by provider should have "fips=yes" property.
  • Real-life requirement: support of syntax like "fips-capable = alg1, alg2" allows specifying which algorithms provided by driver have the "fips=yes" property.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant