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.

Sign up for GitHub

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

Jump to bottom

Consider deriving PKCS #11 public key from certificate #71

Open
clundin25 opened this issue Mar 22, 2023 · 0 comments
Open

Consider deriving PKCS #11 public key from certificate #71

clundin25 opened this issue Mar 22, 2023 · 0 comments
Assignees
@clundin25
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: question Request for information or clarification. Not an issue.

Comments

@clundin25
Copy link
Collaborator

Currently PKCS#11 requires a public key to be token. Alternatively, the public key can be derived from the certificate, similar to the windows and macos implementations.

This would:

  1. Reduce work. There is no reason to have the public key stored in the HSM, our use case only cares about the certificate.
  2. Reduce mistakes. Most users of ECP will likely think a certificate and private key is enough. Extracting and loading the Public key is an awkward and extra step.
@clundin25 clundin25 added type: question Request for information or clarification. Not an issue. priority: p3 Desirable enhancement or fix. May not be included in next release. labels Mar 22, 2023
@clundin25 clundin25 self-assigned this Mar 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@clundin25 clundin25

Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: question Request for information or clarification. Not an issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@clundin25