-
Notifications
You must be signed in to change notification settings - Fork 86
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
AttributeError
exception in module community.crypto.openssl_privatekey_info
when check_consistency
is true
#701
Comments
As a workaround you can either stick to cryptography < 42.0.0, or disable that check. There will be a new version of the collection ~this weekend fixing this bug. |
Hi
Yes. That was what we in fact did (disable the check). Thanks! Looking forward for that fix. Cheers |
Please note that it won't be a real fix for the functionality, since that is no longer reachable with cryptography 42.0.0+. It will simply disable the consistency check for RSA private keys, and the test will return #702 contains the fix. Out of curiosity, what is your use-case for |
Thanks for this. We are completely fine with that approach.
Well we were using the consistency check simply in a test playbook which was part of a molecule test scenario. That was the context. So we are not using this functionality in production. Thanks again for your support. Cheers |
the following did the trick in my case pip3 install cryptography==41.0.5 |
SUMMARY
A task step like this:
will end up with the following exception:
AttributeError: 'cryptography.hazmat.bindings._rust.openssl.rsa.RSA' object has no attribute '_backend'
ISSUE TYPE
COMPONENT NAME
community.crypto.openssl_privatekey_info
ANSIBLE VERSION
COLLECTION VERSION
CONFIGURATION
OS / ENVIRONMENT
OS version:
Package versions in python virtual environment:
STEPS TO REPRODUCE
Assuming you have ansible and community.crypto installed, you execute a playbook like this:
EXPECTED RESULTS
The playbook above should finish with no errors.
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: