- openldap-bugs - openldap.org

Re: (ITS#8997) openldap-nssov/back ldap segfault
by matt＠pallissard.net 28 Mar '19

28 Mar '19

--dtfibegrdp7hfoq4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On 2019-03-21T15:13:30, Pallissard, Matthew wrote: > On 2019-03-20T22:01:40, Howard Chu wrote: > > matt(a)pallissard.net wrote: > > > > > 2. Turning the log level to 0 /seems/ to make the issue go away. I'll report > > > back once I can confirm that. Follow up, turning the log level to 0 does *not* prevent these segfaults. Matt Pallissard --dtfibegrdp7hfoq4 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYIAB0WIQTvIUMPApUGn6YFkXl1uof+t048SQUCXJzSGQAKCRB1uof+t048 SWYnAQDjIXjPORzGof/8TpqzansV7PXn5pdMnRxU14gqMcXsrwD+LS2nEqUmslpE T4PWgWNKb0AY0eWcSNAj+klqAkolcAs= =8ONg -----END PGP SIGNATURE----- --dtfibegrdp7hfoq4--

1 0

(ITS#9000) memberOf value is lost when group DN is modified with only case change
by clement.oudot＠worteks.com 27 Mar '19

27 Mar '19

Full_Name: Clement OUDOT Version: 2.4.47 OS: GNU/Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (81.250.130.213) We use a very standard configuration with memberof overlay. The issue is very easy to reproduce : * Create a group with a user in an OpenLDAP server using memberof overlay * The user should now have the group DN in memberOf attribute * Rename the group to change its case, for example uppercase the first letter * The group has be renamed but was removed form user memberOf attribute The OpenLDAP log is the following: 5c9ba447 conn=1000 op=23 MODRDN dn="cn=memberoftest,ou=groups,dc=example,dc=com" 5c9ba447 conn=1000 op=23: memberof_value_modify DN="uid=coudot,ou=users,dc=example,dc=com" add memberOf="cn=memberofTEST,ou=groups,dc=example,dc=com" failed err=20 Seems it is because memberof try to add the new value before deleting the old one. As the values are the same when ignoring the case, the modification is rejected. I would say that doing the LDAP_SLIST_REMOVE before the LDAP_SLIST_INSERT_HEAD in memberof.c should be enough but I don't know if this is safe.

1 0

Re: (ITS#8999) telephoneNumberMatch crashed slapd
by hyc＠symas.com 26 Mar '19

26 Mar '19

thomassiegmund(a)gmx.de wrote: > Full_Name: Thomas Siegmund > Version: 2.4.47 > OS: OpenBSD > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (2a02:8106:22a:4b02:e76f:90a1:5b27:161e) > > > When importing/saving the following certificate as a userCertificate;binary, > slapd crashes when calling dnX509Normalize. > > Files: > telephoneNumberMatch.der > telephoneNumberMatch.ldif > telephoneNumberMatch.llog > > Thanks for the report. Fixed now in git master. -- -- 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#8999) telephoneNumberMatch crashed slapd
by thomassiegmund＠gmx.de 26 Mar '19

26 Mar '19

Full_Name: Thomas Siegmund Version: 2.4.47 OS: OpenBSD URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (2a02:8106:22a:4b02:e76f:90a1:5b27:161e) When importing/saving the following certificate as a userCertificate;binary, slapd crashes when calling dnX509Normalize. Files: telephoneNumberMatch.der telephoneNumberMatch.ldif telephoneNumberMatch.llog

1 0

(ITS#8998) ldapi:// with SASL_NOCANON -> Local error (-2)
by michael＠stroeder.com 25 Mar '19

25 Mar '19

Full_Name: Michael Str.der Version: 2.4.47 OS: openSUSE Tumbleweed URL: Submission from: (NULL) (213.240.182.56) Adding line SASL_NOCANON on to my ~/.ldaprc causes ldapwhoami to fail like this: $ ldapwhoami -H ldapi:// -Y EXTERNAL ldap_sasl_interactive_bind_s: Local error (-2) Using the full LDAPI path name just works as expected: $ ldapwhoami -H ldapi://%2frun%2fslapd%2fldapi -Y EXTERNAL SASL/EXTERNAL authentication started SASL username: gidNumber=1000+uidNumber=1000,cn=peercred,cn=external,cn=auth SASL SSF: 0 dn:cn=michael,dc=example,dc=com

1 0

Re: (ITS#8995) OpenLdap (SyncRepl + Mirror Mode) issue
by quanah＠symas.com 25 Mar '19

25 Mar '19

--On Monday, March 25, 2019 9:51 PM +0530 abhishek negi <abhisheknegi684(a)gmail.com> wrote: > > > Hi Quanah, > > > We tried with 2.4.47 as well. Unfortunately still getting the same issue. You will need to provide the full configurations for each node, minus passwords to look any further. --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

Re: (ITS#8995) OpenLdap (SyncRepl + Mirror Mode) issue
by abhisheknegi684＠gmail.com 25 Mar '19

25 Mar '19

--0000000000008204140584ecc1ed Content-Type: text/plain; charset="UTF-8" Hi Quanah, We tried with 2.4.47 as well. Unfortunately still getting the same issue. Any further suggestions, please support On Mon 25 Mar, 2019, 7:11 PM Quanah Gibson-Mount <quanah(a)symas.com wrote: > --On Monday, March 25, 2019 2:55 PM +0530 abhishek negi > <abhisheknegi684(a)gmail.com> wrote: > > > > > Hi Team, > > > > > > I tried replication with version 2.4.44 and still facing the same issue. > > Can you help me with it. > > I clearly stated to use the latest release, which as of this moment is > 2.4.47. There was a major focus on fixing replication related bugs in the > 2.4.45 and 2.4.46 releases. You need to upgrade further. > > --Quanah > > > -- > > Quanah Gibson-Mount > Product Architect > Symas Corporation > Packaged, certified, and supported LDAP solutions powered by OpenLDAP: > <http://www.symas.com> > > --0000000000008204140584ecc1ed Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"auto"><div>Hi Quanah,</div><div dir=3D"auto"><br></div><div dir= =3D"auto">We tried with 2.4.47 as well. Unfortunately still getting the sam= e issue.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Any further sug= gestions, please support<br><br><div class=3D"gmail_quote" dir=3D"auto"><di= v dir=3D"ltr">On Mon 25 Mar, 2019, 7:11 PM Quanah Gibson-Mount <<a href= =3D"mailto:quanah@symas.com">quanah(a)symas.com</a> wrote:<br></div><blockquo= te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so= lid;padding-left:1ex">--On Monday, March 25, 2019 2:55 PM +0530 abhishek ne= gi <br> <<a href=3D"mailto:abhisheknegi684@gmail.com" target=3D"_blank" rel=3D"n= oreferrer">abhisheknegi684(a)gmail.com</a>> wrote:<br> <br> ><br> > Hi Team,<br> ><br> ><br> > I tried replication with version 2.4.44 and still facing the same issu= e.<br> > Can you help me with it.<br> <br> I clearly stated to use the latest release, which as of this moment is <br> 2.4.47.=C2=A0 There was a major focus on fixing replication related bugs in= the <br> 2.4.45 and 2.4.46 releases.=C2=A0 You need to upgrade further.<br> <br> --Quanah<br> <br> <br> --<br> <br> Quanah Gibson-Mount<br> Product Architect<br> Symas Corporation<br> Packaged, certified, and supported LDAP solutions powered by OpenLDAP:<br> <<a href=3D"http://www.symas.com" rel=3D"noreferrer noreferrer" target= =3D"_blank">http://www.symas.com</a>><br> <br> </blockquote></div></div></div> --0000000000008204140584ecc1ed--

1 0

Re: (ITS#8995) OpenLdap (SyncRepl + Mirror Mode) issue
by quanah＠symas.com 25 Mar '19

25 Mar '19

--On Monday, March 25, 2019 2:55 PM +0530 abhishek negi <abhisheknegi684(a)gmail.com> wrote: > > Hi Team, > > > I tried replication with version 2.4.44 and still facing the same issue. > Can you help me with it. I clearly stated to use the latest release, which as of this moment is 2.4.47. There was a major focus on fixing replication related bugs in the 2.4.45 and 2.4.46 releases. You need to upgrade further. --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

Re: (ITS#8995) OpenLdap (SyncRepl + Mirror Mode) issue
by abhisheknegi684＠gmail.com 25 Mar '19

25 Mar '19

--000000000000c9eebd0584e6f502 Content-Type: text/plain; charset="UTF-8" Hi Team, I tried replication with version 2.4.44 and still facing the same issue. Can you help me with it. On Tue 19 Mar, 2019, 11:58 PM abhishek negi <abhisheknegi684(a)gmail.com wrote: > Okay. > Thanks for the help and support. > Hope issue gets resolve after upgradation. > > Thanks, > Abhishek > > On Tue 19 Mar, 2019, 11:10 PM Quanah Gibson-Mount <quanah(a)symas.com wrote: > >> --On Tuesday, March 19, 2019 3:33 PM +0530 abhishek negi >> <abhisheknegi684(a)gmail.com> wrote: >> >> > >> > Hi Quanah, >> > >> > >> > If want to replicate Production (DC) site with Recovery (DR) site at >> real >> > time without any time lag which replication,DB and openldap verison >> would >> > be best to implement. >> >> I've already stated you need to upgrade to the current OpenLDAP release. >> I >> do not know how to make that any clearer. Additionally, it would >> literally >> defy physics to have instantaneous replication. There will always be >> some >> amount of delay. >> >> I would generally recommend the current OpenLDAP release using back-mdb >> as >> the database engine and delta-syncrepl using refreshAndPersist. >> >> --Quanah >> >> -- >> >> Quanah Gibson-Mount >> Product Architect >> Symas Corporation >> Packaged, certified, and supported LDAP solutions powered by OpenLDAP: >> <http://www.symas.com> >> >> --000000000000c9eebd0584e6f502 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"auto">Hi Team,<div dir=3D"auto"><br></div><div dir=3D"auto">I t= ried replication with version 2.4.44 and still facing the same issue.</div>= <div dir=3D"auto">Can you help me with it.</div></div><br><div class=3D"gma= il_quote"><div dir=3D"ltr">On Tue 19 Mar, 2019, 11:58 PM abhishek negi <= <a href=3D"mailto:abhisheknegi684@gmail.com">abhisheknegi684(a)gmail.com</a> = wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e= x;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"auto"><div>Okay.= </div><div dir=3D"auto">Thanks for the help and support.</div><div dir=3D"a= uto">Hope issue gets resolve after upgradation.</div><div dir=3D"auto"><br>= </div><div dir=3D"auto">Thanks,</div><div dir=3D"auto">Abhishek</div><div d= ir=3D"auto"><br><div class=3D"gmail_quote" dir=3D"auto"><div dir=3D"ltr">On= Tue 19 Mar, 2019, 11:10 PM Quanah Gibson-Mount <<a href=3D"mailto:quana= h(a)symas.com" target=3D"_blank" rel=3D"noreferrer">quanah(a)symas.com</a> wrot= e:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo= rder-left:1px #ccc solid;padding-left:1ex">--On Tuesday, March 19, 2019 3:3= 3 PM +0530 abhishek negi <br> <<a href=3D"mailto:abhisheknegi684@gmail.com" rel=3D"noreferrer noreferr= er" target=3D"_blank">abhisheknegi684(a)gmail.com</a>> wrote:<br> <br> ><br> > Hi Quanah,<br> ><br> ><br> > If want to replicate Production (DC) site with Recovery (DR) site at r= eal<br> > time without any time lag which replication,DB and openldap verison wo= uld<br> > be best to implement.<br> <br> I've already stated you need to upgrade to the current OpenLDAP release= .=C2=A0 I <br> do not know how to make that any clearer.=C2=A0 Additionally, it would lite= rally <br> defy physics to have instantaneous replication.=C2=A0 There will always be = some <br> amount of delay.<br> <br> I would generally recommend the current OpenLDAP release using back-mdb as = <br> the database engine and delta-syncrepl using refreshAndPersist.<br> <br> --Quanah<br> <br> --<br> <br> Quanah Gibson-Mount<br> Product Architect<br> Symas Corporation<br> Packaged, certified, and supported LDAP solutions powered by OpenLDAP:<br> <<a href=3D"http://www.symas.com" rel=3D"noreferrer noreferrer noreferre= r" target=3D"_blank">http://www.symas.com</a>><br> <br> </blockquote></div></div></div> </blockquote></div> --000000000000c9eebd0584e6f502--

1 0

Re: (ITS#8997) openldap-nssov/back ldap segfault
by matt＠pallissard.net 21 Mar '19

21 Mar '19

--hs6rsxv3pygoehyq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On 2019-03-20T22:01:40, Howard Chu wrote: > matt(a)pallissard.net wrote: > > > 2. Turning the log level to 0 /seems/ to make the issue go away. I'll report > > back once I can confirm that. > > That would imply the SEGV is specifically due to a NULL pointer being passed in a Debug message. > If that's true, you should be able to reproduce this using whatever accounts aren't fully populated > with POSIX attributes. > > > A note on this; We do have a good handful of 'service accounts' that don't > > have all of the posix attributes in active directory. As such those entries do > > spam the logs a bit. I have a backtrace I can submit. What's the proper way of doing so? As there is ldap info in it I'd rather not have it publicly accessable. Matt Pallissard --hs6rsxv3pygoehyq Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYIAB0WIQTvIUMPApUGn6YFkXl1uof+t048SQUCXJQMhgAKCRB1uof+t048 SbqCAQDSEgiivcwR6cztHGogp+hn5+2pikvZ/djpH5XVkRBD7gD9EhqWRSW8QOeY yPjj8smWGuoO+nbF8VIoGm3Mtw4PCA8= =cG48 -----END PGP SIGNATURE----- --hs6rsxv3pygoehyq--

1 0

Re: (ITS#8997) openldap-nssov/back ldap segfault
by hyc＠symas.com 20 Mar '19

20 Mar '19

matt(a)pallissard.net wrote: > 2. Turning the log level to 0 /seems/ to make the issue go away. I'll report > back once I can confirm that. That would imply the SEGV is specifically due to a NULL pointer being passed in a Debug message. If that's true, you should be able to reproduce this using whatever accounts aren't fully populated with POSIX attributes. > A note on this; We do have a good handful of 'service accounts' that don't > have all of the posix attributes in active directory. As such those entries do > spam the logs a bit. -- -- 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#8997) openldap-nssov/back ldap segfault
by matt＠pallissard.net 20 Mar '19

20 Mar '19

Full_Name: Matthew Pallissard Version: 2.4.47 OS: Archlinux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (185.236.200.195) Hi, We're seeng a lot of segfaults on some of our busier HPC machines. These typically have hundreds of jobs landing on them at a given time. We use back-ldap with an nssov-overlay and pcache in front of Active Directory. This is Authorization only, authentication is handled via krb5. The relevant bits of slightly scrubbed config are at the bottom of this message. We notice two things; 1. this can be replicated semi-consistently; 1. stop slapd, ensure cache is empty 2. do something dumb like this > for i in {1..100}; do ./dumb.sh &; done > #!/bin/bash > # dumb.sh > while [[ 1 -ne 2 ]]; do > for i in $(getent passwd | cut -f 1 -d ':'); do > time id ${i} > done > done 3. start slapd 2. Turning the log level to 0 /seems/ to make the issue go away. I'll report back once I can confirm that. A note on this; We do have a good handful of 'service accounts' that don't have all of the posix attributes in active directory. As such those entries do spam the logs a bit. # config 2.4.47 dn: cn=module,cn=config objectClass: olcModuleList cn: module olcModulePath: /usr/lib/openldap olcModuleLoad: pcache olcModuleLoad: nssov olcModuleLoad: back_ldap olcModuleLoad: back_mdb dn: olcDatabase={1}ldap,cn=config objectClass: olcDatabaseConfig objectClass: olcLDAPConfig olcDatabase: {1}ldap olcSuffix: dc=ad,dc=domain,dc=edu olcAddContentAcl: FALSE olcLastMod: FALSE olcMaxDerefDepth: 15 olcReadOnly: FALSE olcSyncUseSubentry: FALSE olcMonitoring: FALSE olcRootDN: cn=ldap_rootdn,cn=config olcDbURI: "ldap://ad.domain.edu" olcDbStartTLS: none starttls=no olcDbACLBind: bindmethod=simple timeout=0 network-timeout=0 binddn="" crede ntials="" keepalive=0:0:0 olcDbIDAssertBind: mode=none flags=prescriptive,proxy-authz-non-critical bin dmethod=simple timeout=0 network-timeout=0 binddn="" credentials="" keepalive=0:0:0 olcDbIDAssertAuthzFrom: * olcDbRebindAsUser: FALSE olcDbChaseReferrals: FALSE olcDbTFSupport: no olcDbProxyWhoAmI: FALSE olcDbProtocolVersion: 3 olcDbSingleConn: FALSE olcDbCancel: abandon olcDbUseTemporaryConn: FALSE olcDbConnectionPoolMax: 16 olcDbSessionTrackingRequest: FALSE olcDbNoRefs: FALSE olcDbNoUndefFilter: FALSE olcDbOnErr: continue olcDbKeepalive: 0:0:0 structuralObjectClass: olcLDAPConfig dn: olcOverlay={0}nssov,olcDatabase={1}ldap,cn=config objectClass: olcOverlayConfig objectClass: olcNssOvConfig olcOverlay: {0}nssov olcNssSsd: group ldap:///dc=ad,dc=domain,dc=edu??sub?(objectClass=posi xGroup) olcNssSsd: passwd ldap:///dc=ad,dc=domain,dc=edu??sub?(objectClass=pos ixAccount) olcNssSsd: shadow ldap:///dc=ad,dc=domain,dc=edu??sub?(objectClass=sha dowAccount) olcNssMap: group uniqueMember member olcNssMap: passwd gecos title olcNssMap: passwd homeDirectory unixHomeDirectory olcNssPam: uid2dn olcNssPamMinUid: 0 olcNssPamMaxUid: 0 structuralObjectClass: olcNssOvConfig dn: olcOverlay={1}pcache,olcDatabase={1}ldap,cn=config objectClass: olcOverlayConfig objectClass: olcPcacheConfig olcOverlay: {1}pcache olcPcache: mdb 1000000 30 1000000 3600 olcPcacheAttrset: 0 uid userPassword uidNumber gidNumber gecos cn homeDirectory loginShell objectClass olcPcacheAttrset: 1 cn userPassword gidNumber memberUid objectClass member olcPcacheTemplate: "(&(objectclass=)(|(memberuid=)(member=)))" 1 3600 olcPcacheTemplate: "(&(objectclass=)(|(memberuid=)(uniquemember=)))" 1 3600 olcPcacheTemplate: "(&(objectclass=)(gidnumber=))" 1 3600 olcPcacheTemplate: "(&(objectclass=)(uidnumber=))" 0 3600 olcPcacheTemplate: "(&(objectclass=)(uid=))" 0 3600 olcPcacheTemplate: "(objectclass=)" 0 3600 olcPcacheTemplate: "(objectclass=)" 1 3600 olcPcachePosition: head olcPcacheMaxQueries: 10000000 olcPcachePersist: FALSE olcPcacheValidate: FALSE olcPcacheOffline: TRUE dn: olcDatabase={0}mdb,olcOverlay={1}pcache,olcDatabase={1}ldap,cn=config objectClass: olcMdbConfig objectClass: olcPcacheDatabase olcDatabase: {0}mdb olcDbDirectory: /var/lib/openldap/openldap-data olcDbNoSync: FALSE olcDbIndex: objectClass eq olcDbIndex: cn pres,eq,sub olcDbIndex: uid pres,eq,sub olcDbIndex: uidNumber eq olcDbIndex: gidNumber eq olcDbIndex: memberUid eq olcDbIndex: sn pres,eq,sub olcDbIndex: mail pres,eq,sub olcDbIndex: uniqueMember eq

1 0

(ITS#8996) Please supply a pkg-config file for libldap
by hugh.mcmaster＠outlook.com 20 Mar '19

20 Mar '19

Full_Name: Hugh McMaster Version: 2.4.47 OS: Debian URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (60.224.220.43) Dear maintainer, Automated detection of openldap (libldap) is more laborious than it needs to be. pkg-config is comfortably available everywhere these days, making it very attractive for easier development and detection of headers and libraries. It would be very helpful if openldap could supply a pkg-config (.pc) files for libldap. If you need a patch for this, please let me know. Thank you

1 0

Re: (ITS#8995) OpenLdap (SyncRepl + Mirror Mode) issue
by abhisheknegi684＠gmail.com 19 Mar '19

19 Mar '19

--000000000000e3b1ea058476ad43 Content-Type: text/plain; charset="UTF-8" Okay. Thanks for the help and support. Hope issue gets resolve after upgradation. Thanks, Abhishek On Tue 19 Mar, 2019, 11:10 PM Quanah Gibson-Mount <quanah(a)symas.com wrote: > --On Tuesday, March 19, 2019 3:33 PM +0530 abhishek negi > <abhisheknegi684(a)gmail.com> wrote: > > > > > Hi Quanah, > > > > > > If want to replicate Production (DC) site with Recovery (DR) site at real > > time without any time lag which replication,DB and openldap verison would > > be best to implement. > > I've already stated you need to upgrade to the current OpenLDAP release. > I > do not know how to make that any clearer. Additionally, it would > literally > defy physics to have instantaneous replication. There will always be some > amount of delay. > > I would generally recommend the current OpenLDAP release using back-mdb as > the database engine and delta-syncrepl using refreshAndPersist. > > --Quanah > > -- > > Quanah Gibson-Mount > Product Architect > Symas Corporation > Packaged, certified, and supported LDAP solutions powered by OpenLDAP: > <http://www.symas.com> > > --000000000000e3b1ea058476ad43 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"auto"><div>Okay.</div><div dir=3D"auto">Thanks for the help and= support.</div><div dir=3D"auto">Hope issue gets resolve after upgradation.= </div><div dir=3D"auto"><br></div><div dir=3D"auto">Thanks,</div><div dir= =3D"auto">Abhishek</div><div dir=3D"auto"><br><div class=3D"gmail_quote" di= r=3D"auto"><div dir=3D"ltr">On Tue 19 Mar, 2019, 11:10 PM Quanah Gibson-Mou= nt <<a href=3D"mailto:quanah@symas.com">quanah(a)symas.com</a> wrote:<br><= /div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le= ft:1px #ccc solid;padding-left:1ex">--On Tuesday, March 19, 2019 3:33 PM +0= 530 abhishek negi <br> <<a href=3D"mailto:abhisheknegi684@gmail.com" target=3D"_blank" rel=3D"n= oreferrer">abhisheknegi684(a)gmail.com</a>> wrote:<br> <br> ><br> > Hi Quanah,<br> ><br> ><br> > If want to replicate Production (DC) site with Recovery (DR) site at r= eal<br> > time without any time lag which replication,DB and openldap verison wo= uld<br> > be best to implement.<br> <br> I've already stated you need to upgrade to the current OpenLDAP release= .=C2=A0 I <br> do not know how to make that any clearer.=C2=A0 Additionally, it would lite= rally <br> defy physics to have instantaneous replication.=C2=A0 There will always be = some <br> amount of delay.<br> <br> I would generally recommend the current OpenLDAP release using back-mdb as = <br> the database engine and delta-syncrepl using refreshAndPersist.<br> <br> --Quanah<br> <br> --<br> <br> Quanah Gibson-Mount<br> Product Architect<br> Symas Corporation<br> Packaged, certified, and supported LDAP solutions powered by OpenLDAP:<br> <<a href=3D"http://www.symas.com" rel=3D"noreferrer noreferrer" target= =3D"_blank">http://www.symas.com</a>><br> <br> </blockquote></div></div></div> --000000000000e3b1ea058476ad43--

1 0

Re: (ITS#8995) OpenLdap (SyncRepl + Mirror Mode) issue
by quanah＠symas.com 19 Mar '19

19 Mar '19

--On Tuesday, March 19, 2019 3:33 PM +0530 abhishek negi <abhisheknegi684(a)gmail.com> wrote: > > Hi Quanah, > > > If want to replicate Production (DC) site with Recovery (DR) site at real > time without any time lag which replication,DB and openldap verison would > be best to implement. I've already stated you need to upgrade to the current OpenLDAP release. I do not know how to make that any clearer. Additionally, it would literally defy physics to have instantaneous replication. There will always be some amount of delay. I would generally recommend the current OpenLDAP release using back-mdb as the database engine and delta-syncrepl using refreshAndPersist. --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

Re: (ITS#8995) OpenLdap (SyncRepl + Mirror Mode) issue
by abhisheknegi684＠gmail.com 19 Mar '19

19 Mar '19

--00000000000026eeeb05846ec7bd Content-Type: text/plain; charset="UTF-8" Hi Quanah, If want to replicate Production (DC) site with Recovery (DR) site at real time without any time lag which replication,DB and openldap verison would be best to implement. Earlier in version 2.4.38 , we used syncrepl +mirror mode replication but getting some time-lag. Please suggest On Mon 18 Mar, 2019, 7:18 PM Quanah Gibson-Mount <quanah(a)symas.com wrote: > --On Monday, March 18, 2019 2:24 PM +0000 abhisheknegi684(a)gmail.com wrote: > > > Full_Name: abhishek negi > > Version: 2.4.38 > > Hello, > > The 2.4.38 release is over 5 years old. There have literally been > hundreds > of bugs fixed with replication since that time. Please upgrade to a > current, modern release. No replication related issues will be examined > around such an ancient build of OpenLDAP. > > <https://www.openldap.org/software/release/changes.html> > > 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> > > --00000000000026eeeb05846ec7bd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"auto">Hi Quanah,<div dir=3D"auto"><br></div><div dir=3D"auto">I= f want to replicate Production (DC) site with Recovery (DR) site at real ti= me without any time lag which replication,DB and openldap verison would be = best to implement.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Earli= er in version 2.4.38 , we used syncrepl +mirror mode replication but gettin= g some time-lag.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Please = suggest</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Mon 1= 8 Mar, 2019, 7:18 PM Quanah Gibson-Mount <<a href=3D"mailto:quanah@symas= .com">quanah(a)symas.com</a> wrote:<br></div><blockquote class=3D"gmail_quote= " style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">-= -On Monday, March 18, 2019 2:24 PM +0000 <a href=3D"mailto:abhisheknegi684@= gmail.com" target=3D"_blank" rel=3D"noreferrer">abhisheknegi684(a)gmail.com</= a> wrote:<br> <br> > Full_Name: abhishek negi<br> > Version: 2.4.38<br> <br> Hello,<br> <br> The 2.4.38 release is over 5 years old.=C2=A0 There have literally been hun= dreds <br> of bugs fixed with replication since that time.=C2=A0 Please upgrade to a <= br> current, modern release.=C2=A0 No replication related issues will be examin= ed <br> around such an ancient build of OpenLDAP.<br> <br> <<a href=3D"https://www.openldap.org/software/release/changes.html" rel= =3D"noreferrer noreferrer" target=3D"_blank">https://www.openldap.org/softw= are/release/changes.html</a>><br> <br> This ITS will be closed.<br> <br> Regards,<br> Quanah<br> <br> <br> --<br> <br> Quanah Gibson-Mount<br> Product Architect<br> Symas Corporation<br> Packaged, certified, and supported LDAP solutions powered by OpenLDAP:<br> <<a href=3D"http://www.symas.com" rel=3D"noreferrer noreferrer" target= =3D"_blank">http://www.symas.com</a>><br> <br> </blockquote></div> --00000000000026eeeb05846ec7bd--

1 0

Re: (ITS#8995) OpenLdap (SyncRepl + Mirror Mode) issue
by quanah＠symas.com 18 Mar '19

18 Mar '19

--On Monday, March 18, 2019 2:24 PM +0000 abhisheknegi684(a)gmail.com wrote: > Full_Name: abhishek negi > Version: 2.4.38 Hello, The 2.4.38 release is over 5 years old. There have literally been hundreds of bugs fixed with replication since that time. Please upgrade to a current, modern release. No replication related issues will be examined around such an ancient build of OpenLDAP. <https://www.openldap.org/software/release/changes.html> 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#8995) OpenLdap (SyncRepl + Mirror Mode) issue
by abhisheknegi684＠gmail.com 18 Mar '19

18 Mar '19

Full_Name: abhishek negi Version: 2.4.38 OS: Linux 6 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (182.77.13.52) PLease suggest a way to rectify the delay observed while replication. Below are the details: Replication used: SyncRepl + Mirror Mode (active-active setup) Replication Issue summary: Replication from DC-->DR is working fine with no time-lag b/w the packets/data. Facing issue with replication from DR--x-->DC setup. Sometimes, data/packets from DR flows with a delay to DC. This case doesn't follow any pattern, the setup works perfectly fine for 4-5 days, then suddenly packets/data flows with delay/time-lag. This delay is only observed from DR to DC. syncrepl rid=841 provider=ldap://<DC-IP>:389 bindmethod=simple binddn="cn=root,ou=test,o=test1,c=in" credentials=XXXXXXXXXXX searchbase="ou=test,o=test1,c=in" schemachecking=on attrs=* interval=00:00:00:10 type=refreshAndPersist retry="5 5 300 5" syncrepl rid=842 provider=ldap://<DR-IP>:389 bindmethod=simple binddn="cn=root,ou=test,o=test1,c=in" credentials=XXXXXXXXXXX searchbase="ou=test,o=test1,c=in" schemachecking=on attrs=* interval=00:00:00:10 type=refreshAndPersist retry="5 5 300 5" index entryCSN eq index entryUUID eq mirrormode TRUE overlay syncprov syncprov-checkpoint 100 10 syncprov-sessionlog 100

1 0

Re: (ITS#8992) LDAP Over TLS causing reload
by quanah＠symas.com 14 Mar '19

14 Mar '19

--On Thursday, March 14, 2019 10:47 AM +0000 soneshkumar.patel(a)tcs.com wrote: > Full_Name: Sonesh Patel > Version: 2.4.46 > OS: FreeBSD > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (45.249.219.13) > > > Hi, > > We have introduced LDAP client using OpenLDAP 2.4.46 on FreeBSD server > and we are using LibreSSL 2.3.6 to perform SSL operations. We are using > SSL_CTX_add_extra_chain_cert API to add CA certificate into SSL context > and connection to LDAP server is successful. OpenLDAP does not support LibreSSL. Any build of OpenLDAP compiled against LibreSSL was hacked into place and is not supported by the OpenLDAP project. If you can reproduce the same behavior using a supported TLS library (OpenSSL or GnuTLS), feel free to follow up. > We already sent mail to the forum (openldap-its(a)openldap.org) dated Fri 7 > Dec, 2018 but no response till now. The list is for traffic regarding existing ITSes. It is not a general email list. This ITS will be closed. --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

(ITS#8992) LDAP Over TLS causing reload
by soneshkumar.patel＠tcs.com 14 Mar '19

14 Mar '19

Full_Name: Sonesh Patel Version: 2.4.46 OS: FreeBSD URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (45.249.219.13) Hi, We have introduced LDAP client using OpenLDAP 2.4.46 on FreeBSD server and we are using LibreSSL 2.3.6 to perform SSL operations. We are using SSL_CTX_add_extra_chain_cert API to add CA certificate into SSL context and connection to LDAP server is successful. But when client initiate 100 parallel secure connection per second towards LDAP server by calling ldap_start_tls_s() API. FreeBSD server is going for Reload due to software exception reported from SSL library. We are using blocking socket to send and receive LDAP queries. With non-secure LDAP connection, client able to initiate 900 parallel connection towards LDAP server per second, but with secure LDAP connection, FreeBSD server is going for reload at 100 parallel connection per second itself. Does anyone observed similar issues with secure LDAP connection? We already sent mail to the forum (openldap-its(a)openldap.org) dated Fri 7 Dec, 2018 but no response till now. Appreciate for your response on above query. Regards, Sonesh

1 0

Re: (ITS#8991) Error while trying to create database with attribute olcSuffix in internationalized UTF-8 DN format.
by hyc＠symas.com 13 Mar '19

13 Mar '19

uneex(a)ya.ru wrote: > Full_Name: Varnava Sergey > Version: openldap-sasl-server-2.4.47 > OS: FreeBSD 12.0-RELEASE > URL: > Submission from: (NULL) (86.62.75.82) > > > slapd configured to use cn=config > > I'm trying to create database under cn=config with olcSuffix attribute set to DN > with international UTF-8 characters. > > `cat adddb.ldif` > dn: olcDatabase=mdb > objectClass: olcDatabaseConfig > objectClass: olcMdbConfig > olcDatabase: mdb > olcSuffix:: ZGM90KHQvtC70L3Ri9GI0LrQvixkYz3QlNGD0YDQlNC+0LwK > olcRootDN:: Y2490JTQuNGA0LXQutGC0L7RgCxkYz3QodC+0LvQvdGL0YjQutC+LGRjPdCU0YPRgNCU0L7QvAo= > olcRootPW:: e1NTSEF9ZHVyc2VjcmV0Cg== > olcDbIndex: objectClass eq > olcDbDirectory: /var/db/openldap-data > > When doing `ldapadd -x -w secret -f /root/adddb.ldif` > I'm getting this error: > > adding new entry "olcDatabase=mdb" > ldap_add: Invalid syntax (21) > additional info: olcSuffix: value #0 invalid per syntax Your DN is using "dc" attribute, whose syntax doesn't allow the characters you're using. This is not an OpenLDAP bug, this ITS will be closed. -- -- 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#8991) Error while trying to create database with attribute olcSuffix in internationalized UTF-8 DN format.
by uneex＠ya.ru 13 Mar '19

13 Mar '19

Full_Name: Varnava Sergey Version: openldap-sasl-server-2.4.47 OS: FreeBSD 12.0-RELEASE URL: Submission from: (NULL) (86.62.75.82) slapd configured to use cn=config I'm trying to create database under cn=config with olcSuffix attribute set to DN with international UTF-8 characters. `cat adddb.ldif` dn: olcDatabase=mdb objectClass: olcDatabaseConfig objectClass: olcMdbConfig olcDatabase: mdb olcSuffix:: ZGM90KHQvtC70L3Ri9GI0LrQvixkYz3QlNGD0YDQlNC+0LwK olcRootDN:: Y2490JTQuNGA0LXQutGC0L7RgCxkYz3QodC+0LvQvdGL0YjQutC+LGRjPdCU0YPRgNCU0L7QvAo= olcRootPW:: e1NTSEF9ZHVyc2VjcmV0Cg== olcDbIndex: objectClass eq olcDbDirectory: /var/db/openldap-data When doing `ldapadd -x -w secret -f /root/adddb.ldif` I'm getting this error: adding new entry "olcDatabase=mdb" ldap_add: Invalid syntax (21) additional info: olcSuffix: value #0 invalid per syntax Some debug from log file: ... Mar 13 20:32:00 ldap slapd[2181]: send_ldap_result: conn=1004 op=0 p=3 Mar 13 20:32:00 ldap slapd[2181]: send_ldap_response: msgid=1 tag=97 err=0 Mar 13 20:32:00 ldap slapd[2181]: daemon: activity on 1 descriptor Mar 13 20:32:00 ldap slapd[2181]: daemon: activity on: Mar 13 20:32:00 ldap slapd[2181]: 13r Mar 13 20:32:00 ldap slapd[2181]: Mar 13 20:32:00 ldap slapd[2181]: daemon: read activity on 13 Mar 13 20:32:00 ldap slapd[2181]: daemon: select: listen=6 active_threads=0 tvp=NULL Mar 13 20:32:00 ldap slapd[2181]: daemon: select: listen=7 active_threads=0 tvp=NULL Mar 13 20:32:00 ldap slapd[2181]: daemon: select: listen=8 active_threads=0 tvp=NULL Mar 13 20:32:00 ldap slapd[2181]: connection_get(13): got connid=1004 Mar 13 20:32:00 ldap slapd[2181]: connection_read(13): checking for input on id=1004 Mar 13 20:32:00 ldap slapd[2181]: op tag 0x68, time 1552498320 Mar 13 20:32:00 ldap slapd[2181]: conn=1004 op=1 do_add Mar 13 20:32:00 ldap slapd[2181]: daemon: activity on 1 descriptor Mar 13 20:32:00 ldap slapd[2181]: daemon: waked Mar 13 20:32:00 ldap slapd[2181]: daemon: select: listen=6 active_threads=0 tvp=NULL Mar 13 20:32:00 ldap slapd[2181]: daemon: select: listen=7 active_threads=0 tvp=NULL Mar 13 20:32:00 ldap slapd[2181]: daemon: select: listen=8 active_threads=0 tvp=NULL Mar 13 20:32:00 ldap slapd[2181]: >>> dnPrettyNormal: <olcDatabase=mdb> Mar 13 20:32:00 ldap slapd[2181]: <<< dnPrettyNormal: <olcDatabase=mdb>, <olcDatabase=mdb> Mar 13 20:32:00 ldap slapd[2181]: >>> dnPretty: <dc=Солн<D1>M-^K<D1>M-^Hко,dc=<D0>M-^T<D1>M-^C<D1>M-^@<D0>M-^Tом > Mar 13 20:32:00 ldap slapd[2181]: send_ldap_result: conn=1004 op=1 p=3 Mar 13 20:32:00 ldap slapd[2181]: send_ldap_response: msgid=2 tag=105 err=21 Mar 13 20:32:00 ldap slapd[2181]: daemon: activity on 1 descriptor Mar 13 20:32:00 ldap slapd[2181]: daemon: activity on: Mar 13 20:32:00 ldap slapd[2181]: 13r Mar 13 20:32:00 ldap slapd[2181]: Mar 13 20:32:00 ldap slapd[2181]: daemon: read activity on 13 Mar 13 20:32:00 ldap slapd[2181]: daemon: select: listen=6 active_threads=0 tvp=NULL Mar 13 20:32:00 ldap slapd[2181]: daemon: select: listen=7 active_threads=0 tvp=NULL Mar 13 20:32:00 ldap slapd[2181]: daemon: select: listen=8 active_threads=0 tvp=NULL Mar 13 20:32:00 ldap slapd[2181]: connection_get(13): got connid=1004 Mar 13 20:32:00 ldap slapd[2181]: connection_read(13): checking for input on id=1004 Mar 13 20:32:00 ldap slapd[2181]: op tag 0x42, time 1552498320 Mar 13 20:32:00 ldap slapd[2181]: ber_get_next on fd 13 failed errno=0 (No error: 0) Mar 13 20:32:00 ldap slapd[2181]: connection_read(13): input error=-2 id=1004, closing. Mar 13 20:32:00 ldap slapd[2181]: connection_closing: readying conn=1004 sd=13 for close Mar 13 20:32:00 ldap slapd[2181]: connection_close: deferring conn=1004 sd=13 Mar 13 20:32:00 ldap slapd[2181]: conn=1004 op=2 do_unbind Mar 13 20:32:00 ldap slapd[2181]: connection_resched: attempting closing conn=1004 sd=13 Mar 13 20:32:00 ldap slapd[2181]: connection_close: conn=1004 sd=13 Mar 13 20:32:00 ldap slapd[2181]: daemon: removing 13 Mar 13 20:32:00 ldap slapd[2181]: daemon: activity on 1 descriptor Mar 13 20:32:00 ldap slapd[2181]: daemon: waked Mar 13 20:32:00 ldap slapd[2181]: daemon: select: listen=6 active_threads=0 tvp=NULL Mar 13 20:32:00 ldap slapd[2181]: daemon: select: listen=7 active_threads=0 tvp=NULL Mar 13 20:32:00 ldap slapd[2181]: daemon: select: listen=8 active_threads=0 tvp=NULL ... Is it possible to solve this problem?

1 0

(ITS#7770) mdb_stat in cn=monitor
by michael＠stroeder.com 12 Mar '19

12 Mar '19

I'm currently testing this feature back-ported to RE24 branch. I noticed that these attributes are set to empty values: creatorsName: modifiersName: Rest of entry looks good: dn: cn=Database 1,cn=Databases,cn=Monitor objectClass: monitoredObject objectClass: olmMDBDatabase structuralObjectClass: monitoredObject cn: Database 1 creatorsName: modifiersName: createTimestamp: 20190312102553Z modifyTimestamp: 20190312102553Z monitoredInfo: mdb monitorIsShadow: FALSE namingContexts: cn=accesslog readOnly: FALSE monitorOverlay: noopsrch seeAlso: cn=Overlay 1,cn=Overlays,cn=Monitor seeAlso: cn=Backend 2,cn=Backends,cn=Monitor olmMDBPagesMax: 97656 olmMDBPagesUsed: 33695 olmMDBPagesFree: 88 olmMDBReadersMax: 126 olmMDBReadersUsed: 3 olmDbDirectory: /var/lib/ldap/accesslog/ entryDN: cn=Database 1,cn=Databases,cn=Monitor subschemaSubentry: cn=Subschema hasSubordinates: TRUE

1 0

(ITS#8990) accesslog overlay misses SLAP_MOD_SOFT mod ops
by hyc＠openldap.org 11 Mar '19

11 Mar '19

Full_Name: Howard Chu Version: 2.4 OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (80.233.37.163) Submitted by: hyc The delta-sync consumer turns incoming delete modops with no value into Soft deletes, to avoid the need for an error check. The accesslog overlay is ignoring these modops.

1 0

Re: (ITS#8987) Dirty compile without -Wall and friends
by hyc＠symas.com 10 Mar '19

10 Mar '19

noloader(a)gmail.com wrote: > Full_Name: JW > Version: 2.4.47 > OS: Linux (Fedora 29, x86_64, fully patched) > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (151.196.22.177) >=20 >=20 > I'm building OpenLDAP 2.4.47 from sources on Fedora 29, x86_64. These l= ook like > a valid complaints: All of these are already fixed in git. Most as part of ITS#8890, some fro= m other commits. >=20 > cc -g2 -O2 -fsanitize=3Dundefined -march=3Dnative -fPIC -I../../../inc= lude > -I../../../include -I.. -I./.. -I/usr/local/include -DNDEBUG -c ldif.c = -o > ldif.o > bconfig.c: In function =E2=80=98config_rename_one=E2=80=99: > bconfig.c:4487:38: warning: passing argument 3 of =E2=80=98ldap_bv2rdn=E2= =80=99 from > incompatible pointer type [-Wincompatible-pointer-types] > rc =3D ldap_bv2rdn( &e->e_name, &rDN, &text, LDAP_DN_FORMAT_LDAP ); > ^~~~~ > In file included from ../../include/portable.h:1171, > from bconfig.c:21: > ../../include/ldap.h:1711:9: note: expected =E2=80=98char **=E2=80=99 b= ut argument is of type > =E2=80=98const char **=E2=80=99 > char **next, > ~~~~~~~^~~~ > ../../include/ldap_cdefs.h:32:25: note: in definition of macro =E2=80=98= LDAP_P=E2=80=99 > # define LDAP_P(protos) protos > ^~~~~~ >=20 >=20 >=20 > bconfig.c: In function =E2=80=98config_build_entry=E2=80=99: > bconfig.c:6505:31: warning: passing argument 3 of =E2=80=98ldap_bv2rdn=E2= =80=99 from > incompatible pointer type [-Wincompatible-pointer-types] > rc =3D ldap_bv2rdn( rdn, &rDN, &text, LDAP_DN_FORMAT_LDAP ); > ^~~~~ > In file included from ../../include/portable.h:1171, > from bconfig.c:21: > ../../include/ldap.h:1711:9: note: expected =E2=80=98char **=E2=80=99 b= ut argument is of type > =E2=80=98const char **=E2=80=99 > char **next, > ~~~~~~~^~~~ > ../../include/ldap_cdefs.h:32:25: note: in definition of macro =E2=80=98= LDAP_P=E2=80=99 > # define LDAP_P(protos) protos > ^~~~~~ >=20 >=20 > cc -g2 -O2 -fsanitize=3Dundefined -march=3Dnative -fPIC -I../../include= -I. > -I./slapi -I. -I../../include -I/usr/local/include -DNDEBUG -c -o > backends.o backends.c > backend.c: In function =E2=80=98fe_acl_group=E2=80=99: > backend.c:1503:56: warning: comparison between pointer and zero charact= er > constant [-Wpointer-compare] > if ( ludp->lud_filter !=3D NULL && ludp->lud_filter !=3D '\0') { > ^~ > backend.c:1503:39: note: did you mean to dereference the pointer? > if ( ludp->lud_filter !=3D NULL && ludp->lud_filter !=3D '\0') { > ^ >=20 >=20 > cc -g2 -O2 -fsanitize=3Dundefined -march=3Dnative -fPIC -I../../../inc= lude > -I../../../include -I.. -I./.. -I. -I./../back-bdb -I/usr/local/include= -DNDEBUG > -c tools.c -o tools.o > In file included from ../../../include/portable.h:1171, > from init.c:17: > init.c: In function 'hdb_db_open': > ../back-bdb/proto-bdb.h:22:35: warning: passing argument 2 of > 'db->bdi_db->set_dup_compare' from incompatible pointer type > [-Wincompatible-pointer-types] > #define BDB_SYMBOL(x) LDAP_CONCAT(hdb_,x) > ^~~~ >=20 >=20 >=20 > syntax.c: In function =E2=80=98syn_add=E2=80=99: > syntax.c:222:33: warning: comparison between pointer and zero character= constant > [-Wpointer-compare] > if ( (*lsei)->lsei_values[0] =3D=3D '\0' > ^~ > syntax.c:222:9: note: did you mean to dereference the pointer? > if ( (*lsei)->lsei_values[0] =3D=3D '\0' > ^ > syntax.c:223:32: warning: comparison between pointer and zero character= constant > [-Wpointer-compare] > || (*lsei)->lsei_values[1] !=3D '\0' ) > ^~ > syntax.c:223:8: note: did you mean to dereference the pointer? > || (*lsei)->lsei_values[1] !=3D '\0' ) > ^ >=20 >=20 >=20 > cc -g2 -O2 -fsanitize=3Dundefined -march=3Dnative -fPIC -I../../include > -I../../include -I/usr/local/include -DNDEBUG -c -o slapd-addel.o > slapd-addel.c > slapd-addel.c: In function =E2=80=98main=E2=80=99: > slapd-addel.c:176:36: warning: comparison between pointer and zero char= acter > constant [-Wpointer-compare] > if (( attrs =3D=3D NULL ) || ( *attrs =3D=3D '\0' )) { > ^~ >=20 >=20 >=20 >=20 --=20 -- 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs