Ryan Pfeifle
Sr. Programmer
Voice Print International, Inc.
Immediate Results. Unmatched Value.
Tel: 1.805.389.5200 x5297
Fax: N/A
Email: r...@vpi-corp.com
Web: www.VPI-corp.com
Experience the VPI Value Advantage at http://www.VPI-corp.com/Value
The information transmitted in this message is intended only for the addressee
and may contain confidential and/or privileged material. Any review,
retransmission, dissemination or other use of, or taking of any action in
reliance upon, this information by persons or entities other than the intended
recipient is prohibited. If you received this in error, please contact the
sender and delete this material from any computer.
-----Original Message-----
From: William A. Rowe Jr. [mailto:wr...@rowe-clan.net]
Sent: Thursday, April 08, 2010 5:01 AM
To: openssl-users@openssl.org
Cc: Ryan Pfeifle
Subject: Re: does bio_get_mem_data handle unicode?
> That's one approach. Another is to use UTF-8 filenames as the
> local code page, this is the solution the APR library opted for.
Unfortunately, that is not currently an option when passing filenames to
OpenSSL on Windows. The entire OpenSSL API uses char* only, and internally
uses C library Ansi functions for file I/O instead of Unicode functions. So
there is no possibility to get a Unicode filename all the way down to the
filesystem intact.
> Either way, the OpenSSL API needs customization to pass wchar args
> for path names, etc. Starting as utf-8, or handled entirely by unicode.
Adding support for wchar parameters would not be needed, and thus no change to
the existing API interfaces, if OpenSSL were to natively support UTF-8 values.
It could then decode UTF-8 input values, and encode UTF-8 output values,
to/from other charsets internally as needed on a per-platform basis.
