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

ca: support back old cyptography API #839

Merged
merged 1 commit into from Jan 18, 2022

Conversation

aplanas
Copy link
Contributor

@aplanas aplanas commented Jan 18, 2022

After [1] we moved from M2Crypto to cryptography, and we started to drop
the use of the, now optional, backend parameter. This is OK as we are
explicit on the minimal version of cryptography, but we still use in
other modules (like crypto.py or tpm_main.py for example) the old API.

This patch use the optional backend parameter to unify the API usage,
and still be compatible with some older versions of cryptography.

[1] #747

Signed-off-by: Alberto Planas aplanas@suse.com

After [1] we moved from M2Crypto to cryptography, and we started to drop
the use of the, now optional, `backend` parameter.  This is OK as we are
explicit on the minimal version of cryptography, but we still use in
other modules (like crypto.py or tpm_main.py for example) the old API.

This patch use the optional `backend` parameter to unify the API usage,
and still be compatible with some older versions of cryptography.

[1] keylime#747

Signed-off-by: Alberto Planas <aplanas@suse.com>
@mpeters mpeters merged commit 59246d7 into keylime:master Jan 18, 2022
@aplanas aplanas deleted the fix_crypto_backend branch January 18, 2022 15:49
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.

None yet

2 participants