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

164 pkcs11 support #253

Merged
merged 8 commits into from
Mar 12, 2024
Merged

164 pkcs11 support #253

merged 8 commits into from
Mar 12, 2024

Conversation

tdivis
Copy link
Contributor

@tdivis tdivis commented Apr 13, 2023

Fix #164.

Note: It's based on branch for #164, which should be merged first so the tests pass.

@tdivis tdivis force-pushed the 164-pkcs11-support branch 7 times, most recently from b23ab3c to 0b5939f Compare April 17, 2023 11:55
if ((key = PyXmlSec_NewKey1((PyTypeObject*)self)) == NULL) goto ON_FAIL;

Py_BEGIN_ALLOW_THREADS;
key->handle = xmlSecCryptoAppKeyLoad(engine_and_key_id, xmlSecKeyDataFormatEngine, NULL, xmlSecCryptoAppGetDefaultPwdCallback(),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A note with xmlsec 1.3.3, xmlSecCryptoAppKeyLoad is deprecated in favor of xmlSecCryptoAppKeyLoadEx. This added an argument which adds the capacity to handle public keys. Since we're handling a private key, I think that this line should be this:
key->handle = xmlSecCryptoAppKeyLoad(engine_and_key_id, xmlSecKeyDataTypePrivate, xmlSecKeyDataFormatEngine, NULL, xmlSecCryptoAppGetDefaultPwdCallback(),

@jimjag jimjag merged commit 99e5cb2 into xmlsec:master Mar 12, 2024
0 of 31 checks passed
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

Successfully merging this pull request may close these issues.

Support PKCS11
4 participants