On Thu, Nov 19, 2009, Brant Thomsen wrote: > One major issue to consider when using UTF-16 encoding is that the string > can be big-endian or little-endian. If you were to somehow generate a > certificate using UTF-16 encoded strings, you would need to make sure that > those certificates will only be used on machines that have the same > architecture as the machine generating the certificate. Otherwise, the > strings will be unreadable. > > I would highly recommend just converting your UTF-16 strings into UTF-8 and > using that in your certificate(s). It will save you a lot of headaches. >
The encoding rules dictate that BMPStrings have to be big endian format. Steve. -- Dr Stephen N. Henson. OpenSSL project core developer. Commercial tech support now available see: http://www.openssl.org ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
