https://bugzilla.redhat.com/show_bug.cgi?id=536907
A RDN value with an escaped NULL character (\00) is not handled correctly. Run the test script attached to bug #438136 with test string 16 ('\00\11\22\33'). You will find that an extra CN value is added to the entry with the unescaped DN form (which leaves the NULL character escaped). When the test script renames the entry, the first correct CN value is left around since it is not considered to match the old RDN. Here is the output from the test script demonstrating the issue: Binding with Directory Manager ...Bound... ===========================> Initial entry DN: cn=\00\09\12\1b,dc=test,dc=com ------------------------------------------------------------------------ dn:cn=\00\09\12\1b,dc=test,dc=com objectClass: top person sn: Last Name cn: \00 ===========================> Renamed entry DN: cn=WithoutSlash,dc=test,dc=com ------------------------------------------------------------------------ dn:cn=WithoutSlash,dc=test,dc=com objectClass: top person sn: Last Name cn: WithoutSlash
batch update to FUTURE milestone
set default ticket origin to Community
Added initial screened field value.
corner case
Metadata Update from @nkinder: - Issue set to the milestone: 1.3.6 backlog
Metadata Update from @mreynolds: - Custom field reviewstatus reset (from Needs Review) - Issue close_status updated to: None - Issue set to the milestone: FUTURE (was: 1.3.6 backlog)
Metadata Update from @vashirov: - Custom field reviewstatus adjusted to None - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/95
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.