[Date Prev][Date Next]
ACL checks and slapo-unique
- To: firstname.lastname@example.org
- Subject: ACL checks and slapo-unique
- From: Michael Ströder <email@example.com>
- Date: Wed, 15 Nov 2017 17:09:31 +0100
- Openpgp: id=43C8730E84A20E560722806C07DC7AE36A8BC938
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 SeaMonkey/2.49.1
What really strikes users is the lack of feedback in case a unique
constraint or other constraint fails.
Let's look at error messages of slapo-unique first. I'm experimenting
with a pretty simple patch for returning the effective uniqueness filter
in the diagnosticMessage.
Example output with this patch (line wrapped):
$ ldapadd -f test.ldif
adding new entry "uid=foo,ou=Users,dc=example,dc=com"
ldap_add: Constraint violation (19)
additional info: non-unique attributes found with
Even this minimum information is already somewhat useful. Of course it
would be even more nice to get the list of non-unique attribute values
(I vaguely remember some idea for a "What Failed?" response control.)
Now formerly one of the arguments against returning more information in
the diagnosticMessage was that this would reveal content information to
an attacker which is obtained by an internal search with a more
Yes, that's right.
But this problem exists anyway because an attacker can probe
values by adding entries with non-unique attributes and determine
whether an attribute value exists or not by distinguishing the result
code constraintViolation(19) vs. insufficientAccessRights(50).
Even worse this even works in case the attacker does not have read
This leads to the question whether some sort of access control or limit
check should be applied in unique_search().
What do you think?