https://bugs.openldap.org/show_bug.cgi?id=9621
Issue ID: 9621 Summary: back-mdb multival NULL matchingrule crash Product: OpenLDAP Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: --- Component: backends Assignee: bugs@openldap.org Reporter: hyc@openldap.org Target Milestone: ---
When configured for multival, back-mdb may crash if the attribute schema has no equality matching rule.
https://bugs.openldap.org/show_bug.cgi?id=9621
Quanah Gibson-Mount quanah@openldap.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |2.5.7 Resolution|--- |TEST Status|UNCONFIRMED |RESOLVED
--- Comment #1 from Quanah Gibson-Mount quanah@openldap.org --- Commits: • 5cd45ec9 by Howard Chu at 2021-08-02T20:24:58+01:00 ITS#9621 fix for multival with NULL mr
https://bugs.openldap.org/show_bug.cgi?id=9621
Quanah Gibson-Mount quanah@openldap.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Assignee|bugs@openldap.org |hyc@openldap.org
https://bugs.openldap.org/show_bug.cgi?id=9621
--- Comment #2 from Howard Chu hyc@openldap.org --- Note that it's a violation of the data model for a multivalued attribute to be missing an EQUALITY matching rule. So this bug only affects sites with defective schema definitions.
https://bugs.openldap.org/show_bug.cgi?id=9621
--- Comment #3 from Michael Ströder michael@stroeder.com --- (In reply to Howard Chu from comment #2)
Note that it's a violation of the data model for a multivalued attribute to be missing an EQUALITY matching rule.
Why is that a violation of the data model?
For example I definitely expect it's possible to store multiple values in attribute 'userPKCS12' without any issues via MOD_REPLACE affecting the whole attribute value set.
I don't expect that I can add/remove distinct attribute values though.
https://bugs.openldap.org/show_bug.cgi?id=9621
--- Comment #4 from Howard Chu hyc@openldap.org --- (In reply to Michael Ströder from comment #3)
(In reply to Howard Chu from comment #2)
Note that it's a violation of the data model for a multivalued attribute to be missing an EQUALITY matching rule.
Why is that a violation of the data model?
For example I definitely expect it's possible to store multiple values in attribute 'userPKCS12' without any issues via MOD_REPLACE affecting the whole attribute value set.
I don't expect that I can add/remove distinct attribute values though.
The server is required to prevent the storage of duplicate values. That's inherent to the definition of a SET, and attributes are sets of values. A server is unable to fulfill this requirement without an EQUALITY matching rule.
https://bugs.openldap.org/show_bug.cgi?id=9621
Quanah Gibson-Mount quanah@openldap.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |VERIFIED Resolution|TEST |FIXED