[Date Prev][Date Next]
uniqueMember and nameUID* issues (ITS#3210)
Full_Name: Pierangelo Masarati
Version: HEAD, 2.2
OS: Linux (irrelevant)
Submission from: (NULL) (220.127.116.11)
There are issues with the uniqueMember attribute. Adding an optional UID
(i.e. a suffix of the form "#'<uid>'B" to a DN-style value) causes an assertion
in dnPretty because the DN is not NULL terminated (which is a bit old and
overconservative, but indicates a problem in any case, since we still want to be
able to use generic DNs in string representation as NULL terminated strings).
Moreover, the numeric ID is accepted whatever string it uses, whilke its syntax
requires it be a bitstring (i.e. '1' or '0', with the lead digit a '1' unless
the whole value is '0').
Finally, the uniqueMemberMatch is a bit optimistic since it does memcmp() on the
UID part even if the length of the UIDs is different.
A patch is coming.