Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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
This bug has been unresolved for a long time, and it is not a priority to fix. This bug is being closed since there is not a pressing reason to address it, though the upstream ticket will remain open in case someone in the community is compelled to provide a patch.