Replies: 2 comments 2 replies
-
|
Use: It will output all of the keys it can find and pkcs11-provider will produce a pkcs11-uri as an additional output, example: As you can se the object ID is printed there (if a random number it will not be the easiest to read but it is available). |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Unfortunately no, we could add a key parameter that you could obtain via EVP_PKEY_get_params(), but it is not currently something we do. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello there!
I have been using pkcs11-provider to manage my softhsm setup and it's been working well. I notice that when I create a new private key using pkcs11-provider (by creating a new EVP_PKEY_CTX and set corresponding parameters), if
pkcs11-uriparameter is empty, a random id will be generated for the key (I suppose this comes from softhsm not pkcs11-provider).I know that you can set up
pkcs11-uriparameter to designate an uri for the newly created key. However this parameter seems only settable but not gettable for EVP_PKEY_CTX.Now I'm wondering, with an EVP_PKEY_CTX (or related object, such as EVP_PKEY, or even OSSL_STORE/OSSL_STORE_INFO), does pkcs11-provider support any way of querying its
pkcs11-uri?Thanks for your time in advance!
Beta Was this translation helpful? Give feedback.
All reactions