openldap-bugs

openldap-bugs@openldap.org

1 participants
20967 discussions

ITS#6512 BDB 5.0
by hyc＠symas.com 16 Feb '11

16 Feb '11

This was resolved by ITS#6698, support for BDB 5.x was released in 2.4.24. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#6834) Conversion to cn=config needs more detail
by hyc＠symas.com 16 Feb '11

16 Feb '11

andrew.findlay(a)skills-1st.co.uk wrote: > On Wed, Feb 16, 2011 at 11:50:21AM +0000, Andrew Findlay wrote: > >> Admin Guide Section 5.4. "Converting old style slapd.conf(5) file to cn=config >> format" suggests that it is enough to run a slapd tool with both -f and -F >> options to perform this conversion. While strictly true, this will almost >> certainly result in an un-manageable server because there is no rootPW set for >> cn=config. >> >> The attached patch provides guidance to avoid this trap. > > It would also be useful to copy the config database clause from > slapd-config(5) into the example in the Admin Guide: > > # set a rootpw for the config database so we can bind. > # deny access to everyone else. > dn: olcDatabase=config,cn=config > objectClass: olcDatabaseConfig > olcDatabase: config > olcRootPW: {SSHA}XKYnrjvGT3wZFQrDD5040US592LxsdLy > olcAccess: to * by * none That ACL is already the default. In an isolated example there's no need to specify it. (It is present in the slapd-config(5) example to ensure that it takes precedence over the olcFrontendConfig ACLs immediately above it.) -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#6833) LDAP hangs on Solaris
by tombolala＠gmx.de 16 Feb '11

16 Feb '11

Hi Quanah! sorry for the wrong release, I meant 2.4.22 of course. /Thomas -------- Original-Nachricht -------- > Datum: Wed, 16 Feb 2011 16:34:39 GMT > Von: quanah(a)zimbra.com > An: openldap-its(a)openldap.org > Betreff: Re: (ITS#6833) LDAP hangs on Solaris > --On Wednesday, February 16, 2011 11:37 AM +0000 tombolala(a)gmx.de wrote: > > > Full_Name: Thomas Bopp > > Version: 4.2.22 > > > I really need a solution for this problem. > > I suggest you list an actual OpenLDAP release. It's near impossible to > help you without that. > > --Quanah > > -- > > Quanah Gibson-Mount > Sr. Member of Technical Staff > Zimbra, Inc > A Division of VMware, Inc. > -------------------- > Zimbra :: the leader in open source messaging and collaboration > > -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

1 0

(ITS#6835) extend pwFailureTime timestamp to microsecond resolution to improve pwdMaxFailure enforcement
by brian-ldap＠starvingprogrammer.com 16 Feb '11

16 Feb '11

Full_Name: Brian Wasserman Version: 2.4.21-0ubuntu5.3 OS: Ubuntu 10.04 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (198.151.13.15) More than pwdMaxFailure attempts can be made before locking out an account if multiple attempts are made within the same second since it'll only log one pwdFailureTime per second. This is because the timestamp is stored in second resolution. Changing this timestamp to use microsecond resolution should minimize this limitation. In order to reproduce the problem by exceeding the number of max failures configured, just attempt to bind to a server with the policy below (or similar) multiple times per second with a valid user and observer the number of pwdFailureTime entries that are added to the given account. The account is locked after three pwdFailureTime entries are added, regardless of the number of actual attempts. Here's my policy configuration: dn: cn=Standard,ou=Policies,dc=local,dc=com cn: Standard description: Standard password policy. pwdAttribute: userPassword pwdCheckQuality: 1 pwdLockout: TRUE pwdMustChange: TRUE pwdAllowUserChange: TRUE pwdSafeModify: TRUE objectClass: device objectClass: pwdPolicy pwdInHistory: 3 pwdMaxFailure: 3 pwdMinLength: 8 pwdMaxAge: 7776000 pwdMinAge: 86400

1 0

sortvals oddity
by Andrew Elble 16 Feb '11

16 Feb '11

I've run into the following issue while trying to track down why we are occasionally seeing duplicate members/memberUids in our groups: Set the server up for "sortvals memberUid". Add a posixGroup without any memberUid attributes present. Adding new memberUid attributes to the group afterwards will result in them being unsorted until server restart. I'm shooting from the hip here - shouldn't attr_merge() (in attr.c) have something like the following? if ( *a == NULL ) { *a = attr_alloc( desc ); if (desc->ad_type->sat_flags & SLAP_AT_SORTED_VAL) { (*a)->a_flags |= SLAP_ATTR_SORTED_VALS; } } else { Thanks, Andy -- Andrew W. Elble aweits(a)discipline.rit.edu Infrastructure Engineer, Communications Technical Lead Rochester Institute of Technology PGP: BFAD 8461 4CCF DC95 DA2C B0EB 965B 082E 863E C912 CONFIDENTIALITY NOTE: The information transmitted, including attachments, is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy any copies of this information.

2 1

Re: (ITS#6833) LDAP hangs on Solaris
by quanah＠zimbra.com 16 Feb '11

16 Feb '11

--On Wednesday, February 16, 2011 11:37 AM +0000 tombolala(a)gmx.de wrote: > Full_Name: Thomas Bopp > Version: 4.2.22 > I really need a solution for this problem. I suggest you list an actual OpenLDAP release. It's near impossible to help you without that. --Quanah -- Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: (ITS#6834) Conversion to cn=config needs more detail
by andrew.findlay＠skills-1st.co.uk 16 Feb '11

16 Feb '11

On Wed, Feb 16, 2011 at 11:50:21AM +0000, Andrew Findlay wrote: > Admin Guide Section 5.4. "Converting old style slapd.conf(5) file to cn=config > format" suggests that it is enough to run a slapd tool with both -f and -F > options to perform this conversion. While strictly true, this will almost > certainly result in an un-manageable server because there is no rootPW set for > cn=config. > > The attached patch provides guidance to avoid this trap. It would also be useful to copy the config database clause from slapd-config(5) into the example in the Admin Guide: # set a rootpw for the config database so we can bind. # deny access to everyone else. dn: olcDatabase=config,cn=config objectClass: olcDatabaseConfig olcDatabase: config olcRootPW: {SSHA}XKYnrjvGT3wZFQrDD5040US592LxsdLy olcAccess: to * by * none Andrew -- ----------------------------------------------------------------------- | From Andrew Findlay, Skills 1st Ltd | | Consultant in large-scale systems, networks, and directory services | | http://www.skills-1st.co.uk/ +44 1628 782565 | -----------------------------------------------------------------------

1 0

(ITS#6834) Conversion to cn=config needs more detail
by andrew.findlay＠skills-1st.co.uk 16 Feb '11

16 Feb '11

Full_Name: Andrew Findlay Version: 2.4.24 OS: OpenSuSE 11.3 URL: ftp://ftp.openldap.org/incoming/afindlay-slapdconf2.sdf.20110216.diff Submission from: (NULL) (88.97.25.132) Admin Guide Section 5.4. "Converting old style slapd.conf(5) file to cn=config format" suggests that it is enough to run a slapd tool with both -f and -F options to perform this conversion. While strictly true, this will almost certainly result in an un-manageable server because there is no rootPW set for cn=config. The attached patch provides guidance to avoid this trap.

1 0

(ITS#6833) LDAP hangs on Solaris
by tombolala＠gmx.de 16 Feb '11

16 Feb '11

Full_Name: Thomas Bopp Version: 4.2.22 OS: Solaris 10 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (195.47.255.100) After approximately one week our LDAP stops working and hangs (we had this situation several times). We have the www.sunfreeware.com package of LDAP installed. It had a bunch of connection in CLOSE_WAIT state (indicating basically that a close request has come in but slapd did not serve it). Making a truss on the process showed all threads blocked on lwp_cond_wait. I really need a solution for this problem.

1 0

(ITS#6832) fix #elif statement
by naota＠elisp.net 16 Feb '11

16 Feb '11

Full_Name: Naohiro Aota Version: 2.4.23 OS: Gentoo/FreeBSD 8.0 URL: http://elisp.net/openldap.patch Submission from: (NULL) (125.102.92.74) There are some #elif statements like "#elif FOOBAR", which should be "#elif defined(FOOBAR)". These statements might cause build error like this: i686-gentoo-freebsd8.0-gcc -O2 -pipe -march=prescott --param l1-cache-size=16 --param l1-cache-line-size=64 -mtune=prescott -D_GNU_SOURCE -I../../include -I../../include -I/usr/include/db4.8 -I/usr/include/db4.8 -c -o detach.o detach.c detach.c:131:7: error: missing binary operator before token "long" gmake[2]: *** [detach.o] Error 1 gmake[2]: Leaving directory `/usr/tmp/portage/net-nds/openldap-2.4.23/work/openldap-2.4.23/libraries/liblutil' gmake[1]: *** [all-common] Error 1 gmake[1]: Leaving directory `/usr/tmp/portage/net-nds/openldap-2.4.23/work/openldap-2.4.23/libraries' gmake: *** [all-common] Error 1 Build Environment: Gentoo/FreeBSD 8.0 gcc 4.4.4 URL is a address of the patch to fix the statements.

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-bugs