- openldap-bugs - openldap.org

(ITS#5050) array bounds violation in test045-syncreplication-proxied
by h.b.furuseth＠usit.uio.no 18 Jul '07

18 Jul '07

Full_Name: Hallvard B Furuseth Version: HEAD, RE23 OS: Linux URL: Submission from: (NULL) (129.240.202.105) Submitted by: hallvard syncprov + back-ldap, and presumably + back-meta if that were used, give an array bounds violation in test045-syncreplication-proxied: syncprov_db_open() uses connection_fake_init(), which sets op->o_tag=0. It passes op to back-ldap. ldap_back_op_result() assumes op is a known LDAP request: It calls slap_req2op() and gets SLAP_OP_LAST (for unknown tag). That is used as an index into ldapinfo_t.li_timeout[], which has size SLAP_OP_LAST. back-meta/bind.c does the same in meta_back_bind_op_result() and meta_back_op_result(). HEAD backtrace, from an assert(0) I put in slap_req2op(): #3 0x003d8d91 in __assert_fail () from /lib/tls/libc.so.6 #4 0x0809ac0e in slap_req2op (tag=0) at operation.c:203 #5 0x0816dba8 in ldap_back_op_result (lc=0x83a12f8, op=0xbfffe948, rs=0xbfffe70c, msgid=1, timeout=-1, sendok=20) at bind.c:1582 #6 0x0816d727 in ldap_back_dobind_int (lcp=0xbfffe760, op=0xbfffe948, rs=0xbfffe70c, sendok=LDAP_BACK_GETCONN, retries=0, dolock=1) at bind.c:1411 #7 0x0816d814 in ldap_back_dobind (lcp=0xbfffe760, op=0xbfffe948, rs=0xbfffe70c, sendok=LDAP_BACK_DONTSEND) at bind.c:1440 #8 0x0812921a in ldap_back_entry_get (op=0xbfffe948, ndn=0x833b2a8, oc=0x0, at=0x82ec610, rw=0, ent=0xbfffe944) at search.c:790 #9 0x080f7a55 in overlay_entry_get_ov (op=0xbfffe948, dn=0x833b2a8, oc=0x0, ad=0x82ec610, rw=0, e=0xbfffe944, on=0x0) at backover.c:365 #10 0x081bd9da in syncprov_db_open (be=0x833a8a0) at syncprov.c:2550 #11 0x080f70b2 in over_db_func (be=0x833a8a0, which=db_open) at backover.c:61 #12 0x080f74c9 in over_db_open (be=0x833a8a0) at backover.c:174 #13 0x08092515 in backend_startup_one (be=0x833a8a0) at backend.c:212 #14 0x080929a2 in backend_startup (be=0x833a8a0) at backend.c:303 #15 0x080b9a94 in slap_startup (be=0x0) at init.c:243 #16 0x0806719d in main (argc=8, argv=0xbfffef14) at main.c:919

1 0

(ITS#5049) uninitialized Connection in syncprov
by h.b.furuseth＠usit.uio.no 18 Jul '07

18 Jul '07

Full_Name: Hallvard B Furuseth Version: HEAD, RE23 OS: Linux URL: Submission from: (NULL) (129.240.202.105) Submitted by: hallvard syncprov_db_close() does not initialize 'conn' before passing it to connection_fake_init(). (That function is a bit misnamed - the passed connection must be initialized, but not the passed operation.) Fixing in HEAD. Is RE23 frozen now?

1 0

(ITS#5048) Suspicious use of 'unchecked' limit syncprov
by h.b.furuseth＠usit.uio.no 18 Jul '07

18 Jul '07

Full_Name: Hallvard B Furuseth Version: HEAD, RE23 OS: URL: Submission from: (NULL) (129.240.202.105) Submitted by: hallvard overlays/syncprov.c:syncprov_findcsn() sets an unchecked limit to 1. findcsn_cb() says /* We just want to know that at least one exists, so it's OK if * we exceed the unchecked limit or size limit. */ This looks like it can return a false positive if two or more other entries which the filter would eliminate have the same hash as the value syncprov searches for. Also syncprov_findcsn() passes fc_limits uninitialized outside of the .lms_s_unchecked field to slapd. Valgrind complains in test018 about .lms_s_pr_hide in back-bdb/search.c:bdb_search(). Tested in HEAD.

1 0

(ITS#5046) ITS auto-reply and copyright date
by ghenry＠OpenLDAP.org 14 Jul '07

14 Jul '07

Full_Name: Gavin Henry Version: OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (212.159.59.85) Submitted by: ghenry ITS auto-reply needs updating: "Copyright 1998-2006 The OpenLDAP Foundation, All Rights Reserved."

1 0

(ITS#5045) collect.c and Dynamic Config
by ghenry＠OpenLDAP.org 14 Jul '07

14 Jul '07

Full_Name: Gavin Henry Version: HEAD OS: N/A URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (212.159.59.85) Submitted by: ghenry Dear all, I think if collect.c is still to be used as demonstration of overlay code in 2.4, then it needs some of the usual ConfigDriver/ConfigTable/ConfigOCs stuff. Would be useful for new contributors etc. Saying that, there is no harm in others reviewing existing overlays. Just some thoughts. Gavin.

1 0

Re: (ITS#5044) slapd: rdwr.c:256: ldap_pvt_thread_rdwr_runlock: Assertion `rw->ltrw_r_active >= 0' failed
by h.b.furuseth＠usit.uio.no 13 Jul '07

13 Jul '07

Do you use "database ldbm" in slapd.conf? The LDAP Compare operation can make it crash that way. (Since OpenLDAP 2.3.16; back-ldbm/compare.c rev 1.53.) I've committed a fix: http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/back-ldbm/Attic/comp… BDB more reliable. LDBM has been removed in OpenLDAP 2.4. -- Regards, Hallvard

1 0

Re: (ITS#5044) slapd: rdwr.c:256: ldap_pvt_thread_rdwr_runlock: Assertion `rw->ltrw_r_active >= 0' failed
by hyc＠symas.com 13 Jul '07

13 Jul '07

alexander.kasper(a)ruhr-uni-bochum.de wrote: > Full_Name: Alexander Kasper > Version: @(#) $OpenLDAP: slapd 2.3.36 (Jul 6 2007 14:15:37) $ > OS: Linux version 2.6.18-xendomU (root@localhost) (gcc version 4.1.1 (Gentoo 4.1.1-r3)) #3 SMP > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (134.147.48.236) > > > I cannot clearly reproduce the error/assert > > slapd: rdwr.c:256: ldap_pvt_thread_rdwr_runlock: Assertion `rw->ltrw_r_active >= > 0' failed > > since the slapd dies randomly. I'm runnig it on a virtual xen userDomain in > 64Bit mode. > > plz tell me, which debug-level would be fine, since -d 65535 produce 10MB output > for one search, and as i said slapd dies randomly. There are reports that Xen does not properly support mutexes. As such, it cannot be used to run slapd. http://www.openldap.org/lists/openldap-software/200603/msg00207.html -- -- 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

(ITS#5044) slapd: rdwr.c:256: ldap_pvt_thread_rdwr_runlock: Assertion `rw->ltrw_r_active >= 0' failed
by alexander.kasper＠ruhr-uni-bochum.de 13 Jul '07

13 Jul '07

Full_Name: Alexander Kasper Version: @(#) $OpenLDAP: slapd 2.3.36 (Jul 6 2007 14:15:37) $ OS: Linux version 2.6.18-xendomU (root@localhost) (gcc version 4.1.1 (Gentoo 4.1.1-r3)) #3 SMP URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (134.147.48.236) I cannot clearly reproduce the error/assert slapd: rdwr.c:256: ldap_pvt_thread_rdwr_runlock: Assertion `rw->ltrw_r_active >= 0' failed since the slapd dies randomly. I'm runnig it on a virtual xen userDomain in 64Bit mode. plz tell me, which debug-level would be fine, since -d 65535 produce 10MB output for one search, and as i said slapd dies randomly. greets Alex

1 0

Re: (ITS#5028) incomplete slapcat docs
by ghenry＠suretecsystems.com 13 Jul '07

13 Jul '07

<quote who="ghenry(a)suretecsystems.com"> > <quote who="h.b.furuseth(a)usit.uio.no"> >> hyc(a)symas.com writes: >>> steve(a)stevenwills.com wrote: >>>> The slapcat man page says in the Limitations section: >>>> >>>> In general, your slapd(8) should not be running (at least, not >>>> in >>>> read-write mode) when you do this to ensure consistency of the >>>> database. >>>> (...) >>> Given that back-ldbm has been deleted for 2.4, I guess we can just >>> delete this sentence. >> >> It could produce garbage data with back-ldif, and with some foreign >> database module. I think it should say it's safe with bdb (and null). >> Could copy it to the slapd-bdb(5) too. (I don't suggest to make >> slapcat(8) refer the user to that, since there is only one example >> anyway.) > > Obviously hdb too. Would it produce garbage on 2.4? Do we want to do anything with this for .37? > >> >> -- >> Regards, >> Hallvard >> >> >> > > >

1 0

Re: (ITS#5043) double free in slapo-rwm when rewriting search filters
by ando＠sys-net.it 12 Jul '07

12 Jul '07

Fixed in HEAD/re23 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

(ITS#5043) double free in slapo-rwm when rewriting search filters
by ando＠sys-net.it 12 Jul '07

12 Jul '07

Full_Name: Pierangelo Masarati Version: HEAD/re23 OS: irrelevant URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (81.72.89.40) Submitted by: ando See subject; a fix is coming.

1 0

(ITS#5042) Contribution: Active Directory Password Cache
by s.hetze＠linux-ag.de 12 Jul '07

12 Jul '07

Full_Name: Sebastian Hetze Version: 2.3.30 OS: Linux URL: ftp://ftp.openldap.org/incoming/Sebastian-Hetze-pgk-070712.tgz Submission from: (NULL) (212.21.78.130) Hi *, in your FTP incoming you find a piece of software that we would like to contribute to the slapd-modules collection. We hope you find it useful and we would very much like to receive feedback about useability, ideas for improvements and (in the very unlikely case of occurance ;-) bugreports and fixes. Best regards Sebastian Hetze ------------------------------------------------------------------------------------ Active Directory Password Cache =============================== Active Directory does not provide any means to read user credentials on any public API. It is possible, to install additional libraries as password sniffer to catch and forward cleartext passwords on changes. In case you cannot or simply dont want to install such libraries, the Active Directory Password Cache overlay is your option. The Active Directory Password Cache overlay allows to mirror user account credentials without any modification on the AD server. It only takes one occasional simple bind authentication against the OpenLDAP server. If the credential has not been mirrored yet, the overlay uses the krbPrincipalName and the password provided by the user to perform a Kerberos init against the Active Directory. A successful Kerberos init guarantees a correct password for this principal, and therefor the bind finally succeeds. Within this overlay operation, the password gets encrypted with the default OpenLDAP hash alorithm and stored as userPassword attribute. There is an option to update the sambaNTPassword also (using code borrowed from Howard Chu's smbk5pwd overlay). All following simple bind authentications will first try these cached credentials, making the OpenLDAP server independent from AD. In case the user changes its password on the Active Directory server, the old password stays valid in OpenLDAP until the user first presents the new password for an simple bind. Within this bind operation, the overlay performs another Kerberos init and updates the cached credentials in OpenLDAP.

1 0

Can't delete user using DN (Error 32) or add user using DN (Error 68)
by Chase Putans 12 Jul '07

12 Jul '07

I am not sure this is actually a bug, but I figure I will submit this anyways. We had a power outage some time ago, and the bdb files got corrupted. I ran a slapindex after shutting down and it seems one entry is now missing. I have tried re-adding it, but when I do that, I get an error that this entry already exists. When I try and delete with that particular DN, it says that it does not exist. This is openldap 2.2.29-1 installed via Yum on FC4. [root@PDC]# ldapadd -D "<ROOT DN>" -x -W -f entrymods Enter LDAP Password: adding new entry "uid=<username>,ou=People,dc=3sixtygroup,dc=com" ldap_add: Already exists (68) [root@PDC]# ldapdelete -D "<ROOT DN>" -x -W -f entrymods2 Enter LDAP Password: Delete Result: No such object (32) Matched DN: ou=People,dc=3sixtygroup,dc=com Contents of entrymods is as follows: dn: uid=<username>,ou=People,dc=3sixtygroup,dc=com uid: <username> objectClass: top objectClass: person objectClass: organizationalPerson objectClass: inetOrgPerson objectClass: posixAccount objectClass: shadowAccount objectClass: sambaSamAccount cn: <username> sn: <username> givenName: <username> uidNumber: <uidnumber> gidNumber: <gidnumber> homeDirectory: /home/<username> loginShell: /bin/bash gecos: System User sambaLogonTime: 0 sambaLogoffTime: 2147483647 displayName: <username> sambaSID: <> sambaPrimaryGroupSID: <> sambaLogonScript: scripts\logon.bat sambaHomePath: \\PDC\<username> sambaHomeDrive: H: sambaAcctFlags: [U] Contents of entrymods2: uid=<username>,ou=People,dc=3sixtygroup,dc=com changetype: delete Any help would be much appreciated. Thanks. -- Chase Putans Systems Administrator / Programmer / Web Developer / Support The 3Sixty Group http://3sixtygroup.com Ph: 800-440-3967 Fax: 800-453-9683

2 4

Re: (ITS#4986) manageDSAit might control cause problems in database selection
by hyc＠symas.com 11 Jul '07

11 Jul '07

hyc(a)symas.com wrote: > Thinking back, I think the idea here is that you might have a set of nested > databases connected by referral entries. E.g., > > database ldbm > suffix dc=sub,dc=example,dc=com > > database ldbm > suffix dc=example,dc=com > > If you had an referral entry in the superior DB that pointed to the sub > database, you would need the manageDSAit control to be able to operate on the > referral entry. > > None of this really makes sense post 2.1 since subordinate/glue makes it > superfluous. > I'm going to rip all of that out. -- -- 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

Re: (ITS#4981) Try -lpthread before -pthread
by rra＠stanford.edu 11 Jul '07

11 Jul '07

Quanah Gibson-Mount <quanah(a)zimbra.com> writes: > I believe the circumstances that caused this ITS to be opened have > changed, is that correct? Yes, the underlying toolchain bug is now fixed and the ITS can be closed. Thanks for the check! -- Russ Allbery (rra(a)stanford.edu) <http://www.eyrie.org/~eagle/>

1 0

Re: (ITS#4981) Try -lpthread before -pthread
by quanah＠zimbra.com 11 Jul '07

11 Jul '07

Russ, I believe the circumstances that caused this ITS to be opened have changed, is that correct? --Quanah --On May 24, 2007 2:37:49 AM +0000 kurt(a)OpenLDAP.org wrote: > > On May 23, 2007, at 10:16 PM, rra(a)stanford.edu wrote: >> libtool does not pass -pthread through > > Our libtool does. But gcc might not do the right thing with it. > In that case, it's a gcc bug which should be reported to the gcc > folks. > > I believe using -lpthread over -pthread will cause more problems > than its worth. That is, the problems caused by the missing link > on some platforms is not nearly as bad as the caused by using > -lc instead of -lc_r on other platforms. > > -- Kurt > > -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Solaris Client
by daniel perez del campo 10 Jul '07

10 Jul '07

Hi, I have configurated openLdap in Debian, and it works well with Linux clients. But I want to authenticate a Solaris client against the Ldap server. I don't know how to do this. Could someone tell me what have I have to do?? Or some guide? I have looked for information in Google and I don't find anything clear. Thanks a lot, and sorry for my english. Dani _________________________________________________________________ Grandes éxitos, superhéroes, imitaciones, cine y TV... http://es.msn.kiwee.com/ Lo mejor para tu móvil.

3 2

Re: imporvement to slapo-constraint (ITS#4987)
by manu＠netbsd.org 07 Jul '07

07 Jul '07

Gavin Henry <ghenry(a)suretecsystems.com> wrote: > It would be best to move this dicussion to openldap-devel(a)openldap.org now. Let's go... Summarry: I've added a new feature to slapo-constraint for constraining a value attribute the the existing values of another attribute. The idea is that you can have a catalog of allowed values (eg: for titles: Mr, Mrs, Miss) and constraint an attribute to these values Before working further on this patch (style, dod), I'd like some feeback on: 1) the way it's implemented: is there rought bugs, or is the logic fine? 2) configuration syntax: do we keep this one or do we swtich to something else? Could someone comment on the patch? -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu(a)netbsd.org

1 0

Re: imporvement to slapo-constraint (ITS#4987)
by ghenry＠suretecsystems.com 07 Jul '07

07 Jul '07

<quote who="manu(a)netbsd.org"> >> Did you see http://www.openldap.org/devel/contributing.html > > Right, but before moving foward with appropriate style, documentation, > and so on, I'd like to have some input about the config syntax and the > way it's implemented. I had no feedback at all yet on that. It would be best to move this dicussion to openldap-devel(a)openldap.org now. Try raising a question again there. Gavin. > > -- > Emmanuel Dreyfus > http://hcpnet.free.fr/pubz > manu(a)netbsd.org > > >

1 0

Re: imporvement to slapo-constraint (ITS#4987)
by manu＠netbsd.org 07 Jul '07

07 Jul '07

> Did you see http://www.openldap.org/devel/contributing.html Right, but before moving foward with appropriate style, documentation, and so on, I'd like to have some input about the config syntax and the way it's implemented. I had no feedback at all yet on that. -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu(a)netbsd.org

1 0

start_tls while chasing referrals
by Bin Lu 06 Jul '07

06 Jul '07

Hi, I noticed the following bug fix in referral chasing http://bugzilla.padl.com/show_bug.cgi?id=210 This seems only to take care of the usage with pam ldap lib. What if the ldap connection is not from the pam lib? In that case, when an ldap operation reaches a referral point, would the new connection be consistent if the original connection is using TLS(and the referral url is not using ldaps)? Our test shows it is not. Please advice, if that is also a security hole? Regards, Wenwu

2 1

Re: (ITS#5041) ldapwhoami takes unused "user" arg
by ando＠sys-net.it 05 Jul '07

05 Jul '07

h.b.furuseth(a)usit.uio.no wrote: > ldapwhoami and "ldapexop whoami" take an unused command line > argument "user". The code has been there since rev 1.1. could be a leftover or something like that? In any case, just trimmed. 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

(ITS#5041) ldapwhoami takes unused "user" arg
by h.b.furuseth＠usit.uio.no 05 Jul '07

05 Jul '07

Full_Name: Hallvard B Furuseth Version: 1.1->current OS: URL: Submission from: (NULL) (129.240.6.233) Submitted by: hallvard ldapwhoami and "ldapexop whoami" take an unused command line argument "user". The code has been there since rev 1.1.

1 0

(ITS#5040) modifyTimestamp being updated on login (bind) failure
by dan.cushing＠netideasinc.com 05 Jul '07

05 Jul '07

Full_Name: Dan Cushing Version: 2.3.36 OS: Solaris 9 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (71.76.187.82) When running OpenLDAP with the ppolicy overlay, the modifyTimestamp for a user entry is updated if the user attempts to login (bind) with an incorrect password. This is happening because the password lockout feature is enabled and the operational attribute 'pwdFailureTime' is being updated. It seems like this results in a misleading modifyTimestamp. Is it intended that the modifyTimestamp attribute be updated when operational attributes are updated? To reproduce the issue, compile with the ppolicy overlay and enable password lockout. Below I've included the entries for a minimal policy.ldif file that I tested with. Then perform the following actions. 1) As the directory administrator execute the following search: ldapsearch -x -D "cn=Manager,o=testorg.com" -w password -b o=testorg.com uid=testuser pwdFailureTime modifyTimestamp. This will return something like "modifyTimestamp: 20070705142825Z" 2) As testuser execute the following search: ldapsearch -x -D "uid=testuser,o=testorg.com" -w correctPassword -b o=testorg.com uid=testuser modifyTimestamp. This will also return something like "modifyTimestamp: 20070705142825Z" 3) As testuser execute the following search (note the INCORRECT password): ldapsearch -x -D "uid=testuser,o=testorg.com" -w WRONGPassword -b o=testorg.com uid=testuser modifyTimestamp. This will also return something like "ldap_bind: Invalid credentials (49)" 4) As the directory administrator execute the following search: ldapsearch -x -D "cn=Manager,o=testorg.com" -w password -b o=testorg.com uid=testuser pwdFailureTime modifyTimestamp. This will return something like "pwdFailureTime: 20070705144735Z modifyTimestamp: 20070705144735Z". Note that the 'pwdFailureTime attribute has been created and the 'modifyTimestamp' attribute has been updated to the time that the bind attempt failed. Contents of my Standard policy file are ... dn: cn=Standard, ou=Policies, o=testorg.com pwdLockout: TRUE pwdMaxFailure: 3 objectClass: top objectClass: device objectClass: pwdPolicy pwdFailureCountInterval: 120 pwdLockoutDuration: 3600 cn: Standard pwdAttribute: userPassword

1 0

Re: (ITS#5035) Warning patrol
by ando＠sys-net.it 04 Jul '07

04 Jul '07

h.b.furuseth(a)usit.uio.no wrote: > #1. slapd/frontend.c:frontend_init() has the statement > if ( slap_known_controls ) > which is always true since slap_known_controls is an array. > Maybe it should be if ( slap_known_controls[0] )? > > Except... controls.c says slap_known_controls[0] == NULL, which is > not true - at least not at the time of the if-test above. What's > that about? Probably a leftover of a time when slap_known_controls was a pointer > #2. The return value from op->o_callback->sc_cleanup() is never > used. Should it be? I noticed because the pcache_op_cleanup() > function does not return anything. What should it return? two possibilities: a) ignore it: cleanup could occur too late, when response has already been returned to client; in this case a return code is there only because of the standard API b) handle it: cleanup return code could be usefully returned to caller if (a), then the return code can be safely ignored > #3. RE23 struct sync_cookie.rid and struct syncinfo_s.si_rid are > 'long', but are printed as 'int'. Could change the formats, but - > any reason not to instead change their types to 'int' as in HEAD? > I haven't looked at the HEAD syncrepl changes, so I don't know > what other issues might be involved. There should be no impact, since they're both limited to 0,999 > #4. bconfig.c: Integer overflow in (1 << (sizeof(int)*8 - 1)) in > slap_loglevel_get(). If anything else have been trusting signed > integer overflow to resemble unsigned integers, it's time to cease > that. The behaviour is undefined, and compilers make use of this > fact to optimize. > > The loglevel functions are confused about types anyway. They > collect masks in slap_mask_t, but the API uses an int for the > masks. Agree > Either the API should use slap_mask_t Agree > or masks should be > stored in (unsigned) ints. Not for 2.3, I think. Agree 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs