Michael Ströder wrote:
Howard Chu wrote:
In other words, you have software that was broken for the past 10 years that RFC2251 was in effect, before RFC4511 was written to allow your software vendor to get away with never fixing their broken code. Nice.
But IMO it's worth thinking about how to deal in slapd with the wording "MAY or MAY NOT include the RDN attribute(s)" found in RFC4511 today.
Ultimately, there's nothing to think about. RFC2251 is now obsolete and RFC4511 is the spec, so we'll have to change to comply. It's just a question of someone who feels strongly enough getting motivated to write the patch.