-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
PKCS11 TA: Invalid attribute CKA_CHECK_VALUE for secure key object #6453
Comments
If you have an implementation for |
This issue has been marked as a stale issue because it has been open (more than) 30 days with no activity. Remove the stale label or add a comment, otherwise this issue will automatically be closed in 5 days. Note, that you can always re-open a closed issue at any time. |
Imeplemented by #6494. |
This issue has been marked as a stale issue because it has been open (more than) 30 days with no activity. Remove the stale label or add a comment, otherwise this issue will automatically be closed in 5 days. Note, that you can always re-open a closed issue at any time. |
Work still on-going.
|
This issue has been marked as a stale issue because it has been open (more than) 30 days with no activity. Remove the stale label or add a comment, otherwise this issue will automatically be closed in 5 days. Note, that you can always re-open a closed issue at any time. |
We can close this issue. It's been addressed by the P-Rs referred above. |
Hello,
According to the PKCS#11 specifications, CKA_CHECK_VALUE is an attribute of certificate object (CKO_CERTIFICATE) and also secure key object (CKO_SECRET_KEY). It seems that the PKCS11 TA recognizes this only for certificate object, returing invalid attribute type when requested for a secure key object (CKR_ATTRIBUTE_TYPE_INVALID). It is intentional ? or a bug ?
I'll open a PR.
@etienne-lms FYI.
Thanks
Maro
The text was updated successfully, but these errors were encountered: