You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to be able to work in an openssl configuration where the only provider configured is the pkcs11-provider, in that case we need to be able to import both public and private keys into sessions objects for tokens that can handle all operations (eg soft tokens).
This is because people may end up using a mix of in-token and out of token keys in applications where the main usage dictates use of in-token only keys, but some auxiliary libraries try to use keys from files, or from memory for some functions (like checking signatures, decrypting data, and what not).
The text was updated successfully, but these errors were encountered:
It will not work with the only pkcs11 provider configured - or we have to import/implement decoder stuff into it. We still need base or default provider
simo5
changed the title
Test that importing private kets from PEM files (or evn just memory buffers) into session objects works
Test that importing private keys from PEM files (or evn just memory buffers) into session objects works
Jun 11, 2024
simo5
changed the title
Test that importing private keys from PEM files (or evn just memory buffers) into session objects works
Test that importing private keys from PEM files (or even just memory buffers) into session objects works
Aug 29, 2024
We want to be able to work in an openssl configuration where the only provider configured is the pkcs11-provider, in that case we need to be able to import both public and private keys into sessions objects for tokens that can handle all operations (eg soft tokens).
This is because people may end up using a mix of in-token and out of token keys in applications where the main usage dictates use of in-token only keys, but some auxiliary libraries try to use keys from files, or from memory for some functions (like checking signatures, decrypting data, and what not).
The text was updated successfully, but these errors were encountered: