-
Notifications
You must be signed in to change notification settings - Fork 90
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
Using x509_certificate_info on certificates with unicode SANs fails #312
Comments
Different than the other issue you mentioned, but for a similar reason. For Python 2.7.5 I think @felixfontein is the better person to provide a solution however. |
Yes, adding the |
Is there a workaround I can use while waiting for the fix to be released? |
What you could do is:
|
Ok, thank you for that. The platform is pretty tied down in regards to using newer versions of python packages (Red Hat Satellite 6.9 on Red Hat Enterprise Linux 7.9). |
For the time being as a workaround I've just dumped the new revision in place. This seems to work.
|
community.crypto 1.9.6 is now out with a fix for this. |
SUMMARY
Using x509_certificate_info on certificates with unicode SANs fails.
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe6'
Could this be a similar issue to #270?
ISSUE TYPE
COMPONENT NAME
x509_certificate_info
ANSIBLE VERSION
COLLECTION VERSION
CONFIGURATION
OS / ENVIRONMENT
STEPS TO REPRODUCE
I created a certificate with acme.sh that contained an encoded Internationalized domain name (IDNA encoding).
Tried to read it with openssl_certificate_info but that failed, so I installed the latest collection and tried with
community.crypto.x509_certificate_info
but that fails too.The task I first used:
The error that resulted:
After that I did
ansible-galaxy collection install community.crypto
and changed the task:The error that resulted:
EXPECTED RESULTS
Expected it to parse successfully.
ACTUAL RESULTS
Give a unicode error:
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe6'
The text was updated successfully, but these errors were encountered: