openldap-bugs

openldap-bugs@openldap.org

1 participants
21001 discussions

Re: (ITS#7916) ppolicy doesn't set pwdAccountLockedTime
by quanah＠zimbra.com 06 Aug '14

06 Aug '14

--On Wednesday, August 06, 2014 11:26 AM +0000 anshman.osc(a)gmail.com wrote: > Full_Name: Anshuman > Version: 2.4.23 2.4.23 is 4+ years old. In addition, the ITS system is for filing bugs, not for asking usage questions. You need to (a) upgrade to a current release or (b) contact the vendor of your massively out of date packages. For (a), I suggest packages from either Symas or the LTB project if you are not able to build OpenLDAP yourself. This ITS will be closed. --Quanah -- Quanah Gibson-Mount Server Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

(ITS#7916) ppolicy doesn't set pwdAccountLockedTime
by anshman.osc＠gmail.com 06 Aug '14

06 Aug '14

Full_Name: Anshuman Version: 2.4.23 OS: RHEL 6.4 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (198.241.211.15) Hello, I am trying to get the ppolicy to lock account after N unsuccessful attempts. To accomplish this, I defined the overlay policy in slapd.conf, and also attached the pwdPolicySubentry to the user object. It is able to detect the password policy, because the number of times "pwdFailureTime" appears is always 1 less than the value I set for "pwdMaxFailure" in the password policy. So, if I set pwdMaxFailure=4, the count pwdFailureTime stops growing after 3. However, the pwdAccountLockedTime is never set. Up until release 2.3.x adding a rootdn entry to the slapd.conf solved this issue. But today we are trying to upgrade to 2.4.23, and this "fix" no longer works. Could someone please let me know what needs to be done to make this work? -- slapd.conf--- # Load dynamic backend modules: modulepath /usr/lib64/openldap moduleload ppolicy.la moduleload auditlog.la overlay ppolicy ppolicy_default "cn=Standard,ou=Policies,dc=mycompany,dc=com" ppolicy_use_lockout

1 0

Re: (ITS#7906) segv when changing olcDbDirectory with ppolicy running
by ebackes＠symas.com 05 Aug '14

05 Aug '14

> While testing out the new mdb_copy compaction, I tried switching a live instance > to use a different db path via MOD to change olcDbDirectory. > This results in repeatable segv in ppolicy.c:ppolicy_connection_destroy, where > conn refers to the correction making the change that is likely in the process of > disconnecting, and pwcons is NULL. There are more pwcons hits than just ppolicy_connection_destroy, looking for the others but at a minimum ppolicy_restrict. -- Emily Backes Symas Corporation ebackes(a)symas.com

1 0

Re: (ITS#7915) pcache and translucent crashes OL
by hyc＠symas.com 04 Aug '14

04 Aug '14

nvoutsin(a)gmail.com wrote: > Full_Name: Nikos Voutsinas > Version: 2.4.39 > OS: Debian > URL: http://users.uoa.gr/~nvoutsin/OpenLdap_ITS/add-trasnlucent(bdb)-pcache(bdb)… http://users.uoa.gr/~nvoutsin/OpenLdap_ITS/add-translucent(bdb)-pcache(bdb)… http://users.uoa.gr/~nvoutsin/OpenLdap_ITS/add-trasnlucent(bdb)-pcache%mdmd… http://users.uoa.gr/~nvoutsin/OpenLdap_ITS/add-translucent(bdb)-pcache(mdb)… http://users.uoa.gr/~nvoutsin/OpenLdap_ITS/add-trasnlucent(mdb)-pcache(mdb)… http://users.uoa.gr/~nvoutsin/OpenLdap_ITS/add-translucent(mdb)-pcache(mdb)… http://users.uoa.gr/~nvoutsin/OpenLdap_ITS/add-trasnlucent(mdb)-pcache(bdb)… http://users.uoa.gr/~nvoutsin/OpenLdap_ITS/add-translucent(mdb)-pcache(bdb)… > Submission from: (NULL) (5.54.11.83) Thanks for the report, fixed in git master. > The combination of translucent and pcache overlays crashes OL or makes it > unresponsive. Any attempt to modify an object on the replica by using the > following ldif: > > dn: uid=joe,dc=foo,dc=com > changetype: modify > add: description > description: first > - > > dn: uid=joe,dc=foo,dc=com > changetype: modify > replace: description > description: second > - > > cause OL to fail either during the modification or on the subsequent operation. > Specifically, OL behaves differently depending on the type of database backends > that are used for translucent and pcache DBs, as it is shown below: > > translucent db,pcache db: comment > bdb,bdb: freezes on the second modify op > bdb,mdb: crashes on the secend modify op (invalid pointer) > mdb,mdb: completes the modify ops. crashes on the first search on object > mdb,bdb: completes the modify ops. crashes, if not on the first, then on > subsequent op > > Attached files: a)the cn=config ldif for each of the above cases and b)the > corresponding debug output during the modification of the user object or if that > completes during the subsequent search on 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#7915) pcache and translucent crashes OL
by quanah＠zimbra.com 04 Aug '14

04 Aug '14

--On Monday, August 04, 2014 10:16 PM +0300 Nikos Voutsinas=20 <nvoutsin(a)gmail.com> wrote: > I am aware of #7587, however based on the release dates shouldn't > this=C2=A0fix be=C2=A0included in 2.4.39; I just told you specifically that the fix was made after 2.4.39 was=20 released. Again, please test current RE24. Thanks! --Quanah -- Quanah Gibson-Mount Server Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: (ITS#7915) pcache and translucent crashes OL
by nvoutsin＠gmail.com 04 Aug '14

04 Aug '14

--001a11364318a34ed604ffd1be1c Content-Type: text/plain; charset=UTF-8 I am aware of #7587, however based on the release dates shouldn't this fix be included in 2.4.39; On Monday, August 4, 2014, Quanah Gibson-Mount <quanah(a)zimbra.com> wrote: > --On Monday, August 04, 2014 1:04 AM +0000 nvoutsin(a)gmail.com wrote: > > Full_Name: Nikos Voutsinas >> Version: 2.4.39 >> OS: Debian >> > > This looks like a duplicate of ITS#7587. Can you please re-test with > current code from RE24 where this is fixed? > > Thanks! > > --Quanah > > > > -- > > Quanah Gibson-Mount > Server Architect > Zimbra, Inc. > -------------------- > Zimbra :: the leader in open source messaging and collaboration > --001a11364318a34ed604ffd1be1c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I am aware of #7587, however based on the release dates shouldn't this= =C2=A0fix be=C2=A0included in 2.4.39; On Monday, August= 4, 2014, Quanah Gibson-Mount <<a href=3D"mailto:quanah@zimbra.com">quan= ah(a)zimbra.com</a>> wrote: <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex">--On Monday, August 04, 2014 1:04 AM +0000 <= a>nvoutsin(a)gmail.com</a> wrote: <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"> Full_Name: Nikos Voutsinas Version: 2.4.39 OS: Debian </blockquote> This looks like a duplicate of ITS#7587. =C2=A0Can you please re-test with = current code from RE24 where this is fixed? Thanks! --Quanah -- Quanah Gibson-Mount Server Architect Zimbra, Inc. -------------------- Zimbra :: =C2=A0the leader in open source messaging and collaboration </blockquote> --001a11364318a34ed604ffd1be1c--

1 0

Re: (ITS#7915) pcache and translucent crashes OL
by quanah＠zimbra.com 04 Aug '14

04 Aug '14

--On Monday, August 04, 2014 1:04 AM +0000 nvoutsin(a)gmail.com wrote: > Full_Name: Nikos Voutsinas > Version: 2.4.39 > OS: Debian This looks like a duplicate of ITS#7587. Can you please re-test with current code from RE24 where this is fixed? Thanks! --Quanah -- Quanah Gibson-Mount Server Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

(ITS#7915) pcache and translucent crashes OL
by nvoutsin＠gmail.com 03 Aug '14

03 Aug '14

Full_Name: Nikos Voutsinas Version: 2.4.39 OS: Debian URL: http://users.uoa.gr/~nvoutsin/OpenLdap_ITS/add-trasnlucent(bdb)-pcache(bdb)… http://users.uoa.gr/~nvoutsin/OpenLdap_ITS/add-translucent(bdb)-pcache(bdb)… http://users.uoa.gr/~nvoutsin/OpenLdap_ITS/add-trasnlucent(bdb)-pcache%mdmd… http://users.uoa.gr/~nvoutsin/OpenLdap_ITS/add-translucent(bdb)-pcache(mdb)… http://users.uoa.gr/~nvoutsin/OpenLdap_ITS/add-trasnlucent(mdb)-pcache(mdb)… http://users.uoa.gr/~nvoutsin/OpenLdap_ITS/add-translucent(mdb)-pcache(mdb)… http://users.uoa.gr/~nvoutsin/OpenLdap_ITS/add-trasnlucent(mdb)-pcache(bdb)… http://users.uoa.gr/~nvoutsin/OpenLdap_ITS/add-translucent(mdb)-pcache(bdb)… Submission from: (NULL) (5.54.11.83) The combination of translucent and pcache overlays crashes OL or makes it unresponsive. Any attempt to modify an object on the replica by using the following ldif: dn: uid=joe,dc=foo,dc=com changetype: modify add: description description: first - dn: uid=joe,dc=foo,dc=com changetype: modify replace: description description: second - cause OL to fail either during the modification or on the subsequent operation. Specifically, OL behaves differently depending on the type of database backends that are used for translucent and pcache DBs, as it is shown below: translucent db,pcache db: comment bdb,bdb: freezes on the second modify op bdb,mdb: crashes on the secend modify op (invalid pointer) mdb,mdb: completes the modify ops. crashes on the first search on object mdb,bdb: completes the modify ops. crashes, if not on the first, then on subsequent op Attached files: a)the cn=config ldif for each of the above cases and b)the corresponding debug output during the modification of the user object or if that completes during the subsequent search on it.

1 0

Re: (ITS#7914) LMDB: MDB_DUPSORT and mdb_cursor_put(.., MDB_CURRENT) can put DB in illegal state
by h.b.furuseth＠usit.uio.no 03 Aug '14

03 Aug '14

On 03/08/14 20:13, hyc(a)symas.com wrote: > The recent doc changes are a bit over-zealous here. The only requirement is > that the new value would naturally sort into the same position. So yes, you > can store a value different than the old value. No, MDB_CURRENT does not update branch keys. That was the reason for those latest doc changes.

1 0

Re: (ITS#7914) LMDB: MDB_DUPSORT and mdb_cursor_put(.., MDB_CURRENT) can put DB in illegal state
by hyc＠symas.com 03 Aug '14

03 Aug '14

Max Bolingbroke wrote: > On 2 August 2014 17:43, Howard Chu <hyc(a)symas.com <mailto:hyc@symas.com>> wrote: > > Max Bolingbroke wrote: > > OK, that does make sense. So MDB_CURRENT is totally useless with > MDB_DUPSORT? > Since you are either pointing at the (k, v) pair already (so the put > will do > nothing) or you aren't (so the put will break the DB). > > > The feature would not exist if it were useless. > > > An alternative explanation for the existence of MDB_CURRENT could be that it > is useful without MDB_DUPSORT (which is certainly is!) but is useless with it > on. I take it from this remark that you do see some use for the combination of > the two options but I guess I must be too stupid to see what that is! > > I suppose that MDB_CURRENT might be useful with MDB_DUPSORT if you could use > it to replace the (key, value) pair being pointed to by the cursor with a > different (key, value) pair, so long as the LMDB user knew that the > replacement would not violate the LMDB invariant that duplicates must be > sorted and distinct. Though this use case "seems" to work with the current > implementation the docs certainly do not promise that this is supported. What defines a "match" depends on the comparison function. If you use a comparator that only uses a portion of the value then of course you can store different values that still match. Prefix comparison is the most obvious example. The recent doc changes are a bit over-zealous here. The only requirement is that the new value would naturally sort into the same position. So yes, you can store a value different than the old value. -- -- 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

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