openldap-devel

openldap-devel@openldap.org

1418 discussions

Re: commit: ldap/doc/man/man5 slapd-meta.5
by Pierangelo Masarati 14 Apr '08

14 Apr '08

ando(a)OpenLDAP.org wrote: > Log Message: > make pseudoroot-bind-defer TRUE by default (part of ITS#5440 fix) This is a change in a side-feature of back-meta, something that should not hurt in most cases, but definitely a change in the default behavior, established since back-meta was released. What's the best way to notify it? 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 4

slapo-dynlist improvement
by manu＠netbsd.org 12 Apr '08

12 Apr '08

Hello I'd like to use the slapo-dynlist overlay, to generate an automatically updated list of attributes onan object. My problem is that I want the attribute name to be different than the original: I have dn: cn=list,o=home objectClass: groupOfURLs cn: list memberURL: ldap:///o=home?foo?sub?(objectClass=fooClass) In slapd.conf: overlay dynlist dynlist-attrset groupOfURLs memberURL A search on cn=list,o=home gives me: dn: cn=list,o=home objectClass: groupOfURLs cn: list foo: value1 foo: value2 foo; value3 ... But I would like it to be displayed that way: dn: cn=list,o=home objectClass: groupOfURLs cn: list bar: value1 bar: value2 bar; value3 ... It seems this is not possible with current software (please correct me if I'm wrong). I propose a contribution to slapo-dynlist, to include attribute name remapping capability. In the config file, this qould be configured by extending the member-ad parameter: overlay dynlist dynlist-attrset groupOfURLs memberURL foo:bar Of course, for backward compatibility, dynlist-attrset groupOfURLs memberURL foo would still be equivalent to dynlist-attrset groupOfURLs memberURL foo:dn Opinions? -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu(a)netbsd.org

3 5

OpenLDAP Overlay API
by micky 11 Apr '08

11 Apr '08

Hello, exists a OpenLDAP API Documentation to develop a Overlay (like smbk5pwd)? We just started to explore the source-code (smbk5pwd.c), but we noticed that the struct's and function syntax aren't easy to unterstand - We need a description. Like the smbk5pwd module, we want to develop a analog module for Asterisk. -- Greets Michael

3 2

Proxied attribute descriptions initialization
by Jonathan Clarke 11 Apr '08

11 Apr '08

The feature introduced in 2.3 [1] to map undefined attributes from proxies as "proxied" attribute descriptions enables searches with filters using attributes that have no local definition. For example, given slapd with a back-ldap pointing to an Active Directory (AD) server, this features makes searches with a filter of "(samAccountName=login)" work with no extra configuration, and without explicitly adding samAccountName to local schema. However, such searches will be passed on to the AD server only if a previous search result contained the attributes in question (samAccountName) and was not based on a filter containing the attribute. Otherwise, the filter is considered invalid and replaced with "(?=undefined)" in the logs, and passed to the AD server as "(!(objectclass=*))". This means that the same search, on the same data, can return different results at different times, depending on whether or not a previous search had succeeded and returned given attribute (samAccountName). Currently, we have worked around this problem by either: - running a bogus ldapsearch just after starting slapd, that returns this attribute - adding the attribute description to a local schema What is the general opinion on working around this issue? Might there be a way to implement something that ensures this happens automatically? I'm thinking of delegating filter checking to proxied servers for ldap backends, or automatically fetching schemas from them... Any experience, ideas? Thanks in advance. Best regards, Jonathan [1]http://www.openldap.org/its/index.cgi/Software%20Enhancements?id=3959 -- Jonathan Clarke Open Source Software Assurance (OSSA) - Groupe LINAGORA 27 rue de Berri, 75008 Paris Tél: 01 58 18 68 28, fax: 01 58 18 68 29 http://www.linagora.com - http://www.08000linux.com

2 1

Socket-level timeouts?
by Chris Adams 11 Apr '08

11 Apr '08

We've noticed hard failures on both our Linux and Mac workstations when an LDAP server fails in a way which causes it to stop responding but leave a connection open (e.g. lock contention, disk failure). This usually ends up requiring the system to be rebooted because a key system process will probably have made a call which is waiting on a read() which might take days to fail. I've created a patch simply calls setsockopt() to set SO_SNDTIMEO| SO_RCVTIMEO when LDAP_OPT_NETWORK_TIMEOUT has been set. This appears to produce the desired result on Linux (both with pam_ldap and the ldap utilities) and OS X (within the DirectoryService plugin). Is there a drawback to this approach which I've missed? It appears that the issue has come up in the past but there's no solution that I can see (certainly nothing else uses socket-level timeouts). I'd like to find a solution for this as it's by far the biggest source of Linux downtime in our environment. Thanks, Chris

4 7

security-related gcc bug
by Michael Ströder 08 Apr '08

08 Apr '08

HI! Did anyone already take not of this? Are parts of OpenLDAP's code affected? [Bug c/27180] New: pointer arithmetic overflow handling broken http://gcc.gnu.org/ml/gcc-bugs/2006-04/msg01297.html US-CERT - Vulnerability Note VU#162289: gcc silently discards some wraparound checks http://www.kb.cert.org/vuls/id/162289 Ciao, Michael.

5 9

OpenLDAP Developer's Day - Dublin 2008 (early call for participation)
by Howard Chu 07 Apr '08

07 Apr '08

The OpenLDAP Project is tentatively planning on hosting a developers' day conference in Dublin, Ireland in late July / early August (most likely weekend of August 2-3, and August 4). Those interested in speaking at the conference are encouraged to contact <project(a)openldap.org> with a specific proposal (title, abstract, duration). Discounts will be available to speakers. A formal (and more widely distributed) call for participation will be made once conference details are firmed up a bit (like we fix the date...). Organizations interested in sponsoring this event are encouraged to contact project(a)openldap.org. Currently we've got an agreement with HEAnet to host the event, and Symas will be sponsoring some of the activity. At the moment it's been suggested that we conduct two events - an ODD conference with presentations as we've done in the past, and also a code-sprint where we all grind thru a bunch of code together. Feel free to email me with suggestions. -- -- 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/

2 1

glue entries
by Hallvard B Furuseth 01 Apr '08

01 Apr '08

What are glue entries and how do they work in OpenLDAP? The manageDSAit code in back-bdb is intertwined with is_entry_glue() calls which I don't know what to make of. The only glue I can see bdb create seems to be a fake entry named "" if that is the database suffix. And I don't see any mention of glue entries in other backends. -- Hallvard

2 1

Re: commit: ldap/servers/slapd/overlays auditlog.c
by Pierangelo Masarati 29 Mar '08

29 Mar '08

Rein Tollevik wrote: >> On a slightly related note, but I only noticed because it's near the >> patched lines - if sizeof(time_t) != sizeof(long) then the fprintf >> argument is going to break. I think you should simply keep stamp >> declared as long and let the compiler promote the return value from >> slap_get_time() if it needs to. > > Yes, that is a potential problem that should be fixed. Although I would > prefer it as an explicit cast, as that imho must better tells the random > reader that the programmer har thought about it. I.e, to keep stamp as > a long variable and cast the slap_get_time() return value, or as I would > prefer it to cast the stamp argument in the fprintf statements. I've fixed it the other way. I prefer to use types as they should, and only cast them for printing reasons, to make clear where the "hack" is. In this case, the sole purpose was printing it, so it would have been fine the other way 'round as well, though. 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

Re: commit: ldap/servers/slapd/overlays auditlog.c
by Howard Chu 29 Mar '08

29 Mar '08

ando(a)OpenLDAP.org wrote: > Update of /repo/OpenLDAP/pkg/ldap/servers/slapd/overlays > > Modified Files: > auditlog.c 1.17 -> 1.18 > > Log Message: > avoid system call when not needed (ITS#5441) On a slightly related note, but I only noticed because it's near the patched lines - if sizeof(time_t) != sizeof(long) then the fprintf argument is going to break. I think you should simply keep stamp declared as long and let the compiler promote the return value from slap_get_time() if it needs to. -- -- 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/

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-devel