openldap-bugs

openldap-bugs@openldap.org

1 participants
20961 discussions

(ITS#6650) The synchronization between two Mirror Servers is not stable
by changhong_sun＠yahoo.cn 18 Sep '10

18 Sep '10

Full_Name: Chang Hong Sun Version: 4.2.12 OS: SUSE Linux Enterprise Server 11 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (124.15.219.84) Hi, I'm using OpenLdap 4.2.12 Mirror Mode to make protection between two LDAP servers. Sometimes it works prettey good, but sometimes the synchronization between two servers doesn't work, I don't know if the Mirror Mode is not stable in 4.2.12, should I update to a higher version? Thanks and Best Regards, Changhong

1 0

(ITS#6649) Possible bug in ldapsearch
by kacoroski＠gmail.com 17 Sep '10

17 Sep '10

Full_Name: Ski Kacoroski Version: 2.4.23 OS: debian 64 bit linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (152.157.64.243) When I run a search with the following parameters: 0 'base' 1 'dc=nsd,dc=org' 2 'attr' 3 ARRAY(0x23f0cf0) 0 'nsduidnumber' 4 'filter' 5 '(&(objectClass=nsdAcct)(nsdUIDNumber<=80000)(nsdUIDNumber>=70000))' 6 'control' 7 ARRAY(0x23f0fa8) 0 Net::LDAP::Control::Sort=HASH(0x2374e60) 'order' => ARRAY(0x23f05b8) 0 'nsduidnumber' 'type' => '1.2.840.113556.1.4.473' 'value' => "0\cP0\cN\cD\cLnsduidnumber" 1 Net::LDAP::Control::Paged=HASH(0x23f0b88) 'asn' => HASH(0x23f0d80) 'cookie' => '' 'size' => 10 'size' => 10 'type' => '1.2.840.113556.1.4.319' 'value' => "0\cE\cB\cA\cJ\cD\c@" I can reliably crash the slapd server. Logs are in Ski-Kacoroski-100917.ext If I only use one or the other control it works fine. It only crashed when both controls are used together. Let me know if you need anything else.

1 0

Re: (ITS#6642) back-meta idassert with SASL EXTERNAL ignoring parameters
by mgaupp＠googlemail.com 17 Sep '10

17 Sep '10

> Just to make sure, can you pull the entire HEAD? =A0Thanks for checking, = in > any case. =A0p. I finally had the time to reproduce the issue using the cvs source code from HEAD. The following command was used to build OpenLDAP: -------------------------------- CPPFLAGS=3D"-I/home/openldap/software/include -D_AVL_H" \ LDFLAGS=3D"-L/home/openldap/software/lib -Wl,-rpath=3D/home/openldap/softwa= re/lib" \ ./configure --prefix=3D/home/openldap/software --enable-rewrite --enable-dn= ssrv \ --enable-ldap --enable-meta --enable-auditlog --enable-rwm --enable-sssvl= v \ --with-cyrus-sasl --with-tls=3Dopenssl --enable-bdb make depend; make; make install -------------------------------- The necessary SSL certificates are selfsigned: -------------------------------- openssl genrsa -out server1.key 2048 openssl req -new -key server1.key -x509 -days 365 -out server1.crt openssl genrsa -out server2.key 2048 openssl req -new -key server2.key -x509 -days 365 -out server2.crt -------------------------------- "server2" was started with the command: slapd -f /home/openldap/config/slapd.conf.server2 -h "ldaps://server2:6361" At this point I could already authenticate via SASL EXTERNAL using the ldapsearch command: LDAPTLS_CACERT=3Dserver2.crt LDAPTLS_CERT=3Dserver1.crt LDAPTLS_KEY=3Dserve= r1.key \ ldapsearch -H "ldaps://server2:6361" -b "" -s base -Y EXTERNAL 'objectcla= ss=3D*' Now I started "server1": slapd -f /home/openldap/config/slapd.conf.server1 -h "ldap://server1:3891" Searching with ldapsearch -H ldap://server1:3891 -b "dc=3Dserver2,dc=3Dexample,dc=3Dcom" -= x gives me no result, but the following output on server1's debug log (level = 1): -------------------------------- ldap_connect_to_host: Trying 127.0.0.1:6361 ldap_pvt_connect: fd: 9 tm: -1 async: 0 TLS trace: SSL_connect:before/connect initialization TLS trace: SSL_connect:SSLv2/v3 write client hello A TLS trace: SSL_connect:SSLv3 read server hello A TLS certificate verification: depth: 0, err: 18, subject: /C=3DAU/ST=3DSome-State/O=3DInternet Widgits Pty Ltd/CN=3Dserver2, issuer: /C=3DAU/ST=3DSome-State/O=3DInternet Widgits Pty Ltd/CN=3Dserver2 TLS certificate verification: Error, self signed certificate TLS trace: SSL3 alert write:fatal:unknown CA TLS trace: SSL_connect:error in SSLv3 read server certificate B TLS trace: SSL_connect:error in SSLv3 read server certificate B TLS: can't connect: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed (self signed certificate). conn=3D1000 op=3D1 meta_search_dobind_init[0]: retrying URI=3D"ldaps://server2:6361" DN=3D"". -------------------------------- And again: Starting "server1" with the environment variables and everything works fine= : LDAPTLS_CACERT=3Dserver2.crt LDAPTLS_CERT=3Dserver1.crt LDAPTLS_KEY=3Dserve= r1.key \ slapd -f /home/openldap/config/slapd.conf.server1 -h "ldap://server1:3891= " I hope you can reproduce this issue using the information I provided. The configurations of both servers are attached below. Best Regards, Manuel slapd.conf.server1 -------------------------------- include /home/openldap/software/etc/openldap/schema/core.schema include /home/openldap/software/etc/openldap/schema/cosine.schema include /home/openldap/software/etc/openldap/schema/inetorgperson.s= chema database meta suffix "dc=3Dexample,dc=3Dcom" uri "ldaps://server2:6361/dc=3Dserver2,dc=3Dexample,dc=3Dcom" idassert-authzFrom "*" idassert-bind bindmethod=3Dsasl saslmech=3DEXTERNAL tls_cert=3D/home/openldap/config/server1.crt tls_key=3D/home/openldap/config/server1.key tls_cacert=3D/home/openldap/config/server2.crt mode=3Dnone -------------------------------- slapd.conf.server2 -------------------------------- include /home/openldap/software/etc/openldap/schema/core.schema include /home/openldap/software/etc/openldap/schema/cosine.schema include /home/openldap/software/etc/openldap/schema/inetorgperson.s= chema TLSCertificateFile /home/openldap/config/server2.crt TLSCertificateKeyFile /home/openldap/config/server2.key TLSCACertificateFile /home/openldap/config/server1.crt TLSVerifyClient demand database bdb suffix "dc=3Dserver2,dc=3Dexample,dc=3Dcom" rootdn "cn=3Dmanager,dc=3Dserver2,dc=3Dexample,dc=3Dcom" directory /home/openldap/db.server2 --------------------------------

1 0

(ITS#6648) Syncrepl cold refresh fails with mirrormode supplier
by andrew.findlay＠skills-1st.co.uk 15 Sep '10

15 Sep '10

Full_Name: Andrew Findlay Version: 2.4.23 OS: OpenSuSE 11.1 URL: ftp://ftp.openldap.org/incoming/ajf-syncrepl-config-20100915a.tgz Submission from: (NULL) (88.97.25.132) When a read-only consumer server uses one peer of a mirrormode pair as its supplier, there is a case where the initial refresh phase of the synchronisation loses deletions. This is very similar to the case where a single master server has its serverID changed between taking a slapcat backup to LDIF and bringing up a consumer server fom that LDIF file. See this thread for some background: http://www.openldap.org/lists/openldap-technical/201009/msg00193.html The problem occurs when a deletion was originated on a server whose serverID does not match the serverID of the supplier when a new consumer is brought up. It is masked by the volatile syncprov-sessionlog if the deletion is still in the provider's log, which is why the instructions below stop and start the servers so much. I have uploaded the configs and data files for this to ftp.openldap.org. Case 1: serverID of supplier server changes during the creation of a consumer: people.ldif contains entries #1, #2, #3, #4 under dc=people,dc=example,dc=org 1) Load people.ldif into empty master server 2) Start master 3) Stop master 4) Dump master DB using slapcat > m1.ldif 5) Start master 6) Delete entry#1 7) Stop master 8) change master serverID 9) Start master 10) Dump master DB using slapcat > m2.ldif 11) Delete entry#2 11a) Stop master 11b) Start master 12) Load m1.ldif into empty consumer server 13) Start consumer 14) Check ContextCSN matches on each server 15) Check for Entry#1 Entry#2 Entry#3 If 11a/b are run: Entry#1 and Entry#2 are still found on the consumer If 11a/b are not run: Entry#1 is still found on the consumer Entry#2 is deleted - presumably because it was in the volatile sessionlog Case 2: mirrormode pair supplying read-only consumer: 1) Load people.ldif into empty peer server with serverID 1 2) Start peer 1 3) Start peer 2 and allow it to sync up 4) Stop peer 1 4) Dump peer 1 DB using slapcat > p1.ldif 5) Start peer 1 6) Delete entry#1 on peer 1 7) Delete entry#2 on peer 2 8) Verify that both entries have gone on both servers 9) Stop both peer servers (this clears the volatile syncrepl-sessionlog) 10) Start peer 1 and peer 2 11) Load p1.ldif into empty consumer server (which is configured to sync from peer 1) 12) Start consumer 13) Check ContextCSN matches on each server 14) Check for Entry#1 Entry#2 Entry#3 on all servers Entries #1 and #2 have gone on both mirrormode peers Entries #1 and #2 are still present on the consumer The consumer only has a ContextCSN value from peer 1 15) Restart the consumer server The consumer now has both ContextCSN values but it still has entries #1 and #2 16) Delete Entry #3 on peer 1 17) Check for entry #3 on all servers Correctly deleted 18) Delete Entry #4 on peer 2 19) Check for entry #3 on all servers Correctly deleted Entries #1 and #2 are still present on the consumer Andrew

1 0

Re: (ITS#6647) Overlay sssvlv is always loaded
by masarati＠aero.polimi.it 14 Sep '10

14 Sep '10

> Please try this (nearly blind) patch > > <ftp://ftp.openldap.org/incoming/pierangelo-masarati-2010-09-14-sssvlv.1.pat…> > > and report through the ITS. Thanks, p. I note that I have messed things up a bit in cleanup; however, this should not affect the testing of the functionality, except if you delete the overlay from the configuration using back-config. If the patch works fine, I'll fix that part. p.

1 0

Re: (ITS#6647) Overlay sssvlv is always loaded
by masarati＠aero.polimi.it 14 Sep '10

14 Sep '10

> 2010/9/14 <masarati(a)aero.polimi.it>: >>> On 14/09/2010 11:33, clem.oudot(a)gmail.com wrote: >>>> Full_Name: Clement OUDOT >>>> Version: 2.4.23 >>>> OS: GNU/Linux >>>> URL: ftp://ftp.openldap.org/incoming/ >>>> Submission from: (NULL) (83.145.72.122) >>>> >>>> >>>> Hi, >>>> >>>> I am using OpenLDAP 2.4.23 compiled with --enable-overlays (RPMs from >>>> http://www.ltb-project.org). Overlays are not compiled as modules. >>>> >>>> Overlay sssvlv is compiled, but not activated in configuration >>>> >>>> But: >>>> * SSS and VLV controls are displayed in RootDSE >>>> * SSS control is taken into account if present in an LDAP search >>>> operation >>>> >>>> For example, a search with SSS control on cn (which has no ordering >>>> rule) >>>> gives: >>>> result: 18 Inappropriate matching >>>> text: serverSort control: No ordering rule >>>> >>>> >>>> The error would be normal if overlay has been activated, but I think >>>> control >>>> should be ignored if overlay is not active. >>> >>> I hit this exact same issue just last week - it seems that when the >>> overlay is compiled in, the SSS control is displayed in the rootDSE. >>> >>> In my case, this caused a client to attempt to use the control, then >>> fail with a similar message as above. Without the overlay compiled in, >>> the client just doesn't use the control, and the client's operation >>> suceeded. >>> >>> My point is that I agree this probably shouldn't be activated by >>> default, or at the very least a clear warning added in the >>> documentation= > . >> >> This behavior is common to all overlays that register a general feature, >> like controls, extended ops or even just a bit of custom schema: the >> registration is done when the module is loaded (or at startup, if the >> module is statically built into slapd). =A0As a consequence, the feature >> = > is >> advertised because slapd knows about it, but since it is not explicitly >> configured, does not know how to handle it. >> >> In the end, slapd's behavior is correct: it recognizes the feature, it >> recognizes requests for the feature, but does not know how to handle >> them= > , >> thus returns an appropriate error. =A0This looks pretty consistent with >> RFC4511 and specifications of each feature, although I understand it >> coul= > d >> be disappointing. >> >> Perhaps we could modify this behavior so that the module initialization >> does nothing or so, and only the first instantiation of the feature >> cause= > s >> the real initialization. =A0This was discussed in the past, and I recall >> = > it >> created trouble when part of the initialization was needed earlier (e.g. >> registering schema items that need to be used later in the configuration >> or so; a clear case was back-monitor, which registers schema items that >> are needed by other backends when registering custom monitoring; if >> back-monitor startup didn't occur early enough, one had to instantiate >> it >> before any database that wanted to register custom monitoring). >> >> In conclusion: the current behavior is consistent; on a case by case >> basis, feature instantiation could perhaps be deferred as much as >> possible, unless this conflicts with other features. >> > > I understand your point of view. Indeed, recompiling OpenLDAP without > sssvlv overlay works. > > The fact is that for people compiling OpenLDAP with --enable-overlays, > we have a 'regression' with overlay sssvlv, because LDAP clients are > now using the control and get errors. > > Maybe the issue can be retargeted to sssvlv overlay: if an LDAP client > is using the SSS control in a non-critical mode, OpenLDAP should > return search results (unsorted) even if the control fails (because of > missing ordering rule for requested attribute). If the control is > critical, then the error must be returned. Please try this (nearly blind) patch <ftp://ftp.openldap.org/incoming/pierangelo-masarati-2010-09-14-sssvlv.1.pat…> and report through the ITS. Thanks, p.

1 0

Re: (ITS#6647) Overlay sssvlv is always loaded
by clem.oudot＠gmail.com 14 Sep '10

14 Sep '10

2010/9/14 <masarati(a)aero.polimi.it>: >> On 14/09/2010 11:33, clem.oudot(a)gmail.com wrote: >>> Full_Name: Clement OUDOT >>> Version: 2.4.23 >>> OS: GNU/Linux >>> URL: ftp://ftp.openldap.org/incoming/ >>> Submission from: (NULL) (83.145.72.122) >>> >>> >>> Hi, >>> >>> I am using OpenLDAP 2.4.23 compiled with --enable-overlays (RPMs from >>> http://www.ltb-project.org). Overlays are not compiled as modules. >>> >>> Overlay sssvlv is compiled, but not activated in configuration >>> >>> But: >>> * SSS and VLV controls are displayed in RootDSE >>> * SSS control is taken into account if present in an LDAP search >>> operation >>> >>> For example, a search with SSS control on cn (which has no ordering >>> rule) >>> gives: >>> result: 18 Inappropriate matching >>> text: serverSort control: No ordering rule >>> >>> >>> The error would be normal if overlay has been activated, but I think >>> control >>> should be ignored if overlay is not active. >> >> I hit this exact same issue just last week - it seems that when the >> overlay is compiled in, the SSS control is displayed in the rootDSE. >> >> In my case, this caused a client to attempt to use the control, then >> fail with a similar message as above. Without the overlay compiled in, >> the client just doesn't use the control, and the client's operation >> suceeded. >> >> My point is that I agree this probably shouldn't be activated by >> default, or at the very least a clear warning added in the documentation= . > > This behavior is common to all overlays that register a general feature, > like controls, extended ops or even just a bit of custom schema: the > registration is done when the module is loaded (or at startup, if the > module is statically built into slapd). =A0As a consequence, the feature = is > advertised because slapd knows about it, but since it is not explicitly > configured, does not know how to handle it. > > In the end, slapd's behavior is correct: it recognizes the feature, it > recognizes requests for the feature, but does not know how to handle them= , > thus returns an appropriate error. =A0This looks pretty consistent with > RFC4511 and specifications of each feature, although I understand it coul= d > be disappointing. > > Perhaps we could modify this behavior so that the module initialization > does nothing or so, and only the first instantiation of the feature cause= s > the real initialization. =A0This was discussed in the past, and I recall = it > created trouble when part of the initialization was needed earlier (e.g. > registering schema items that need to be used later in the configuration > or so; a clear case was back-monitor, which registers schema items that > are needed by other backends when registering custom monitoring; if > back-monitor startup didn't occur early enough, one had to instantiate it > before any database that wanted to register custom monitoring). > > In conclusion: the current behavior is consistent; on a case by case > basis, feature instantiation could perhaps be deferred as much as > possible, unless this conflicts with other features. > I understand your point of view. Indeed, recompiling OpenLDAP without sssvlv overlay works. The fact is that for people compiling OpenLDAP with --enable-overlays, we have a 'regression' with overlay sssvlv, because LDAP clients are now using the control and get errors. Maybe the issue can be retargeted to sssvlv overlay: if an LDAP client is using the SSS control in a non-critical mode, OpenLDAP should return search results (unsorted) even if the control fails (because of missing ordering rule for requested attribute). If the control is critical, then the error must be returned. What is your opinion? Cl=E9ment.

1 0

Re: (ITS#6647) Overlay sssvlv is always loaded
by masarati＠aero.polimi.it 14 Sep '10

14 Sep '10

> On 14/09/2010 11:33, clem.oudot(a)gmail.com wrote: >> Full_Name: Clement OUDOT >> Version: 2.4.23 >> OS: GNU/Linux >> URL: ftp://ftp.openldap.org/incoming/ >> Submission from: (NULL) (83.145.72.122) >> >> >> Hi, >> >> I am using OpenLDAP 2.4.23 compiled with --enable-overlays (RPMs from >> http://www.ltb-project.org). Overlays are not compiled as modules. >> >> Overlay sssvlv is compiled, but not activated in configuration >> >> But: >> * SSS and VLV controls are displayed in RootDSE >> * SSS control is taken into account if present in an LDAP search >> operation >> >> For example, a search with SSS control on cn (which has no ordering >> rule) >> gives: >> result: 18 Inappropriate matching >> text: serverSort control: No ordering rule >> >> >> The error would be normal if overlay has been activated, but I think >> control >> should be ignored if overlay is not active. > > I hit this exact same issue just last week - it seems that when the > overlay is compiled in, the SSS control is displayed in the rootDSE. > > In my case, this caused a client to attempt to use the control, then > fail with a similar message as above. Without the overlay compiled in, > the client just doesn't use the control, and the client's operation > suceeded. > > My point is that I agree this probably shouldn't be activated by > default, or at the very least a clear warning added in the documentation. This behavior is common to all overlays that register a general feature, like controls, extended ops or even just a bit of custom schema: the registration is done when the module is loaded (or at startup, if the module is statically built into slapd). As a consequence, the feature is advertised because slapd knows about it, but since it is not explicitly configured, does not know how to handle it. In the end, slapd's behavior is correct: it recognizes the feature, it recognizes requests for the feature, but does not know how to handle them, thus returns an appropriate error. This looks pretty consistent with RFC4511 and specifications of each feature, although I understand it could be disappointing. Perhaps we could modify this behavior so that the module initialization does nothing or so, and only the first instantiation of the feature causes the real initialization. This was discussed in the past, and I recall it created trouble when part of the initialization was needed earlier (e.g. registering schema items that need to be used later in the configuration or so; a clear case was back-monitor, which registers schema items that are needed by other backends when registering custom monitoring; if back-monitor startup didn't occur early enough, one had to instantiate it before any database that wanted to register custom monitoring). In conclusion: the current behavior is consistent; on a case by case basis, feature instantiation could perhaps be deferred as much as possible, unless this conflicts with other features. p.

1 0

Re: (ITS#6647) Overlay sssvlv is always loaded
by jonathan.clarke＠normation.com 14 Sep '10

14 Sep '10

On 14/09/2010 11:33, clem.oudot(a)gmail.com wrote: > Full_Name: Clement OUDOT > Version: 2.4.23 > OS: GNU/Linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (83.145.72.122) > > > Hi, > > I am using OpenLDAP 2.4.23 compiled with --enable-overlays (RPMs from > http://www.ltb-project.org). Overlays are not compiled as modules. > > Overlay sssvlv is compiled, but not activated in configuration > > But: > * SSS and VLV controls are displayed in RootDSE > * SSS control is taken into account if present in an LDAP search operation > > For example, a search with SSS control on cn (which has no ordering rule) > gives: > result: 18 Inappropriate matching > text: serverSort control: No ordering rule > > > The error would be normal if overlay has been activated, but I think control > should be ignored if overlay is not active. I hit this exact same issue just last week - it seems that when the overlay is compiled in, the SSS control is displayed in the rootDSE. In my case, this caused a client to attempt to use the control, then fail with a similar message as above. Without the overlay compiled in, the client just doesn't use the control, and the client's operation suceeded. My point is that I agree this probably shouldn't be activated by default, or at the very least a clear warning added in the documentation. Jonathan -- ========================================== Jonathan CLARKE ------------------------------------------ Normation 44 rue Cauchy, 94110 Arcueil, France ------------------------------------------ Telephone: +33 (0)1 83 62 26 96 ------------------------------------------ Web: http://www.normation.com/ ==========================================

1 0

(ITS#6647) Overlay sssvlv is always loaded
by clem.oudot＠gmail.com 14 Sep '10

14 Sep '10

Full_Name: Clement OUDOT Version: 2.4.23 OS: GNU/Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (83.145.72.122) Hi, I am using OpenLDAP 2.4.23 compiled with --enable-overlays (RPMs from http://www.ltb-project.org). Overlays are not compiled as modules. Overlay sssvlv is compiled, but not activated in configuration But: * SSS and VLV controls are displayed in RootDSE * SSS control is taken into account if present in an LDAP search operation For example, a search with SSS control on cn (which has no ordering rule) gives: result: 18 Inappropriate matching text: serverSort control: No ordering rule The error would be normal if overlay has been activated, but I think control should be ignored if overlay is not active.

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