openldap-bugs

openldap-bugs@openldap.org

1 participants
20960 discussions

(ITS#8520) Maximum number os entries
by teresarosado.net＠gmail.com 18 Oct '16

18 Oct '16

Full_Name: Teresa Rosado Version: 2015-11-15 OS: Win Xp URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (194.65.44.71) Dear Sirs, What is the maximum number of entries your OpenLDAP server can have on DB? What is the maximum number of entries your OpenLDAP server can return on ldapsearch command? BR Teresa

1 0

Re: (ITS#8406) LMDB: Assertion 'mc->mc_flags & C_INITIALIZED' with MDB_NEXT after mdb_cursor_del
by h.b.furuseth＠usit.uio.no 18 Oct '16

18 Oct '16

[Copied from IRC chat] The fix is wrong - this commit broke cursor tracking: 37081325f7356587c5e6 "ITS#8406 fix xcursors after cursor_del" Demo: mtest_rand -v -f700 -i3 -p0x1000 -r1276664687.3 It sets C_DEL on the wrong xcursor, one which is at a different key than the deleted key. Like this: put key1, data1 put[cursor] key2, data2 del key1, data1 Now [cursor].mx_cursor has C_DEL. This also breaks - probably the same bug: mtest_rand -v -c7 -f326 -p0x800 -r2712746413 -- Hallvard

1 0

Re: (ITS#8519) Mahesh
by quanah＠symas.com 17 Oct '16

17 Oct '16

--On Monday, October 17, 2016 2:17 PM +0000 maheshwar.reddy(a)secure-24.com wrote: > Full_Name: Maheshwar Reddy > Version: 2.4.4 > OS: CentOS 6.5 > URL: ftp://ftp.openldap.org/incoming/Mahesh The ITS system is for reporting bugs. Usage/help requests should be directed to the openldap-techincal(a)openldap.org mailing list. Please see <http://www.openldap.org/lists/> for more information. This ITS will be closed. Regards, Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

(ITS#8519) Mahesh
by maheshwar.reddy＠secure-24.com 17 Oct '16

17 Oct '16

Full_Name: Maheshwar Reddy Version: 2.4.4 OS: CentOS 6.5 URL: ftp://ftp.openldap.org/incoming/Mahesh Submission from: (NULL) (175.101.6.130) Dear Openldap Support, First of all thank for the open community, We have been using openldap since last 5 years. Right now we are trying to decommission older version of openldap and trying to build newversion. Prior to that we are testing the openldap functionality and we observed some issue while configuring. We have a Linux team, and they all are need ldap write access. I've created a group and provided a ldap write access to that group. But the people who belongs to that group they were unable to write the ldiff files. Attached information, kindly take look into it. you help would highly appreciated. # ldap_writers, access_control, redhot, redhot.com dn: cn=ldap_writers,ou=access_control,o=redhot,dc=redhot,dc=com cn: ldap_writers objectClass: organizationalRole description: Grants full LDAP write access roleOccupant: uid=maheshwar.reddy,ou=users,o=redhot,dc=redhot,dc=com [root@sal-lnx01 ~]# cat grantaccess.ldif dn: olcDatabase={2}bdb,cn=nonfig changetype: modify add: olcAccess olcAccess: to * by group/organizationalRole/roleOccupant="cn=ldap_writers,ou=access_control,o=redhot,dc=redhot,dc=com" write [root@sal-lnx01 ~]# ldapadd -Y EXTERNAL -H ldapi:/// -f grantaccess.ldif SASL/EXTERNAL authentication started SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth SASL SSF: 0 modifying entry "olcDatabase={2}bdb,cn=config" [root@sal-lnx01 ~]# slapcat -n0 | tail -n10 olcAccess: {1}to dn.base="" by * read olcAccess: {2}to * by dn="cn=Manager,dc=redhot,dc=com" write by * read olcAccess: {3}to * by group/organizationalRole/roleOccupant="cn=ldap_writers ,ou=access_control,o=redhot,dc=redhot,dc=com" write olcSuffix: dc=redhot,dc=com olcRootDN: cn=Manager,dc=redhot,dc=com entryCSN: 20161017124350.966527Z#000000#000#000000 modifiersName: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth modifyTimestamp: 20161017124350Z [root@sal-lnx01 ~]# ldapadd -x -W -D uid=maheshwar.reddy,ou=users,o=redhot,dc=redhot,dc=com -f test.ldif Enter LDAP Password: adding new entry "uid=srikanth.reddy,ou=users,o=redhot,dc=redhot,dc=com" ldap_add: Insufficient access (50) additional info: no write access to parent [root@sal-lnx01 ~]# cat test.ldif # srikanth.reddy, users, redhot.com dn: uid=srikanth.reddy,ou=users,o=redhot,dc=redhot,dc=com cn: Maheshwar objectClass: organizationalPerson objectClass: person objectClass: inetOrgPerson objectClass: posixAccount objectClass: top givenName: Maheshwar Reddy homeDirectory:2F2Fhome/srikanth.reddy loginShell: /bin/bash mail: srikanth.reddy(a)redhot.com sn: Reddy uid: srikanth.reddy uidNumber: 10001 gidNumber: 1000 userPassword: {SSHA}UQU2j5vBuGqjfTE3x+UlA2Ez1ENHAZ/Q

1 0

Re: (ITS#8505) LMDB vs. fork()
by lmb＠cloudflare.com 13 Oct '16

13 Oct '16

--001a1143758a2a3d2c053ec0c5a5 Content-Type: text/plain; charset=UTF-8 I obviously agree that fixing the problems you mention is worthwhile, it just so far doesn't really get me what I need: safe fork() + exec(). Well, or mdb_env_open() could take an > MDB_CLOEXEC flag which says to set FD_CLOEXEC on that FD too. > If I could get that I'd move off my soapbox immediately. I can contribute a patch if that sounds reasonable? -- Lorenz Bauer | Systems Engineer 25 Lavington St., London SE1 0NZ www.cloudflare.com --001a1143758a2a3d2c053ec0c5a5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>I obviously agree that fixing the problems you mentio= n is worthwhile, it just so far doesn't really get me what I need: safe= fork() + exec().<br></div><br><div class=3D"gmail_extra"><div class=3D"gma= il_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8= ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Well, or mdb_en= v_open() could take an<br> MDB_CLOEXEC flag which says to set FD_CLOEXEC on that FD too.<br></blockquo= te><div><br></div><div>If I could get that I'd move off my soapbox imme= diately. I can contribute a patch if that sounds reasonable?</div></div><di= v><br></div>-- <br><div class=3D"gmail_signature">Lorenz Bauer =C2=A0| =C2= =A0Systems Engineer<br>25 Lavington St., London SE1 0NZ<br><br><a href=3D"h= ttp://www.cloudflare.com" target=3D"_blank">www.cloudflare.com</a></div> </div></div> --001a1143758a2a3d2c053ec0c5a5--

1 0

Re: (ITS#8507) adding the syncprov overlay does not load the associated schema elements
by hyc＠symas.com 12 Oct '16

12 Oct '16

ryan(a)nardis.ca wrote: > On Thu, Sep 29, 2016 at 06:03:38PM +0000, elecharny(a)apache.org wrote: >> $ grep -ri "olcSpNoPresent" slapd.d >> $ ... You are never supposed to access the files within the slapd.d directory. > Actually slapd replaces the entire cn=schema entry at runtime. As far as > I can tell, the the cn=schema.ldif file on disk is never used. So it > would certainly be dangerous to rely on its contents for anything. Correct. -- -- 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#8507) adding the syncprov overlay does not load the associated schema elements
by elecharny＠gmail.com 12 Oct '16

12 Oct '16

Le 12/10/16 à 02:40, Ryan Tandy a écrit : > On Thu, Sep 29, 2016 at 06:03:38PM +0000, elecharny(a)apache.org wrote: >> $ grep -ri "olcSpNoPresent" slapd.d >> $ ... >> >> You can stop and restart the server, the attribute is still not present. > > It's system schema and not user schema, so I kind of expect this. The > behaviour is the same when cn=config is initialized using slapadd -n0. > > 'ldapsearch -s base cn=schema,cn=config' does show these attributes. > >> Going back to the slapd.conf file, add the module : >> >> ... >> # Uncomment the mululeloads as needed to enable additional >> # functionalityi when configured. NOTE: We package many >> # more modules options than those found below. >> moduleload back_mdb.la >> moduleload back_monitor.la >> moduleload syncprov.la # Added module >> ... >> >> and regenerate the slapd.d content : >> >> $ /etc/init.d/solserver stop >> $ rm -rf /opt/symas/etc/openldap/slapd.d/* >> $ /opt/symas/bin/slaptest -f /opt/symas/etc/openldap/slapd.conf -F >> /opt/symas/etc/openldap/slapd.d >> $ grep -ri "olcSpNoPresent" /opt/symas/etc/openldap/slapd.d >> slapd.d/cn=config/cn=schema.ldif:olcAttributeTypes: ( OLcfgOvAt:1.3 NAME >> 'olcSpNoPresent' DESC 'Omit Present >> slapd.d/cn=config/cn=schema.ldif: $ olcSpSessionlog $ olcSpNoPresent $ >> olcSpReloadHint ) ) >> $... >> >> This is problematic... > > If there is a bug, I'd say it's the fact that the converter does write > out these attributes. > > Actually slapd replaces the entire cn=schema entry at runtime. As far > as I can tell, the the cn=schema.ldif file on disk is never used. So > it would certainly be dangerous to rely on its contents for anything. I must say that I can't reproduce this behavious with the latest release, so I guess it was fixed since the test I did.

1 0

Re: (ITS#7384) Assert Crash in ppolicy_ctrls_cleanup
by ryan＠nardis.ca 12 Oct '16

12 Oct '16

Just noting that one way to reproduce this assert reliably is to bind to an existing entry, through the relay, with an incorrect password. The important part of the config is: database mdb suffix dc=example,dc=com [...] overlay ppolicy database relay suffix o=example overlay rwm rwm-suffixmassage o=example dc=example,dc=com overlay ppolicy Then, binding through the relay: $ ldapwhoami -x -D uid=test,o=example -w zzz -e ppolicy slapd: ppolicy.c:912: ctrls_cleanup: Assertion `rs->sr_ctrls != ((void *)0)' failed. Same as when someone accidentally attaches two ppolicy instances to a single database. Not totally sure, but I suspect it's wrong here too: I don't see what the ppolicy attached to the relay is supposed to add in this case. I guess in theory they could have different configuration? wrt. e.g. ppolicy_use_lockout, or even pwdLockout/pwdMustChange via a different ppolicy_default... Wondering if it would make sense for add_passcontrol to look for a ppolicy control already existing on the op, and try to fail gracefully if so, instead of hitting this on the way out. Binding to the same entry with the correct password... $ ldapwhoami -x -D uid=test,o=example -w test -e ppolicy currently hits the same segfault reported in ITS#7966.

1 0

Re: (ITS#8507) adding the syncprov overlay does not load the associated schema elements
by ryan＠nardis.ca 12 Oct '16

12 Oct '16

On Thu, Sep 29, 2016 at 06:03:38PM +0000, elecharny(a)apache.org wrote: >$ grep -ri "olcSpNoPresent" slapd.d >$ ... > >You can stop and restart the server, the attribute is still not present. It's system schema and not user schema, so I kind of expect this. The behaviour is the same when cn=config is initialized using slapadd -n0. 'ldapsearch -s base cn=schema,cn=config' does show these attributes. >Going back to the slapd.conf file, add the module : > >... ># Uncomment the mululeloads as needed to enable additional ># functionalityi when configured. NOTE: We package many ># more modules options than those found below. >moduleload back_mdb.la >moduleload back_monitor.la >moduleload syncprov.la # Added module >... > >and regenerate the slapd.d content : > >$ /etc/init.d/solserver stop >$ rm -rf /opt/symas/etc/openldap/slapd.d/* >$ /opt/symas/bin/slaptest -f /opt/symas/etc/openldap/slapd.conf -F >/opt/symas/etc/openldap/slapd.d >$ grep -ri "olcSpNoPresent" /opt/symas/etc/openldap/slapd.d >slapd.d/cn=config/cn=schema.ldif:olcAttributeTypes: ( OLcfgOvAt:1.3 NAME >'olcSpNoPresent' DESC 'Omit Present >slapd.d/cn=config/cn=schema.ldif: $ olcSpSessionlog $ olcSpNoPresent $ >olcSpReloadHint ) ) >$... > >This is problematic... If there is a bug, I'd say it's the fact that the converter does write out these attributes. Actually slapd replaces the entire cn=schema entry at runtime. As far as I can tell, the the cn=schema.ldif file on disk is never used. So it would certainly be dangerous to rely on its contents for anything.

1 0

Re: (ITS#8510) OpenLDAP Crash when using ppolicy
by ryan＠nardis.ca 12 Oct '16

12 Oct '16

Hi, On Mon, Oct 03, 2016 at 08:00:55AM +0000, poil(a)quake.fr wrote: >I have an openldap with a master-master replication >* Config directory is a HDB database >* Main directory (people/group/policy) is a MDB database > >When using ># ldapwhoami -x -H ldap://localhost -D uid=poil,ou=opople,dc=my,dc=test -W -e >ppolicy >LDAP crash > >When using ># ldapwhoami -x -H ldap://localhost -D uid=poil,ou=people,dc=my,dc=test -W >It's working There isn't enough information here to reproduce the issue. Please provide complete steps to reproduce starting from a clean installation, including the entire configuration and some example data that demonstrates the problem.

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