> On Jun 3, 2018, at 4:45 AM, Richard Levitte <levi...@openssl.org> wrote:
> 
> Yeah, I just learned that myself.  Somehow, I thought wchar_t would be
> Unicode characters.  So ok, with this information, UTF-8 makes
> sense...

Nico has convinced me that the mapping from UTF-8 to BMPString should
be UTF-16, which is agrees with the BMP representation on the code
points in the Basic Multinational Plane, but also supports surrogate
pairs for code points outside the plane, so that if someone wanted
to use "emoji" (or more traditional glyph outside the BMP) for their
password, they could.  This is a strict superset of UCS-2 and avoids
having to reject some UTF-8 codepoints.

-- 
        Viktor.

_______________________________________________
openssl-project mailing list
openssl-project@openssl.org
https://mta.openssl.org/mailman/listinfo/openssl-project

Reply via email to