mirror of
https://git.openldap.org/openldap/openldap.git
synced 2026-02-03 20:40:05 -05:00
Annuaire LDAP
error reporting to client and syslog. And indexing, of course. Now, the problem is that matching rules get called from different places that are inconsistent in what an assertedValue is. When doing a modify, a full certificate value is passed (to verify it isn't already there). When doing a search or compare, the passed value is in the syntax of the matching rule. Consistency would require that the caller extracts an asserted value from the full value before calling smr_match. It can do this by calling smr_convert (it was unused, was it meant to be used for this?). Unfortunately, the caller is typically value_find, value_match, etc. that have themselves little knowledge of what they are dealing with, so their interface needs to be extended, new flag values or new arguments, so that they know if they have a value in attribute type syntax or in matching rule syntax. |
||
|---|---|---|
| build | ||
| clients | ||
| contrib | ||
| doc | ||
| include | ||
| libraries | ||
| servers | ||
| tests | ||
| acconfig.h | ||
| acinclude.m4 | ||
| aclocal.m4 | ||
| configure | ||
| configure.in | ||
| COPYRIGHT | ||
| INSTALL | ||
| LICENSE | ||
| Makefile.in | ||
| README | ||
OpenLDAP Devel README This software was obtained from the development branch (HEAD) of the OpenLDAP Software Repository. This copy is likely already not current, the development branch changes frequently. These changes include code implementing experimental features and unproven bug fixes. Please do NOT redistribute copies of the development branch. The OpenLDAP Developer's FAQ is available at: http://www.openldap.org/faq/index.cgi?file=4 Client developers seeking a suitable development platform should use "release" or "stable" versions. http://www.openldap.org/software/ --- $OpenLDAP$