Issue 3229 - "EQUALS" ('=') in DN string representation
Summary: "EQUALS" ('=') in DN string representation
Status: VERIFIED FIXED
Alias: None
Product: OpenLDAP
Classification: Unclassified
Component: slapd (show other issues)
Version: unspecified
Hardware: All All
: --- normal
Target Milestone: ---
Assignee: OpenLDAP project
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-07-10 08:29 UTC by ando@openldap.org
Modified: 2014-08-01 21:06 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description ando@openldap.org 2004-07-10 08:29:39 UTC
Full_Name: Pierangelo Masarati
Version: 2.2/2.1
OS: irrelevant
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (81.74.43.82)


After a short discussion with Hallvard Furuseth, which followed a posting from
Hendrik Harms http://www.openldap.org/lists/openldap-software/200407/msg00224.html
, it emerged that current releases of slapd (2.2, 2.1) treat the EQUALS ('=')
according to our interpretation of the (buggy) RFC 2253 and not according to
draft-ietf-ldapbis-dn, i.e. EQUALS in the value part of an AVA is __ALWAYS__
escaped when converting from DN to string representation, and it must be escaped
when parsing from string to DN representation.

I suggest, for future releases (possibly from 2.3, to avoid changing such an
important behavior in the middle of a minor), to change it into:
    - allow parsing from string to DN representation with or without escaping,
      so that any of "=", "\=", "\3D" is equivalent;
    - always generate string representations from DN in escaped form
      (I personally suggest "\3D" to ease efficient subparsing inside the code,
      e.g. for ACLs or so, Hallvard is more inclined towards the more readable 
      "\=" form, and this can be discussed later) to minimize the possibility
      of incompatiilities between different versions of software
    - we should defer the generation of string representations without escaping
      to a moment when these backwards compatibility issues are negligible.

I wrote this as an ITS to keep track of its evolution; I'm about to commit a
change to HEAD that is protected behind #define LDAP_DEVEL, so it does not get
into release.

p.

Comment 1 ando@openldap.org 2004-07-10 08:30:32 UTC
changed notes
moved from Incoming to Development
Comment 2 ando@openldap.org 2004-07-15 19:08:17 UTC
changed notes
Comment 3 ando@openldap.org 2004-07-18 20:28:21 UTC
changed notes
changed state Open to Release
Comment 4 Kurt Zeilenga 2004-07-28 15:28:43 UTC
changed state Release to Closed
Comment 5 Kurt Zeilenga 2004-07-28 15:28:57 UTC
moved from Development to Software Bugs
Comment 6 Howard Chu 2009-02-17 05:06:49 UTC
moved from Software Bugs to Archive.Software Bugs
Comment 7 OpenLDAP project 2014-08-01 21:06:32 UTC
HEAD/RE22 now complies with draft-ietf-ldapbis-dn