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

Add PKCS11 Support #1

Open
jyao1 opened this issue May 10, 2021 · 1 comment
Open

Add PKCS11 Support #1

jyao1 opened this issue May 10, 2021 · 1 comment
Assignees

Comments

@jyao1
Copy link
Member

jyao1 commented May 10, 2021

PKCS11 is an industry-standard and generic cryptography interface. Instead of libSPDM supporting multiple bindings to cryptography libraries it could have a single PKCS11 layer that then binds to the underlying cryptography libraries.

e.g. opensource implementation: https://github.com/tpm2-software/tpm2-pkcs11

One possible way is to plug-in pkcs11 instead of replacing crytolib directly.
We can let libspdm->cryptlib->pkcs11. e.g. create cryptlib_pkcs11
If anyone implements a pkcs11 lib, then this pkcs11 lib can be plug in.
People still prefers to keep cryptlib interface here, because it is simpler than pkcs11.

@jyao1
Copy link
Member Author

jyao1 commented Nov 2, 2021

Standard reference:

  1. https://docs.oasis-open.org/pkcs11/pkcs11-base/v2.40/pkcs11-base-v2.40.html
  2. https://docs.oasis-open.org/pkcs11/pkcs11-base/v3.0/pkcs11-base-v3.0.html

The header file can be found at: Appendix B. Manifest constants.

We can create a cryptolib_pkcs11.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants