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

PKCS11 TA: Invalid attribute CKA_CHECK_VALUE for secure key object #6453

Closed
maroueneboubakri opened this issue Nov 10, 2023 · 7 comments
Closed
Labels

Comments

@maroueneboubakri
Copy link
Contributor

maroueneboubakri commented Nov 10, 2023

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

@etienne-lms
Copy link
Contributor

If you have an implementation for CKA_CHECK_VALUE, a P-R a warmly welcome. See #6431.

Copy link

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.

@github-actions github-actions bot added the Stale label Dec 11, 2023
@etienne-lms
Copy link
Contributor

Imeplemented by #6494.

@github-actions github-actions bot removed the Stale label Dec 12, 2023
Copy link

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.

@github-actions github-actions bot added the Stale label Jan 11, 2024
@etienne-lms
Copy link
Contributor

Work still on-going.
#6494 has been merged but led to 2 series of fixup changes:

@github-actions github-actions bot removed the Stale label Jan 12, 2024
Copy link

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.

@github-actions github-actions bot added the Stale label Feb 12, 2024
@etienne-lms
Copy link
Contributor

We can close this issue. It's been addressed by the P-Rs referred above.

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

No branches or pull requests

3 participants