[openssl-project] Help deciding on PR 6341 (facilitate reading PKCS#12 objects in OSSL_STORE)

Richard Levitte levitte at openssl.org
Wed Jun 6 07:45:10 UTC 2018


In message <4DCA9A91-1487-4BFC-8A4E-B79FAD473AF3 at dukhovni.org> on Tue, 5 Jun 2018 18:37:21 -0400, Viktor Dukhovni <openssl-users at dukhovni.org> said:

openssl-users> 
openssl-users> 
openssl-users> > On Jun 3, 2018, at 4:45 AM, Richard Levitte <levitte at openssl.org> wrote:
openssl-users> > 
openssl-users> > Yeah, I just learned that myself.  Somehow, I thought wchar_t would be
openssl-users> > Unicode characters.  So ok, with this information, UTF-8 makes
openssl-users> > sense...
openssl-users> 
openssl-users> Nico has convinced me that the mapping from UTF-8 to BMPString should
openssl-users> be UTF-16, which is agrees with the BMP representation on the code
openssl-users> points in the Basic Multinational Plane, but also supports surrogate
openssl-users> pairs for code points outside the plane, so that if someone wanted
openssl-users> to use "emoji" (or more traditional glyph outside the BMP) for their
openssl-users> password, they could.  This is a strict superset of UCS-2 and avoids
openssl-users> having to reject some UTF-8 codepoints.

Yup.  It seems that BMPString evolved from UCS-2 into UTF-16 at some
point, and that evolution affected PKCS#12 objects...

Cheers,
Richard

-- 
Richard Levitte         levitte at openssl.org
OpenSSL Project         http://www.openssl.org/~levitte/


More information about the openssl-project mailing list