Hi, On Wednesday, 19. September 2012, Quanah Gibson-Mount wrote: > In playing with Net::LDAP::Util it became apparent that it is not compliant > with RFC4514, but instead complies with the older RFC2253. Specifically > where #'s in DNs are concerned. Currently it's expecting # followed by hex > digits. This may not be the case once RFC4514 LDIF is in use. > > An example DN that it does not handle correctly: > > dn: zimbraSignatureName=Signature #1,uid=xyz,ou=people,dc=example,dc=com > > The above is not legal with RFC2253, but it is legal with RFC4514.
Please also have alook at a new alternative solution to the ldap_explode_dn issue w.r.t. RFC 4514: https://github.com/marschap/perl-ldap/tree/ldap_explode_dn-relaxed This alternative tries to adhere to Postel's law, "be conservative in what you do, be liberal in what you accept from others". Pro's: - no additional option (like 'rfc2253') necessary - should not break existing code that relied on some RFC 2253 peculiarities (at least, the probability to do so is much lower) - higher compatibilitiy to openLDAP's slapdn than the other alternative Con's: - might accept DN's that are not conforming to any of the RFCs (but canonical_dn will make them confiorming to both) Which of the alternatives do you prefer? Best PEter -- Peter Marschall pe...@adpm.de
