[Date Prev][Date Next]
Re: Error searching DNs with escaped special characters
> Oh, sorry
> I`m running
> OpenLDAP 2.1.16 and 2.1.22
>>And this doesn`t work too!
>>dn: x509issuer=CN=test \22sa\22 sadf\,C=RU,O=ca
> dn: x509issuer=CN=test \5C\22sa\5C\22 sadf\,C=RU,O=ca
> worked but this is wrong !!!
Actually, rethinking my previous post, the latter is correct:
dn: x509issuer=CN=test \5C\22sa\5C\22 sadf\,C=RU,O=ca
while this is wrong:
dn: x509issuer=CN=test \22sa\22 sadf\,C=RU,O=ca
Another perfectly legal form is:
dn: x509issuer=CN=test \\\"sa\\\" sadf\,C=RU,O=ca
Let me elaborate on this (I couldn't wonder what yoo were
going to escape until Michael Stroeder directed me to the
schema definition of x509issuer :)
Your DN holds, as RDN, an attribute whose syntax is
distinguishedName. Then, the attribute value, in string
CN=test \"sa\" sadf,C=RU
note that the double quotes are escaped because inside
a DN, while the comma isn't because it is separating
a RDN from its parent.
When whis value is used inside another DN, all the special
chars it contains must be escaped further; so its escape
CN=test \\\"sa\\\" sadf\,C=RU
note that backslash itself needs be escaped; the same
applies to the quotes, as seen before. The comma must
also be escaped because now it is part of a single value
in a RDN. As a results you get
x509issuer=CN=test \\\"sa\\\" sadf\,C=RU,O=ca
This is what slapd currently interprets as I expect.