diff options
| author | Noriko Hosoi <nhosoi@redhat.com> | 2010-10-05 15:40:10 -0700 |
|---|---|---|
| committer | Noriko Hosoi <nhosoi@redhat.com> | 2010-10-05 15:40:10 -0700 |
| commit | 9a00a444cea117d0950bef3bb9327bd05e9d11bb (patch) | |
| tree | a62045664f3bc7c44f973b234716afb2bc069c47 /missing | |
| parent | c783496c2a020860b33a44db7d89f1f33f036a1d (diff) | |
| download | ds-9a00a444cea117d0950bef3bb9327bd05e9d11bb.tar.gz ds-9a00a444cea117d0950bef3bb9327bd05e9d11bb.tar.xz ds-9a00a444cea117d0950bef3bb9327bd05e9d11bb.zip | |
Bug 640027 - Naming attribute with a special char sequence parsing bug
https://bugzilla.redhat.com/show_bug.cgi?id=640027
Description: When DN is made from RDNs containing escaped plus
"\+", the dn normalizer considers the value could be nested multi-
valued RDNs. (e.g., cn=C\=Z\+A\=X\+B\=Y\,o\=O,o=OO)
In that case, multi-valued RDNs are sorted by the normalizer.
(==> cn=A\=X\+B\=Y\+C\=Z\,o\=O,o=OO)
The sample DN provided by Andrey Ivanov contains "\+", but that
is not a separator for the multi-valued RDNs:
cn=mytest\+\=-123'\;456,dc=example,dc=com
The dn normalizer should have checked the possibility, as well.
The check is added in this patch.
Also, sorting was not triggered if multi-valued RDNs are located
at the end of the value. (e.g., cn=C\=X\,B\=Y\+A\=Z,o=OO)
The bug was fixed, as well.
Diffstat (limited to 'missing')
0 files changed, 0 insertions, 0 deletions