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 steve.dower
Recipients Ilya.Kulakov, christian.heimes, ezio.melotti, paul.moore, steve.dower, tim.golden, vstinner, zach.ware
Date 2016-09-17.21:09:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1474146596.54.0.414680854039.issue27354@psf.upfronthosting.co.za>
In-reply-to
Content
I haven't tracked it down in 1.1, but in 1.0.2 OpenSSL handles ASCII, UTF-8 and mbcs/ANSI paths explicitly: https://github.com/openssl/openssl/blob/OpenSSL_1_0_2-stable/crypto/bio/bss_file.c#L138

So for 3.6 and later, if we're encoding the paths with fsencode(), it'll be fine, but we could also use utf-8 unconditionally.

Doing a search of the codebase though, there's only the one place that does this and everywhere else just uses fopen() without attempting to decode. I don't think we're exposing many of those publicly though.
History
Date User Action Args
2016-09-17 21:09:56steve.dowersetrecipients: + steve.dower, paul.moore, vstinner, christian.heimes, tim.golden, ezio.melotti, zach.ware, Ilya.Kulakov
2016-09-17 21:09:56steve.dowersetmessageid: <1474146596.54.0.414680854039.issue27354@psf.upfronthosting.co.za>
2016-09-17 21:09:56steve.dowerlinkissue27354 messages
2016-09-17 21:09:56steve.dowercreate