<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>I would definitely need something like this. I have some library
code that uses OpenSSL 1.0.2 (can't upgrade to 1.1.x yet because
of all the interface changes), and it currently has to use a
custom X509_LOOKUP_METHOD to handle Unicode filenames on Windows
(in fact, this library had to completely replace several OpenSSL
functions in order to work with Unicode filenames for things like
certificate files, key files, etc).</p>
<p>It would be REALLY REALLY nice if OpenSSL worked with Unicode
filenames/paths consistently on Windows! BIO functions like
BIO_new_file(), BIO_read_filename(), etc do support UTF-8 encoded
filenames on Windows, but not all SSL functions use BIOs to access
files/directories, so UTF-8 filenames/paths are only supported
consistently on POSIX platforms whose file/directory APIs accept
UTF-8 encoded strings. Windows does not support that,
filenames/paths must be encoded in ANSI or UTF-16 only.</p>
<p>What is OpenSSL's current status regarding this?<br>
</p>
<br>
<pre class="moz-signature" cols="72">Remy Lebeau
Lebeau Software</pre>
<div class="moz-cite-prefix">On 2/7/2018 3:59 PM, Salz, Rich via
openssl-users wrote:<br>
</div>
<blockquote type="cite"
cite="mid:8F810AB3-E86A-400A-980D-A35EDE90560F@akamai.com">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
<div class="WordSection1">
<p class="MsoNormal">Yes, if there’s something that was made
impossible to do because of things being made opaque, adding
the missing API’s would be a bugfix and go into 1.1.0 and
beyond. It woud be great if you could create a PR.<o:p> <br>
</o:p></p>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p><br>
</p>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>