openldap-bugs

openldap-bugs@openldap.org

1 participants
21093 discussions

(ITS#7942) memory leak in control parsing
by hyc＠openldap.org 17 Sep '14

17 Sep '14

Full_Name: Howard Chu Version: 2.4 OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (8.25.222.90) Submitted by: hyc A number of controls allocate additional structures in their parsing, stored in the op->o_controls[] array. Nothing cleans these up at the end of the operation. Usually these don't leak because they're allocated on the thread slab, but if the incoming request is large enough it can force them into regular malloc. Fix coming shortly.

1 0

(ITS#7941) crash in slap_bv2ad using repeated tags
by hyc＠openldap.org 17 Sep '14

17 Sep '14

Full_Name: Howard Chu Version: 2.4.x OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (8.25.222.90) Submitted by: hyc Fix coming shortly

1 0

Re: (ITS#6035) slapd requires restart after modifying olcAuthzRegexp
by ryan＠nardis.ca 16 Sep '14

16 Sep '14

Hi, Following up from <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761407#23>: This limitation seems to still exist (tried RE24 and master). Until it can be fixed, please document it clearly in slapd-config.5 (and maybe the admin guide too), as well as any related attrs if they also require a restart (olcAuthzPolicy?). It's surprising behaviour, since almost every other attribute does support online configuration. Proposed patch follows. thanks, Ryan diff --git a/doc/man/man5/slapd-config.5 b/doc/man/man5/slapd-config.5 index c5bf06f..7c39369 100644 --- a/doc/man/man5/slapd-config.5 +++ b/doc/man/man5/slapd-config.5 @@ -409,6 +409,10 @@ values can be specified to allow for multiple matching and replacement patterns. The matching patterns are checked in the order they appear in the attribute, stopping at the first successful match. +Note that changes to +.B olcAuthzRegexp +take effect the next time the server is started, not immediately upon +changing the configuration. .\".B Caution: .\"Because the plus sign + is a character recognized by the regular expression engine, .\"and it will appear in names that include a REALM, be careful to escape the

1 0

Re: (ITS#7940) Glue entry creation creates entries that cannot be found via ldapsearch filters
by quanah＠zimbra.com 16 Sep '14

16 Sep '14

--On Wednesday, September 17, 2014 3:08 AM +0100 Howard Chu <hyc(a)symas.com> wrote: > quanah(a)openldap.org wrote: >> Full_Name: Quanah Gibson-Mount >> Version: 2.4.39 >> OS: Linux 3.11 >> URL: ftp://ftp.openldap.org/incoming/ >> Submission from: (NULL) (75.111.58.125) >> >> >> Found this at a customer site. They loaded an LDIF file that had the >> child of an entry, but not the entry itself. slapadd then created a >> glue entry to account for this, however there some significant problems >> with this process >> >> a) The glue entry is not syntactically correct. There is no RDN value. >> >> b) It is impossible to use a filter with ldapsearch to find the entry. >> It appears the objectClass index is utterly broken. > > Works as designed. Closing this ITS. Even with -M, it appears impossible to find a specific glued entry, which is problematic when attempting to find if it indeed exists or not outside of a slapcat, or trying to parse (in this case) the 306 broken glued entries that exist in the DB. It would be useful to be able (with -M) to actually search for and find the specific entry so that the account management client can then proceed accordingly. Right now, a search for the specific entry results in error code 32, so then the account management software attempts to create it, which results in error code 68. The software then has no way to find the entry and decide if it needs modification or deletion. OTOH, it is entirely the clients fault for providing bad input, so I'm not sure how hard we should chase it. :P --Quanah -- Quanah Gibson-Mount Server Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: (ITS#7940) Glue entry creation creates entries that cannot be found via ldapsearch filters
by hyc＠symas.com 16 Sep '14

16 Sep '14

quanah(a)openldap.org wrote: > Full_Name: Quanah Gibson-Mount > Version: 2.4.39 > OS: Linux 3.11 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (75.111.58.125) > > > Found this at a customer site. They loaded an LDIF file that had the child of > an entry, but not the entry itself. slapadd then created a glue entry to > account for this, however there some significant problems with this process > > a) The glue entry is not syntactically correct. There is no RDN value. > > b) It is impossible to use a filter with ldapsearch to find the entry. It > appears the objectClass index is utterly broken. Works as designed. Closing this ITS. > > Example entry, and the child that created it: > > dn: uid=abcd,ou=people,dc=xxxx,dc=com,dc=uy > entryUUID: a326899a-ad0e-1033-8edf-d9cf7a32cf04 > creatorsName: cn=config > createTimestamp: 20140731145640Z > entryCSN: 20140731145640.037371Z#000000#002#000000 > modifiersName: cn=config%momodifyTimestamp: 20140731145640Z > objectClass: top > objectClass: glue > structuralObjectClass: glue > > dn: zimbraDataSourceName=Adinet,uid=abcd,ou=people,dc=xxxx,dc=com,dc=uy > objectClass: zimbraDataSource > objectClass: zimbraImapDataSource > .... > > As we can see, the glue entry has no RDN attribute at all. It is also > impossible to find this entry via ldapsearch; > > ldapsearch -x -LLL -D $zimbra_ldap_userdn -w $zimbra_ldap_password -H $ldap_url > -b "ou=people,dc=xxxx,dc=com,dc=uy" uid=abcd > [zimbra@ldap01 ~]$ > > [zimbra@ldap01 ~]$ ldapsearch -x -LLL -D $zimbra_ldap_userdn -w > $zimbra_ldap_password -H $ldap_url -b "ou=people,dc=xxxx,dc=com,dc=uy" > "(objectClass=glue)" 1.1 > [zimbra@ldap01 ~]$ > > > > -- -- 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#7939) Unable to filter on "(objectClass=glue)"
by hyc＠symas.com 16 Sep '14

16 Sep '14

quanah(a)openldap.org wrote: > Full_Name: Quanah Gibson-Mount > Version: 2.4.39 > OS: Linux 3.11 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (75.111.58.125) > > > When trying to find a set of broken entries, I found that it is impossible to > filter on objectClass=glue: > > [zimbra@ldap01 ~]$ ldapsearch -x -LLL -D $zimbra_ldap_userdn -w > $zimbra_ldap_password -H $ldap_url -b > "ou=people,dc=xxx,dc=xxx,dc=xxx%2%2"(objectClass=glue)" 1.1 > [zimbra@ldap01 ~]$ echo $? > 0 > > I am immediately returned to the prompt, and the error result is success (0). > Instead, I expect all the broken glue'd objects returned instead. Use the manageDSAit control. This works as designed, no bug, closing this ITS. -- -- 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

(ITS#7940) Glue entry creation creates entries that cannot be found via ldapsearch filters
by quanah＠openldap.org 16 Sep '14

16 Sep '14

Full_Name: Quanah Gibson-Mount Version: 2.4.39 OS: Linux 3.11 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (75.111.58.125) Found this at a customer site. They loaded an LDIF file that had the child of an entry, but not the entry itself. slapadd then created a glue entry to account for this, however there some significant problems with this process a) The glue entry is not syntactically correct. There is no RDN value. b) It is impossible to use a filter with ldapsearch to find the entry. It appears the objectClass index is utterly broken. Example entry, and the child that created it: dn: uid=abcd,ou=people,dc=xxxx,dc=com,dc=uy entryUUID: a326899a-ad0e-1033-8edf-d9cf7a32cf04 creatorsName: cn=config createTimestamp: 20140731145640Z entryCSN: 20140731145640.037371Z#000000#002#000000 modifiersName: cn=config%momodifyTimestamp: 20140731145640Z objectClass: top objectClass: glue structuralObjectClass: glue dn: zimbraDataSourceName=Adinet,uid=abcd,ou=people,dc=xxxx,dc=com,dc=uy objectClass: zimbraDataSource objectClass: zimbraImapDataSource .... As we can see, the glue entry has no RDN attribute at all. It is also impossible to find this entry via ldapsearch; ldapsearch -x -LLL -D $zimbra_ldap_userdn -w $zimbra_ldap_password -H $ldap_url -b "ou=people,dc=xxxx,dc=com,dc=uy" uid=abcd [zimbra@ldap01 ~]$ [zimbra@ldap01 ~]$ ldapsearch -x -LLL -D $zimbra_ldap_userdn -w $zimbra_ldap_password -H $ldap_url -b "ou=people,dc=xxxx,dc=com,dc=uy" "(objectClass=glue)" 1.1 [zimbra@ldap01 ~]$

1 0

Re: (ITS#7939) Unable to filter on "(objectClass=glue)"
by quanah＠zimbra.com 16 Sep '14

16 Sep '14

--On Wednesday, September 17, 2014 1:11 AM +0000 quanah(a)openldap.org wrote: > When trying to find a set of broken entries, I found that it is > impossible to filter on objectClass=glue: Never mind, the entries aren't even valid ldap entries. Closing this ITS. -- Quanah Gibson-Mount Server Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

(ITS#7939) Unable to filter on "(objectClass=glue)"
by quanah＠openldap.org 16 Sep '14

16 Sep '14

Full_Name: Quanah Gibson-Mount Version: 2.4.39 OS: Linux 3.11 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (75.111.58.125) When trying to find a set of broken entries, I found that it is impossible to filter on objectClass=glue: [zimbra@ldap01 ~]$ ldapsearch -x -LLL -D $zimbra_ldap_userdn -w $zimbra_ldap_password -H $ldap_url -b "ou=people,dc=xxx,dc=xxx,dc=xxx%2%2"(objectClass=glue)" 1.1 [zimbra@ldap01 ~]$ echo $? 0 I am immediately returned to the prompt, and the error result is success (0). Instead, I expect all the broken glue'd objects returned instead.

1 0

Re: (ITS#7780) constraint_attribute <attr> <size|count> 0 cause segfault
by ondra＠mistotebe.net 15 Sep '14

15 Sep '14

On Fri, Jan 10, 2014 at 04:40:39AM +0000, fumiyas(a)osstech.co.jp wrote: > If slapd.conf has the following config, slapd segfault at startup. > > overlay constraint > constraint_attribute memberUid size 0 > # or > constraint_attribute memberUid count 0 Hi, I've uploaded a fix to this issue and #7781 to ftp://ftp.openldap.org/incoming/Ondrej-Kuznik-20140915-ITS-7780-7781.tgz could you confirm it fixes the issues for you? The above patch is derived from OpenLDAP Software. All of the modifications to OpenLDAP Software represented in the above patches were developed by Ondřej Kuzník <ondra(a)mistotebe.net>. I have not assigned rights and/or interest in this work to any party. I, Ondřej Kuzník, hereby place the above modifications to OpenLDAP Software (and only these modifications) into the public domain. Hence, these modifications may be freely used and/or redistributed for any purpose with or without attribution and/or other notice. Cheers, Ondrej

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