[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: ldap_explode_dn corrupts UTF-8 encoding (ITS#1890)

At 01:00 AM 2002-06-17, ps@psncc.at wrote:
>On Mon, 17 Jun 2002, Pierangelo Masarati wrote:
>> > OpenLDAP 2.1.2 seems to currupt non-ASCII UTF-8 encoded characters.
>> > It actually turns unprintable chars (in the ASCII sense) into \<hexcode>.
>> I think this is a leftover of when we decided to use UTF8 instead
>> of the '\' + HEXPAIR representation of non-ascii chars, and initially
>> it was intended; of course, when parsing a DN, one wants the correct
>> UTF8 encoding.
>Note that the problem does not exist in 2.0.23...

Difference is within specification and necessary to address
other issues.

>To further elaborate the problem: before passing the DN to the
>ldap_explode_dn function it is properly (UTF-8) encoded. Afterwards the DN
>parts aren't...

Hex pairs can appear in properly encoded DN strings.  See RFC 2253.