openldap-devel

openldap-devel@openldap.org

1443 discussions

Re: commit: ldap/servers/slapd/back-bdb back-bdb.h index.c init.c monitor.c proto-bdb.h
by Pierangelo Masarati 08 Aug '07

08 Aug '07

ando(a)OpenLDAP.org wrote: > add monitor support for unindexed attributes (need to manually #define BDB_MONITOR_IDX) This patch adds an operational attribute, olmBDBNotIndexed, that contains information about search operations directed to this database and using unindexed attributes in the filter. As a result, the monitor entry for the database will contain attributes like olmBDBNotIndexed: <attr>#<count>#<index> where <attr> is the attribute, <count> is the number of occurrences of that attribute in a search filter that could not use indexes, and <index> is the type of filters that were used, with the syntax used for the "index" directive. For example, olmBDBNotIndexed: mobile#91#eq olmBDBNotIndexed: telephoneNumber#1876#eq,sub To enable, one needs to explicitly #define BDB_MONITOR_IDX. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

3 7

Re: commit: ldap/doc/man/man5 slapd-relay.5
by Pierangelo Masarati 06 Aug '07

06 Aug '07

ando(a)OpenLDAP.org wrote: > Log Message: > add back-config support to back-relay Heads-up: I've changed the syntax. Now, slapo-rwm(5) is no longer implicitly instantiated when the "relay" directive is used. I didn't like it at the very beginning, although it would make things simpler for straightforward configurations. So please, holler if you think the old syntax should be preserved. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

Handling links/references in docs (footnotes?)
by Gavin Henry 05 Aug '07

05 Aug '07

Dear all, I'm just about done merging http://www.openldap.org/faq/data/cache/738.html into maintenance.sdf, but I want to keep the link references to the oracle site. Should I do {{URL:blah}} or can sdf to nice footnotes? Thanks. -- Kind Regards, Gavin Henry. Managing Director. T +44 (0) 1224 279484 M +44 (0) 7930 323266 F +44 (0) 1224 824887 E ghenry(a)suretecsystems.com Open Source. Open Solutions(tm). http://www.suretecsystems.com/

1 0

Re: commit: ldap/servers/slapd backend.c backglue.c backover.c bconfig.c config.h proto-slap.h slap.h
by Ralf Haferkamp 03 Aug '07

03 Aug '07

The BI_db_func()-functions (xxx_db_init, xxx_db_open, xxx_db_close and xxx_db_destroy) now accept a ConfigArgs pointer as an additional argument. I think I fixed all existing backends and overlays to accept the new parameter (make test succeeded with --enable-backends=yes and --enable-overlays=yes). Currently only back-monitor uses the new parameter for printing error messages to the ca->msg attribute. I plan to update the other backends and overlays next. On Wednesday 25 July 2007 17:21, ralf(a)openldap.org wrote: [..] > Log Message: > Added a new parameter (ConfigArgs*) to the _db_init, _db_open, _db_close > and _db_destroy functions. [..] -- Ralf

1 1

doc-modified generation?
by Gavin Henry 02 Aug '07

02 Aug '07

Hi All, What file is used for the date of the html generation? It's always stuck at "10 July 2007" Gavin. -- Kind Regards, Gavin Henry. Managing Director. T +44 (0) 1224 279484 M +44 (0) 7930 323266 F +44 (0) 1224 824887 E ghenry(a)suretecsystems.com Open Source. Open Solutions(tm). http://www.suretecsystems.com/

2 1

Re: commit: ldap/servers/slapd dn.c
by Pierangelo Masarati 02 Aug '07

02 Aug '07

hyc(a)OpenLDAP.org wrote: > Update of /repo/OpenLDAP/pkg/ldap/servers/slapd > > Modified Files: > Tag: OPENLDAP_REL_ENG_2_3 > dn.c 1.170.2.10 -> 1.170.2.11 > > Log Message: > ITS#5057 from HEAD re23 is failing test026 because of AVA sorting. Interesting enough, HEAD succeeds. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

Certificate list validation
by Pierangelo Masarati 02 Aug '07

02 Aug '07

I'm playing with certification authorities and so, and I came across certificate lists. Currently, the certificate list syntax 1.3.6.1.4.1.1466.115.121.1.9 is validated by sequenceValidate, which simply checks if the value starts with a LBER_SEQUENCE tag. After reading related RFCs and X.509 I understood that a certificate list is always supposed to be a complete structure, respectful of X.509 7.3. I stumbled on this problem because I have to implement an architecture based on strongAuthenticationUser and certificationAuthority (I know they're deprecated in favor of pkiUser and pkiCA, but this is not an option right now, unfortunately), where the latter requires authorityRevocationList and certificateRevocationList. When the lists are empty, common practice allowed to use an arbitrary dummy value, while OpenLDAP requires at least ":: MAAAAA==" (i.e. LBER_SEQUENCE in base64) to fool sequenceValidate(). I'd like to know: - is my understanding of X.509 correct? (certificate lists need to be complete as per X.509 7.3, with no revokedCertificates) - is there any other common practice to deal with empty authorityRevocationList/certificateRevocationList? - would a certificateListValidate() that complies with X.509 7.3 be helpful/welcome in 2.4? p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

2 2

Yet another backport to suggest
by Benoit Donnette 26 Jul '07

26 Jul '07

Dear Howard, Let me suggest yet another backport on the 2.3 branch (specifically on 2.3.37) from the Head, this time related to the entryDN attributes indexing. Once again you are the original author of the commit that was backported, it seems my contributions relate to backport your most awaited features - am I a serial backporter ? :-) I hope it will be interesting enough a feature to be included. Yours sincerely, Benoît Donnette - Expert TM2L/OSSA - www.08000linux.com LINAGORA - 27 rue de Berri - 75008 PARIS LINAGORA recrute : http://www.linagora.com/societe/nous_rejoindre/

2 1

ITS#5040, operational attribute updates
by Howard Chu 24 Jul '07

24 Jul '07

I don't see anything in X.501/X.511 etc to imply there's any difference - should modifyTimeStamp be left untouched when an update only changes an entry's operational attributes, or should all modifications, regardless of how they were initiated or what they touch, update the modifyTimeStamp? Possible alternatives: 1) only update modifyTimeStamp in response to actual Modify (and MoDDN) requests from a client. (thus, not for any internally generated updates.) 2) only update modifyTimeStamp if user attributes are changed. 3) always update modifyTimeStamp -- -- Howard Chu Chief Architect, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

3 3

BDB 4.6 is out
by Quanah Gibson-Mount 24 Jul '07

24 Jul '07

This release showed amazing promise in the past as the first release to move to after 4.2 that showed real performance gains across the board. Curious to see if the official release will hold up. --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

4 11

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-devel