openldap-bugs

openldap-bugs@openldap.org

1 participants
21001 discussions

Re: (ITS#5399) LDAP Syntax 1.3.6.1.4.1.1466.115.121.1.58 (Substring Assertion) not listed in subschema subentry
by ando＠sys-net.it 01 Mar '08

01 Mar '08

kurt(a)OpenLDAP.org wrote: > IIRC, it's not listed because it only to be used in certain > (extensible) matching rules cases and slapd(8) doesn't support any of > those cases. Technically, I note it's skipped by syn_schema_info() because it has no validator (like many other known syntaxes). I don't recall the reason of this behavior, though. Perhaps it could be relaxed. 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

Re: (ITS#5400) authz-regexp migration issue: ACLs of 2.3 no longer work with 2.4.8
by ando＠sys-net.it 01 Mar '08

01 Mar '08

michael(a)stroeder.com wrote: > Take note of this: > > authz-regexp > "uid=([a-zA-Z0-9]+),cn=digest-md5,cn=auth" > "ldap:///ou=authz-test,dc=stroeder,dc=local??sub?(uid=$1)" > [..] > access to > dn.onelevel="ou=Users,ou=authz-test,dc=stroeder,dc=local" > by * auth > > > See test of recent RE23 (port 2003) vs. recent RE24 (port 2004): As indicated in OpenLDAP 2.4's man page, now the LDA search operation requires "search" privileges on the "entry" pseudo-attribute of the searchBase. This was introduced to be able to honor the "disclose" privilege (or, at least, in conjunction with code that is used to honore the "disclose" privilege). The man page is erroneous in stating that this requirement and that feature were introduced in OpenLDAP 2.3: the code is indeed present in OpenLDAP 2.3, but actually #ifdef'd; it only became the default behavior in OpenLDAP 2.4. This requirement, as usual, is downgraded to "auth" when performing authc/authz related lookups. I'd take this ITS as a request to fix the documentation (indicate the change since 2.4 and not since 2.3) and to better notify the different behavior since 2.3. 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

Re: (ITS#5400) authz-regexp migration issue: ACLs of 2.3 no longer work with 2.4.8
by michael＠stroeder.com 01 Mar '08

01 Mar '08

This is a multi-part message in MIME format. --------------080909030908010602050105 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Follow-up on openldap-software repeated here... Gavin Henry wrote: > Michael Ströder wrote: >> >> I tried to migrate an existing server from 2.3.39 to 2.4.7 (or also >> CVS RE24). I'm making use of authz-regexp to map user entries when >> they do a SASL Bind with DIGEST-MD5. Also some ACLs are in effect. >> This together used to work on 2.3.x with the existing ACLs. >> >> With 2.4.7 this worked no longer. The user wasn't found. In the ACL >> debug log I've noticed that access to the search root database entry >> (suffix) is requested. When I explicitly grant auth access to this >> entry it works. But why is that needed? Was this an intended change? > > Can you paste them? I've prepared a simplified slapd.conf and a LDIF file (both attached) for this particular migration issue. Take note of this: authz-regexp "uid=([a-zA-Z0-9]+),cn=digest-md5,cn=auth" "ldap:///ou=authz-test,dc=stroeder,dc=local??sub?(uid=$1)" [..] access to dn.onelevel="ou=Users,ou=authz-test,dc=stroeder,dc=local" by * auth See test of recent RE23 (port 2003) vs. recent RE24 (port 2004): ----------------------------- snip ----------------------------- $ /opt/openldap-RE24/bin/ldapwhoami -H "ldap://localhost:2003" -Y DIGEST-MD5 -w testsecret SASL/DIGEST-MD5 authentication started SASL username: michael SASL SSF: 128 SASL data security layer installed. dn:uid=michael,ou=users,ou=authz-test,dc=stroeder,dc=local $ /opt/openldap-RE24/bin/ldapwhoami -H "ldap://localhost:2004" -Y DIGEST-MD5 -w testsecret SASL/DIGEST-MD5 authentication started ldap_sasl_interactive_bind_s: Invalid credentials (49) m ----------------------------- snip ----------------------------- If I grant auth access to the database root entry ou=authz-test,dc=stroeder,dc=local it works (see comment of this particular ACL in attached slapd.conf). With RE23 it also works without this ACL! Ciao, Michael. --------------080909030908010602050105 Content-Type: text/x-ldif; name="initialload.ldif" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="initialload.ldif" dn: ou=authz-test,dc=stroeder,dc=local objectClass: organizationalUnit ou: authz-test dn: ou=Users,ou=authz-test,dc=stroeder,dc=local objectClass: organizationalUnit ou: Users dn: uid=michael,ou=Users,ou=authz-test,dc=stroeder,dc=local uid: michael objectClass: account objectClass: simpleSecurityObject userpassword: testsecret --------------080909030908010602050105 Content-Type: text/plain; name="slapd.conf" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="slapd.conf" include /opt/openldap-RE24/etc/openldap/schema/core.schema include /opt/openldap-RE24/etc/openldap/schema/cosine.schema # Define global ACLs to disable default read access. pidfile /home/michael/temp/openldap-authzto-testbed/RE24/run/slapd-1.pid argsfile /home/michael/temp/openldap-authzto-testbed/RE24/run/slapd-1.args modulepath /opt/openldap-RE24/libexec/openldap moduleload back_hdb.la authz-regexp "uid=([a-zA-Z0-9]+),cn=digest-md5,cn=auth" "ldap:///ou=authz-test,dc=stroeder,dc=local??sub?(uid=$1)" database hdb suffix "ou=authz-test,dc=stroeder,dc=local" directory /home/michael/temp/openldap-authzto-testbed/RE24/data # Index-Konfiguration index objectClass,uid eq sizelimit -1 # User entries # ------------------------ access to dn.onelevel="ou=Users,ou=authz-test,dc=stroeder,dc=local" by * auth # Why the hell is this ACL needed for SASL Bind with authz-regexp with OpenLDAP 2.4? access to dn.base="ou=authz-test,dc=stroeder,dc=local" by * auth --------------080909030908010602050105--

1 0

(ITS#5400) authz-regexp migration issue: ACLs of 2.3 no longer work with 2.4.8
by michael＠stroeder.com 01 Mar '08

01 Mar '08

Full_Name: Michael Ströder Version: 2.4.8 OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (84.163.75.104) A configuration using authz-regexp fully functional with appropriate ACLs was working in RE23 but does not work in 2.4.8 anymore. http://www.openldap.org/lists/openldap-software/200802/msg00373.html More to follow...

1 0

Re: (ITS#5399) LDAP Syntax 1.3.6.1.4.1.1466.115.121.1.58 (Substring Assertion) not listed in subschema subentry
by kurt＠OpenLDAP.org 29 Feb '08

29 Feb '08

On Feb 29, 2008, at 1:56 AM, michael(a)stroeder.com wrote: > Full_Name: Michael Ströder > Version: HEAD > OS: > URL: > Submission from: (NULL) (84.163.114.177) > > > Although implemnted since 2.0 the LDAP Syntax with > 1.3.6.1.4.1.1466.115.121.1.58 > (Substring Assertion) is not listed in subschema subentry. IIRC, it's not listed because it only to be used in certain (extensible) matching rules cases and slapd(8) doesn't support any of those cases. I noticed that this came up because someone was trying to use this syntax an attribute description. That attribute description is likely bogus.

1 0

Re: (ITS#5387) slapcat ignores errors while writing output (no space left on device, etc)
by ando＠sys-net.it 29 Feb '08

29 Feb '08

jclarke(a)linagora.com wrote: > jclarke(a)linagora.com a écrit : >>>> When slapcat is writing it's output to disk, it ignores any errors >>>> (with slapcat -l output_file or slapcat > output_file). If an error is >>>> encountered, such as "No space left on device", slapcat then exits >>>> normally with a return code of 0. > > Thanks for commiting this to HEAD. > > Is there any chance of seeing it a future maintenance release of 2.3? As soon as one is planned, if ever. I can't say anything right now, since this issue is not a showstopper, and 2.3.41 has just been released. Unless 2.4 becomes stable any soon, there'll probably be another 2.3 at some point. 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

Re: (ITS#5387) slapcat ignores errors while writing output (no space left on device, etc)
by jclarke＠linagora.com 29 Feb '08

29 Feb '08

jclarke(a)linagora.com a écrit : >>> When slapcat is writing it's output to disk, it ignores any errors >>> (with slapcat -l output_file or slapcat > output_file). If an error is >>> encountered, such as "No space left on device", slapcat then exits >>> normally with a return code of 0. Thanks for commiting this to HEAD. Is there any chance of seeing it a future maintenance release of 2.3? Regards, Jonathan -- Jonathan Clarke Cellule OSSA - Groupe LINAGORA 27 rue de Berri, 75008 Paris Tél: 01 58 18 68 28, fax: 01 58 18 68 29 http://www.linagora.com - http://www.08000linux.com

1 0

ITS#5396
by ecizaguirre＠gmv.com 29 Feb '08

29 Feb '08

Another update about this problem. Connections between slpad and the remote active directory servers remains in ESTABLISHED state for a long time and changes to CLOSE_WAIT state in the slapd server. In the active directory servers the connections then changes to FIN_WAIT_2, so it seems the slapd server is not sending the FIN packet to close the socket. Cheers. Eduardo ________________________________ De: Eduardo Izaguirre Pazos Enviado el: jueves, 28 de febrero de 2008 13:21 Para: 'openldap-its(a)openldap.org' Asunto: ITS#5396 An update about the case, the problem seems to be related with the connections which remains in CLOSE_WAIT state, as an example: [root@metaldap openldap]# netstat -an | grep -i close | wc -l 11361 all these connections are to the remote ldap servers. Cheers. Eduardo. ________________________________ Eduardo Izaguirre Pazos Administrador de Sistemas / Systems Administrator GRUPO TECNOLÓGICO E INDUSTRIAL GMV,S.A. Isaac Newton, 11 P.T.M. Tres Cantos E-28760 Madrid Tel. +34 91 807 21 00 Fax +34 91 807 21 99 www.gmv.com ______________________ Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede contener informacion clasificada por su emisor como confidencial en el marco de su Sistema de Gestion de Seguridad de la Informacion siendo para uso exclusivo del destinatario, quedando prohibida su divulgacion copia o distribucion a terceros sin la autorizacion expresa del remitente. Si Vd. ha recibido este mensaje erroneamente, se ruega lo notifique al remitente y proceda a su borrado. Gracias por su colaboracion. ______________________ This message including any attachments may contain confidential information, according to our Information Security Management System, and intended solely for a specific individual to whom they are addressed. Any unauthorised copy, disclosure or distribution of this message is strictly forbidden. If you have received this transmission in error, please notify the sender immediately and delete it. ______________________

1 0

(ITS#5399) LDAP Syntax 1.3.6.1.4.1.1466.115.121.1.58 (Substring Assertion) not listed in subschema subentry
by michael＠stroeder.com 29 Feb '08

29 Feb '08

Full_Name: Michael Ströder Version: HEAD OS: URL: Submission from: (NULL) (84.163.114.177) Although implemnted since 2.0 the LDAP Syntax with 1.3.6.1.4.1.1466.115.121.1.58 (Substring Assertion) is not listed in subschema subentry.

1 0

(ITS#5398) An account locked in a consumer is only unlocked when the password is changed two times
by ssnet＠ua.es 28 Feb '08

28 Feb '08

Full_Name: maria saez Version: 2.4.8 OS: debian etch URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (193.145.230.2) An account locked in a consumer needs two password changes in the provider to be unlocked. The first time that we change the password in the provider the password change is replicated in the consumer but the account remains locked. Can you help us? We have openldap-2.4.7 and openldap-2.4.8 Is this situation normal? We have the following configuration: Provider ------------------------------------------- database bdb suffix "dc=xx,dc=es" rootdn "cn=config" directory /xx/data index entryCSN eq index entryUUID eq index objectClass eq index mail eq # define the replica provider for this database # (last directives in database section) overlay ppolicy ppolicy_default "cn=Standard Policy,ou=Policies,dc=xx,dc=es" ppolicy_use_lockout overlay syncprov syncprov-checkpoint 100 10 syncprov-sessionlog 100 Consumer ---------------------------------------------------------------- database bdb suffix "dc=xx,dc=es" rootdn "cn=config" directory /xx/data index entryCSN eq index entryUUID eq index objectClass eq index mail eq overlay ppolicy ppolicy_default "cn=Standard Policy,ou=Policies,dc=ua,dc=es" ppolicy_use_lockout syncrepl rid=123 provider=ldaps://xx.xx.es:xx/ binddn="cn=config" bindmethod=simple credentials=xx searchbase="dc=xx,dc=es" schemachecking=on type=refreshAndPersist retry="60 +" overlay syncprov ------------------------------------------------------------------- The policy we have defined: dn: cn=Standard Policy,ou=Policies,dc=xx,dc=es cn: Standard Policy objectClass: top objectClass: device objectClass: pwdPolicy pwdAttribute: 2.5.4.35 pwdLockout: TRUE pwdLockoutDuration: 0 pwdInHistory: 6 pwdCheckQuality: 2 pwdExpireWarning: 10 pwdMaxAge: 120 pwdMinLength: 5 pwdGraceAuthnLimit: 3 pwdAllowUserChange: TRUE pwdMustChange: TRUE pwdMaxFailure: 3 pwdFailureCountInterval: 120 pwdSafeModify: TRUE pwdMinAge: 120 -------------------------------------------------------------

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