This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients Ilya.Kulakov, ezio.melotti, paul.moore, steve.dower, tim.golden, vstinner, zach.ware
Date 2016-06-20.20:01:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1466452901.4.0.0926469906675.issue27354@psf.upfronthosting.co.za>
In-reply-to
Content
"OpenSSL doesn't seem to support paths not encodable to the ANSI code page on Windows. I suggest you to report the issue to the OpenSSL bug tracker: (...)"

For example, it wass already requested 6 years ago on the openssl-users@openssl.org mailing list:
http://comments.gmane.org/gmane.comp.encryption.openssl.user/38104

--

Oh, another link is more useful:
https://stackoverflow.com/questions/2401059/openssl-with-unicode-paths

"you will have to manually load the certificate files yourself using standard OS file I/O functions that support Unicode paths, and then parse the raw data and load it into OpenSSL, such as via PEM_read_bio_X509 with sk_X509_NAME_push, PEM_read_bio_PrivateKey/d2i_PrivateKey_bio with SSL_CTX_use_PrivateKey, d2i_X509_bio/PEM_read_bio_X509 with SSL_CTX_use_certificate, etc."
History
Date User Action Args
2016-06-20 20:01:41vstinnersetrecipients: + vstinner, paul.moore, tim.golden, ezio.melotti, zach.ware, steve.dower, Ilya.Kulakov
2016-06-20 20:01:41vstinnersetmessageid: <1466452901.4.0.0926469906675.issue27354@psf.upfronthosting.co.za>
2016-06-20 20:01:41vstinnerlinkissue27354 messages
2016-06-20 20:01:40vstinnercreate