On 4/7/2010 12:33 PM, Ryan Pfeifle wrote: > While we are on the subject of Unicode, there are other areas of OpenSSL > that need Unicode support added, in particular handling of paths and > filenames on UTF16-based filesystems that require wchar_t* parameters. > For instance, on Windows, OpenSSL cannot load certificate > files/directories that have Unicode characters in them. On ‘nix, this > is not a problem for systems that use UTF8-based filesystems, which can > be passed via char** *parameters. The Indy library > (http://www.indyproject.org) had to work around this issue recently by > implementing its own versions of SSL_load_client_CA_file(), > SSL_CTX_use_certificate_file (), SSL_CTX_use_PrivateKey_file(), and > SSL_CTX_load_verify_locations() from scratch using a custom > X509_LOOKUP_METHOD structure and support routines.
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. Either way, the OpenSSL API needs customization to pass wchar args for path names, etc. Starting as utf-8, or handled entirely by unicode. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
