openldap-bugs

openldap-bugs@openldap.org

1 participants
20963 discussions

Re: (ITS#6727) ./scripts/test047-ldap: line 599: 26709 Segmentation fault
by michael＠stroeder.com 04 Dec '10

04 Dec '10

masarati(a)aero.polimi.it wrote: > h.b.furuseth(a)usit.uio.no wrote: >> Hopefully fixed with the latest ITS#6632/6720 commits. > > You mean ITS#6727, I guess. I fixed ITS#6720 (rwm.c 1.132 -> 1.133), > it looked unrelated. For me, ITS#6727 is now fixed with your patch. > Can you confirm, Michael? 30 test iterations without problems. Seems to be fixed now. Ciao, Michael.

1 0

(ITS#6734) Implment delta-sync based MMR
by quanah＠OpenLDAP.org 03 Dec '10

03 Dec '10

Full_Name: Quanah Gibson-Mount Version: 2.4.23 OS: NA URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (75.111.45.108) To help resolve ITS#6097, it would be helpful to have delta-sync MMR available. I'm mainly filing this bug for tracking.

1 0

Re: (ITS#6620) ppolicy: pwdChangedTime/userPassword delete issue.
by hyc＠symas.com 03 Dec '10

03 Dec '10

Hallvard B Furuseth wrote: > Howard Chu writes: >> h.b.furuseth(a)usit.uio.no wrote: >>> Thanks. Applied a similar patch to cvs HEAD, after fixing a memory leak. >>> >>> Reproducing the bug: >>> >>> userPassword can exist without pwdChangedTime if you bypass >>> ppolicy: Use slapadd to add an entry with userPassword, or add >>> it to a subtree with no policy and then configure a policy. >>> >>> Then set up ppolicy and use ldapmodify to delete userPassword. >> >> In that case the correct fix is to skip the pwdChangedTime attribute >> completely. > > Well, that's what this fix does in this particular code chunk: > Don't try to delete pwdChangedTime if it isn't there. > >> The ppolicy spec says that entries without pwdChangedTime are not >> subject to password expiration at all. > > Sounds like a different issue, but I don't see where it says that. > What I did find is > > 8.2.7. Policy State Updates > > If the value of either pwdMaxAge or pwdMinAge is non-zero, the server > updates the pwdChangedTime attribute on the entry to the current > time. > See the definition of pwdChangedTime, section 5.3.2: 5.3.2. pwdChangedTime This attribute specifies the last time the entry's password was changed. This is used by the password expiration policy. If this attribute does not exist, the password will never expire. -- -- 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

MemberOf out of sync on consumer[s]
by Yuri Bank 03 Dec '10

03 Dec '10

Hello, I've been putting this off for a while, but this is happening frequently enough that I think its time to ask for opinions on the bug I'm running into with OpenLDAP and the MemberOf overlay. Version: 2.4.23 Configuration: Single Provider, with 4 Consumers. It seems that when I add a new users on my provider, the MemberOf attribute disappears randomly for some users, on some ( not all ) consumer nodes. Everything in the DIT is in tact, and the changes made on my provider are replicated to the consumers correctly. The only issue here is with the memberof attribute. The only way for me to remedy this problem is to shutdown slapd on the affected consumer node, delete everything in /var/sun/slapd, and then start slapd again which then fully syncs with my provider with all memberof attributes in tact. My testing shows that this is triggered by making changes to to my LDAP groups/users on the provider node, but that is all I can find. Nothing in the logs gives me any clues as to what is happening. Has anyone experienced similar problems? Thanks, -Yuri Bank

2 1

Re: (ITS#6684) Patch for autogroup overlay
by ryans＠aweber.com 03 Dec '10

03 Dec '10

Just wanted to say that I've tested the patch Norbert submitted with 2.4.21 and 2.4.23, and it fixes the problems for me on both installations. Great job on the patch, Norbert. -Ryan

1 0

Re: (ITS#6727) ./scripts/test047-ldap: line 599: 26709 Segmentation fault
by masarati＠aero.polimi.it 03 Dec '10

03 Dec '10

h.b.furuseth(a)usit.uio.no wrote: > Hopefully fixed with the latest ITS#6632/6720 commits. You mean ITS#6727, I guess. I fixed ITS#6720 (rwm.c 1.132 -> 1.133), it looked unrelated. For me, ITS#6727 is now fixed with your patch. Can you confirm, Michael? Thanks, p.

1 0

Re: (ITS#6727) ./scripts/test047-ldap: line 599: 26709 Segmentation fault
by h.b.furuseth＠usit.uio.no 03 Dec '10

03 Dec '10

Hopefully fixed with the latest ITS#6632/6720 commits. -- Hallvard

1 0

(ITS#6733) LDAP_MEMORY_DEBUG issues
by h.b.furuseth＠usit.uio.no 03 Dec '10

03 Dec '10

Full_Name: Hallvard B Furuseth Version: 2.4.23 OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (129.240.6.233) Submitted by: hallvard With LDAP_MEMORY_DEBUG, - ber_memcalloc_x does not check for overflow. - LBER_MEM_JUNK and the ber_int_mem_hdr initializer get compiler warnings. Fixing.

1 0

Re: (ITS#6632) Core dump in test030 when using back-ldap
by h.b.furuseth＠usit.uio.no 03 Dec '10

03 Dec '10

Easily found with valgrind --track-origins=yes. Fixed in rwm.c rev 1.134. -- Hallvard

1 0

Re: (ITS#6731) Scrambled error strings from back-ldif
by h.b.furuseth＠usit.uio.no 03 Dec '10

03 Dec '10

Howard Chu writes: > It is not an error in ldif_back_add() since rs->sr_text is only used by > send_ldap_result(). Its value upon return from ldif_back_add is irrelevant. Okay. I wondered if overlays could do something strange, but that does seem wrong. Then this bug only affected modify and modrdn. -- Hallvard

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