Re: parsing String Representations back into Distinguished Names (ITS#1314)

[Kurt@OpenLDAP.org]

At 07:35 AM 2001-09-05, norbert.klasen@daasi.de wrote:
>Full_Name: Norbert Klasen
>Version: 2.0.11
>OS: Linux
>URL: 
>Submission from: (NULL) (172.178.2.38)

Handling of UTF-8 in DNs is still quite restricted in 2.0.
We have multiple outstanding ITS in this area [including
at least one with code], so I'll likely just close this one.

See devel list for discussions in this area.

>Hi,
>shouldn't the following strings represent the same DN?
>o=Fakultät,dc=example,dc=com
>o=Fakult\C3\A4t,dc=example,dc=com
>o=#46616B756C74C3A474,dc=example,dc=com

Note that the last string is not equivalent to the
first two and likely is invalid.  The # must be
followed by the base64 encoding of the BER encoding
of the value, a directoryString (presumably of CHOICE
universalString).