- openldap-bugs - openldap.org

Re: (ITS#8335) MDB_MULTIPLE issues
by hyc＠symas.com 13 Feb '17

13 Feb '17

h.b.furuseth(a)usit.uio.no wrote: > On 07/12/15 10:14, h.b.furuseth(a)usit.uio.no wrote: >> Put(0 data items, MDB_MULTIPLE) stores 1 item. The doc does >> not warn against 0 items. I suggest supporting 0 items, it >> is a commonly supported convenience elsewhere (e.g. memcpy). > > I.e. supporting it as a no-op. But on second thought I think > that's misleading and EINVAL is better: If the key doesn't exist, > this is an attempt to create a key with no data. Unsupported. > Bryan Matsuo just posted a test case to openldap-technical. EINVAL makes sense here. > datacount > UINT_MAX is truncated to unsigned int: > data[1].mv_size = 0x100000002 puts 2 items. > datacount * datasize can exceed UINT_MAX, which mdb_page_spill() > truncates to unsigned int. Such a massive put() will likely > fail anyway, but it should at least try to spill properly first. We should probably check if mv_size is greater than UINT_MAX and return EINVAL. (Or ERANGE.) >> Why does MDB_MULTIPLE require a cursor? mdb_put() rejects it. Because get only works with a cursor. -- -- 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#8586) load cert+chain from TLSCertificateFile
by sca＠andreasschulze.de 12 Feb '17

12 Feb '17

Am 12.02.2017 um 12:04 schrieb Michael Ströder: > sca+openldap(a)andreasschulze.de wrote: >> as discussed on the technical ML it's uncommon to put chain certificates in >> TLSCACertificateFile or TLSCACertificatePath. In case of a intermediate CA like >> "Let's Encrypt Authority X3" it may be wrong becaus the user is forced to >> /TRUST/ that intermediate for a unrelated purpose. > > We should be more precise here - especially regarding the term "user". agree > IMO it is common to put the whole CA cert chain in the cert configuration of a TLS > server. This is required so that the TLS *client* only has to know the root CA cert > (trust anchor) and the TLS server sends the intermediate certs. Note that some TLS > implementations like GnuTLS require the CA cert chain to be "in order" (bottom-up). As I don't use GnuTLS I can't tell something about it's internals > The real issue here is that TLSCACertificateFile and TLSCACertificatePath are also used > to specify the set of trusted CA certs to validate TLS client certs used by the TLS > client to authenticate. correct. That's also what "man 3 SSL_CTX_use_certificate" mention. > So I'm not sure whether your patch breaks the use-case of having more than one trusted > root CA cert for validating TLS client certs issued by independent CAs. I may imagine a setup with RSA and EC certificates. Two certs are more complex then one. But if an admin decide to use diferent CAs it's his decision for more complexity > I think we might need different directives for trusted CA certs for client cert > validation and the server cert chain (similar what's done on Apache mod_ssl with > SSLCertificateChainFile and SSLCACertificateFile/SSLCACertificatePath). also: I don't us apache, can't tell if that way is is the best. Postfix,dovecot, nginx for example don't require a "SSLCertificateChainFile" directive. > It could be sufficient to simply add the server CA cert chain to TLSCertificateFile and > only add the trusted root CA certs to TLSCACertificateFile/TLSCACertificatePath (and no C > code patch needed for that, maybe review/clarification of the docs). that's what the patch try. currently I tried to add cert+chain to a file used as TLSCertificateFile The chain is ignored as expected and documented in "man 3 SSL_CTX_use_certificate_file" simply replacing SSL_CTX_use_certificate_file by SSL_CTX_use_certificate_chain_file fix that. I now can put cert+chain (excluding a root) ti the file used as TLSCertificateFile. as simple as it could be. But: I'm aware there are other use cases that will break stuff, years old. So my ITS it more intended to point out a problem then simply changing openldap to my needs. Andreas

1 0

Re: (ITS#8335) MDB_MULTIPLE issues
by h.b.furuseth＠usit.uio.no 12 Feb '17

12 Feb '17

On 07/12/15 10:14, h.b.furuseth(a)usit.uio.no wrote: > Put(0 data items, MDB_MULTIPLE) stores 1 item. The doc does > not warn against 0 items. I suggest supporting 0 items, it > is a commonly supported convenience elsewhere (e.g. memcpy). I.e. supporting it as a no-op. But on second thought I think that's misleading and EINVAL is better: If the key doesn't exist, this is an attempt to create a key with no data. Unsupported. Bryan Matsuo just posted a test case to openldap-technical. datacount > UINT_MAX is truncated to unsigned int: data[1].mv_size = 0x100000002 puts 2 items. datacount * datasize can exceed UINT_MAX, which mdb_page_spill() truncates to unsigned int. Such a massive put() will likely fail anyway, but it should at least try to spill properly first. > Why does MDB_MULTIPLE require a cursor? mdb_put() rejects it.

1 0

Re: (ITS#8586) load cert+chain from TLSCertificateFile
by michael＠stroeder.com 12 Feb '17

12 Feb '17

sca+openldap(a)andreasschulze.de wrote: > as discussed on the technical ML it's uncommon to put chain certificates in > TLSCACertificateFile or TLSCACertificatePath. In case of a intermediate CA like > "Let's Encrypt Authority X3" it may be wrong becaus the user is forced to > /TRUST/ that intermediate for a unrelated purpose. We should be more precise here - especially regarding the term "user". IMO it is common to put the whole CA cert chain in the cert configuration of a TLS server. This is required so that the TLS *client* only has to know the root CA cert (trust anchor) and the TLS server sends the intermediate certs. Note that some TLS implementations like GnuTLS require the CA cert chain to be "in order" (bottom-up). The real issue here is that TLSCACertificateFile and TLSCACertificatePath are also used to specify the set of trusted CA certs to validate TLS client certs used by the TLS client to authenticate. So I'm not sure whether your patch breaks the use-case of having more than one trusted root CA cert for validating TLS client certs issued by independent CAs. I think we might need different directives for trusted CA certs for client cert validation and the server cert chain (similar what's done on Apache mod_ssl with SSLCertificateChainFile and SSLCACertificateFile/SSLCACertificatePath). It could be sufficient to simply add the server CA cert chain to TLSCertificateFile and only add the trusted root CA certs to TLSCACertificateFile/TLSCACertificatePath (and no C code patch needed for that, maybe review/clarification of the docs). Ciao, Michael.

1 0

Re: (ITS#8485) [PATCH] Adding support for encrypted server private keys
by balmerpeak92＠gmail.com 12 Feb '17

12 Feb '17

--f403045f155e1c46d105484cea3d Content-Type: text/plain; charset=UTF-8 This would be a very helpful feature for me - I have a web server that has to regularly interact with a corporately maintained secure LDAP server. I'd love to be able to store the certs for this interaction encrypted for added security. --f403045f155e1c46d105484cea3d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">This would be a very helpful feature for me - I have a web= server that has to regularly interact with a corporately maintained secure= LDAP server. I'd love to be able to store the certs for this interacti= on encrypted for added security.<br></div> --f403045f155e1c46d105484cea3d--

1 0

(ITS#8587) correct spelling errors: wrong: emtpy, correct: empty
by sca+openldap＠andreasschulze.de 11 Feb '17

11 Feb '17

Full_Name: Andreas Schulze Version: RE24 testing call (2.4.45) OS: Linux URL: ftp://ftp.openldap.org/incoming/andreas-schulze-20170211-2.patch Submission from: (NULL) (2001:a60:f0b4:e502:80b6:610b:8fc2:abfe) there are 4 occurrence of "emtpy" which are supposed to be written as "empty"

1 0

(ITS#8586) load cert+chain from TLSCertificateFile
by sca+openldap＠andreasschulze.de 11 Feb '17

11 Feb '17

Full_Name: Andreas Schulze Version: RE24 testing call (2.4.45) OS: Linux URL: ftp://ftp.openldap.org/incoming/andreas-schulze-20170211.patch Submission from: (NULL) (2001:a60:f0b4:e502:80b6:610b:8fc2:abfe) as discussed on the technical ML it's uncommon to put chain certificates in TLSCACertificateFile or TLSCACertificatePath. In case of a intermediate CA like "Let's Encrypt Authority X3" it may be wrong becaus the user is forced to /TRUST/ that intermediate for a unrelated purpose. from https://www.openssl.org/docs/man1.1.0/ssl/SSL_CTX_use_certificate.html#NOTES: SSL_CTX_use_certificate_chain_file() should be used instead of the SSL_CTX_use_certificate_file() function in order to allow the use of complete certificate chains even when no trusted CA storage is used or when the CA issuing the certificate shall not be added to the trusted CA storage. The patch andreas-schulze-20170211.patch only apply for openssl.

1 0

Re: (ITS#8581) slapd-meta backend SSL negociation timeout
by louis.chanouha＠test.univ-toulouse.fr 10 Feb '17

10 Feb '17

I tried with ltb's latest Jessie builds but same problem occurs. I fast-checked tls_o.c, i can't find any code relative to handshake timeout (https://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=blob;f=libraries…), but as i never handle any ssl lib code, i can be completely mistaken. On Jessie, default timeout on gnuTLS seems to be 3600 secs, I will try to wait. /usr/local/openldap/libexec/slapd -V @(#) $OpenLDAP: slapd 2.4.44 (Feb 8 2016 17:34:53) $ root@debian8:/opt/paquet-openldap-debian/openldap-ltb-2.4.44/servers/slapd

1 0

Re: (ITS#8582) LMDB lockfile/mutex arch dependency
by hyc＠symas.com 09 Feb '17

09 Feb '17

hyc(a)openldap.org wrote: > Full_Name: Howard Chu > Version: HEAD > OS: Linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (195.235.15.200) > Submitted by: hyc > > > I ran into some corruption problems when running a 64bit LMDB process concurrent > with a 32bit one using MDB_VL32. While LMDB's own structures are all 64bit clean > in a VL32 build, unfortunately pthread_mutex_t structures are not. In > particular, in glibc a pthread_mutex_t can be one of 3 different sizes - 24 > bytes for 32bit runtime on 32bit processor, 32 bytes for 32bit runtime on > x86-64, and 40 bytes for 64bit runtime on x86-64. As such, we cannot safely > share an LMDB environment between 32 and 64bit Linux processes, even when using > MDB_VL32. > > This problem doesn't affect Windows, platforms using SysV semaphores, or > platforms using POSIX named semaphores. I don't currently know whether this is a > problem on other platforms that support POSIX process-shared mutexes. For glibc, I've submitted an enhancement request regarding mutex sizes: https://sourceware.org/bugzilla/show_bug.cgi?id=21119 -- -- 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#8584) reloadhint for syncprov overlay should default to TRUE
by quanah＠symas.com 07 Feb '17

07 Feb '17

> On Feb 7, 2017, at 10:25 AM, hyc(a)symas.com wrote: >=20 > Quanah Gibson-Mount wrote: >> --On Tuesday, February 07, 2017 8:53 AM +0000 Howard Chu <hyc(a)symas.com> w= rote: >>=20 >>=20 >>> The relevant part of the doc is "It must be set TRUE when using the >>> accesslog overlay for delta-based syncrepl support." Otherwise it has no= >>> effect, so there is no reason to change it in the default case. >>=20 >> Actually, what the manpage says is: >>=20 >> This option should be set TRUE when working with >> newer releases that properly support this flag. It must be set >> TRUE when using the accesslog overlay for delta-based syncrepl >> replication support. >>=20 >> So, that clearly states it should *always* be TRUE unless you have a 2.3.= 11 or >> earlier consumer, which is technically not allowable. There is zero reas= on >> for this tunable to exist. It should be deprecated and the internal code= >> changed to simply set the flag to TRUE. One less item for anyone to have= to >> ever deal with is a win. >=20 > "when working with newer releases that properly support this flag." >=20 > The syncrepl consumer only pays attention to this flag in delta-sync. Ther= e is=20 > no reason to use reloadhint in regular syncrepl. Turning it on by default o= nly=20 > slows down the refresh negotiation in regular syncrepl. >=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/ >=20 Then the man page needs updating since the information on it is blatantly wr= ong. The "newer releases" is clearly indicated to be anything later than 2.= 3.11. --Quanah=

1 0

Re: (ITS#8584) reloadhint for syncprov overlay should default to TRUE
by hyc＠symas.com 07 Feb '17

07 Feb '17

Quanah Gibson-Mount wrote: > --On Tuesday, February 07, 2017 8:53 AM +0000 Howard Chu <hyc(a)symas.com> wrote: > > >> The relevant part of the doc is "It must be set TRUE when using the >> accesslog overlay for delta-based syncrepl support." Otherwise it has no >> effect, so there is no reason to change it in the default case. > > Actually, what the manpage says is: > > This option should be set TRUE when working with > newer releases that properly support this flag. It must be set > TRUE when using the accesslog overlay for delta-based syncrepl > replication support. > > So, that clearly states it should *always* be TRUE unless you have a 2.3.11 or > earlier consumer, which is technically not allowable. There is zero reason > for this tunable to exist. It should be deprecated and the internal code > changed to simply set the flag to TRUE. One less item for anyone to have to > ever deal with is a win. "when working with newer releases that properly support this flag." The syncrepl consumer only pays attention to this flag in delta-sync. There is no reason to use reloadhint in regular syncrepl. Turning it on by default only slows down the refresh negotiation in regular syncrepl. -- -- 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#8584) reloadhint for syncprov overlay should default to TRUE
by quanah＠symas.com 07 Feb '17

07 Feb '17

--On Tuesday, February 07, 2017 8:53 AM +0000 Howard Chu <hyc(a)symas.com> wrote: > The relevant part of the doc is "It must be set TRUE when using the > accesslog overlay for delta-based syncrepl support." Otherwise it has no > effect, so there is no reason to change it in the default case. Actually, what the manpage says is: This option should be set TRUE when working with newer releases that properly support this flag. It must be set TRUE when using the accesslog overlay for delta-based syncrepl replication support. So, that clearly states it should *always* be TRUE unless you have a 2.3.11 or earlier consumer, which is technically not allowable. There is zero reason for this tunable to exist. It should be deprecated and the internal code changed to simply set the flag to TRUE. One less item for anyone to have to ever deal with is a win. --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

(ITS#8585) assert in ber_get_next after connection error
by hyc＠openldap.org 07 Feb '17

07 Feb '17

Full_Name: Howard Chu Version: any OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (195.235.15.200) Submitted by: hyc 1) ldap_result() returns -1 with ld_errno = LDAP_LOCAL_ERROR because it read an unrecognizable message from the network. 2) ldap_result() is called again on the same LDAP*. During (1) the lc->lconn_ber was not zeroed out so it is used again in (2). But ber_get_next() already fully parsed its input during (1) so this assert fails on the 2nd call: 513 if (ber->ber_rwptr == NULL) { 514 assert( ber->ber_buf == NULL ); 515 ber->ber_rwptr = (char *) &ber->ber_len-1; 516 ber->ber_ptr = ber->ber_ptr%r; 517 ber->ber_tag = 0; 518 } ldap_result() should clear lconn_ber before returning with an error. The LDAP* session probably should not be used again after (1) anyway but this is still messy.

1 0

Re: (ITS#8584) reloadhint for syncprov overlay should default to TRUE
by hyc＠symas.com 07 Feb '17

07 Feb '17

quanah(a)openldap.org wrote: > Full_Name: Quanah Gibson-Mount > Version: 2.4.44 > OS: N/A > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (47.208.148.26) > > > The "reloadhint" option for the syncprov overlay currently defaults to FALSE. > However, the documentation clearly notes that you want to set it to true for any > release > 2.3.11. Given that 2.3 has been obsolete for years and it has been > over 11 years since the release of 2.3.11, we should really fix the default > value, and note that it should be changed if and only if there is a consumer > running 2.3.11 or prior. The relevant part of the doc is "It must be set TRUE when using the accesslog overlay for delta-based syncrepl support." Otherwise it has no effect, so there is no reason to change it in the default case. -- -- 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#8584) reloadhint for syncprov overlay should default to TRUE
by quanah＠symas.com 07 Feb '17

07 Feb '17

--On Monday, February 06, 2017 11:54 PM +0000 quanah(a)openldap.org wrote: > The "reloadhint" option for the syncprov overlay currently defaults to > FALSE. However, the documentation clearly notes that you want to set it > to true for any release > 2.3.11. Given that 2.3 has been obsolete for > years and it has been over 11 years since the release of 2.3.11, we > should really fix the default value, and note that it should be changed > if and only if there is a consumer running 2.3.11 or prior. Actually, since it is not a valid configuration scenario to have a 2.4 provider and a 2.3 consumer, it seems that the configuration option should be deprecated entirely, and the internal code simply default to TRUE. --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

(ITS#8584) reloadhint for syncprov overlay should default to TRUE
by quanah＠openldap.org 07 Feb '17

07 Feb '17

Full_Name: Quanah Gibson-Mount Version: 2.4.44 OS: N/A URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (47.208.148.26) The "reloadhint" option for the syncprov overlay currently defaults to FALSE. However, the documentation clearly notes that you want to set it to true for any release > 2.3.11. Given that 2.3 has been obsolete for years and it has been over 11 years since the release of 2.3.11, we should really fix the default value, and note that it should be changed if and only if there is a consumer running 2.3.11 or prior.

1 0

(ITS#8583) LDAPCtrl::LDAPCtrl(const LDAPControl* ctrl) issue
by jim.rooks＠neustar.biz 06 Feb '17

06 Feb '17

Full_Name: Jim Rooks Version: 2.4.44 OS: RedHat 6.8 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (104.129.194.54) The following code in contrib/ldapc++/src/LDAPControl.cpp needs to be corrected: LDAPCtrl::LDAPCtrl(const LDAPControl* ctrl){ DEBUG(LDAP_DEBUG_CONSTRUCT,"LDAPCtrl::LDAPCtrl()" << endl); m_oid = string(ctrl->ldctl_oid); m_oid = ctrl->ldctl_iscritical ? true : false; m_oid = string(ctrl->ldctl_value.bv_val, ctrl->ldctl_value.bv_len ); } to something like: LDAPCtrl::LDAPCtrl(const LDAPControl* ctrl){ DEBUG(LDAP_DEBUG_CONSTRUCT,"LDAPCtrl::LDAPCtrl()" << endl); m_oid = string(ctrl->ldctl_oid); m_isCritical = ctrl->ldctl_iscritical ? true : false; m_data = string(ctrl->ldctl_value.bv_val, ctrl->ldctl_value.bv_len ); m_noData = ctrl->ldctl_value.bv_len ? false : true; }

1 0

Re: [Spam?] (ITS#8577) Accesslog overlay hangs slapd depending on module loading order
by quanah＠symas.com 06 Feb '17

06 Feb '17

--On Wednesday, February 01, 2017 6:38 PM +0000 mj(a)netauth.com wrote: > Full_Name: Mike Jackson > Version: 2.4.44 > OS: Oracle Linux Server release 7.2 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (194.157.185.162) > > > Same issue as Stroeder mentioned here: > > http://www.openldap.org/lists/openldap-bugs/201111/msg00027.html > > If accesslog.la is loaded before syncprov.la, slapd will stop accepting > connections immediately after accesslog overlay is added. To note, this was a configuration error where accesslog overlay was being configured to write ops back onto itself. We should probably check for this and reject it (vs allowing it to lock up slapd). --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

(ITS#8582) LMDB lockfile/mutex arch dependency
by hyc＠openldap.org 06 Feb '17

06 Feb '17

Full_Name: Howard Chu Version: HEAD OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (195.235.15.200) Submitted by: hyc I ran into some corruption problems when running a 64bit LMDB process concurrent with a 32bit one using MDB_VL32. While LMDB's own structures are all 64bit clean in a VL32 build, unfortunately pthread_mutex_t structures are not. In particular, in glibc a pthread_mutex_t can be one of 3 different sizes - 24 bytes for 32bit runtime on 32bit processor, 32 bytes for 32bit runtime on x86-64, and 40 bytes for 64bit runtime on x86-64. As such, we cannot safely share an LMDB environment between 32 and 64bit Linux processes, even when using MDB_VL32. This problem doesn't affect Windows, platforms using SysV semaphores, or platforms using POSIX named semaphores. I don't currently know whether this is a problem on other platforms that support POSIX process-shared mutexes. Hallvard has suggested that we add some additional LOCK_FORMAT bits to protect against incompatible accesses. This would primarily be useful for the mdb_stat command, which can still safely retrieve some useful information from an environment without acquiring any mutexes. E.g., an MDB_VL32 build of mdb_stat could retrieve most envinfo, statinfo, and readerinfo from a running 64bit environment. It could not scan the freelist, scan all the names of named DBs, or clean the reader list, since these operations all require taking the reader mutex.

1 0

Re: (ITS#8581) slapd-meta backend SSL negociation timeout
by michael＠stroeder.com 05 Feb '17

05 Feb '17

This is a cryptographically signed message in MIME format. --------------ms020706080404060907060004 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: quoted-printable louis.chanouha(a)univ-toulouse.fr wrote: > OS: Debian 8 Jessie x64 > slapd: 2.4.40+dfsg-1+deb8u2 > gnutls: 3.3.8-6+deb8u4 Note that the Debian builds are an older version and AFAICS the GnuTLS wr= apping code does not receive much love. Try again release 2.4.44 linked to OpenSSL e.g. by using the ltb-project = builds or your own custom build. Ciao, Michael. --------------ms020706080404060907060004 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC CucwggT9MIID5aADAgECAhBFRleVrRF8X5GwbV0tcLCgMA0GCSqGSIb3DQEBCwUAMHUxCzAJ BgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSkwJwYDVQQLEyBTdGFydENvbSBD ZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEjMCEGA1UEAxMaU3RhcnRDb20gQ2xhc3MgMSBDbGll bnQgQ0EwHhcNMTYwOTE2MDcxNjUxWhcNMTkxMjE2MDcxNjUxWjBEMR0wGwYDVQQDDBRtaWNo YWVsQHN0cm9lZGVyLmNvbTEjMCEGCSqGSIb3DQEJARYUbWljaGFlbEBzdHJvZWRlci5jb20w ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQChMBt5jtuLXsNQ5U7rBbZit8sknIwz hfaousT3d/fssQ6qZwe9l1yklILSXVMqI7/bxbiqcd3zrz+imdSlZPrFBHGfh04DZHCfss2F RwSswGejqP1qE3hPvZi96wFfOMqenpN+pSXqNJ1OPBCJ8a+8ZEioFKoEj3HkCCXjbmezAgms FuA7aFE9BfjJ2eQKw8B9G8X1FjvOTinYSZ2F+qHpKgywl4HTx0dMnYy+Pwu4DDIHkEaVH+uj K1/ed76WUEH51mX9m2Xu0onfQlSM3me6EvAAZiIDsCEbF9WttRuJbpfCFo0m2uW7BBugS7EG Jro1nRSQVnpJyTFgHb5EGMVVAgMBAAGjggG4MIIBtDAOBgNVHQ8BAf8EBAMCBLAwHQYDVR0l BBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMAkGA1UdEwQCMAAwHQYDVR0OBBYEFFh1801TSuxT Nltnv9rOjrZzUUgNMB8GA1UdIwQYMBaAFCSBbDlhvkkPj7cbRivJKLUnSG1oMG8GCCsGAQUF BwEBBGMwYTAkBggrBgEFBQcwAYYYaHR0cDovL29jc3Auc3RhcnRzc2wuY29tMDkGCCsGAQUF BzAChi1odHRwOi8vYWlhLnN0YXJ0c3NsLmNvbS9jZXJ0cy9zY2EuY2xpZW50MS5jcnQwOAYD VR0fBDEwLzAtoCugKYYnaHR0cDovL2NybC5zdGFydHNzbC5jb20vc2NhLWNsaWVudDEuY3Js MB8GA1UdEQQYMBaBFG1pY2hhZWxAc3Ryb2VkZXIuY29tMCMGA1UdEgQcMBqGGGh0dHA6Ly93 d3cuc3RhcnRzc2wuY29tLzBHBgNVHSAEQDA+MDwGCysGAQQBgbU3AQIFMC0wKwYIKwYBBQUH AgEWH2h0dHBzOi8vd3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3kwDQYJKoZIhvcNAQELBQADggEB AKiJ9wpjJeHdEzHDZyqmhn4cHcRj9Ag7ZQK0meq1N3oQ9M1YeVge6vZe20LXojgXsNUQGLSt 1lW2s7fABkL9CF+/RtWznHxlp4YpWX/RgbHBo3uXKNA5JUOjbxQ2+1b1jaTp/FUrSIISAxgd RpeYAODJ0db1x8Q+l66DtIVjj7ktWISdJWE2Opn4QnaRwdj6n35Rul4S2ikUsmxtGrHLpjRR XJqbsGa0RZdJyUKlZ2ZRAoRz4jKHOogQcig937sR5Ut2pGOhrScEhgARY2c8Gs2olRTL3pue mE4vjY0g1Nwr9RzeFwMuasiFh4yD34i6jIRfoNzuLPgydjsJ0grw0akwggXiMIIDyqADAgEC AhBrp4p9CteI1lEK+Vnk57ThMA0GCSqGSIb3DQEBCwUAMH0xCzAJBgNVBAYTAklMMRYwFAYD VQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0 ZSBTaWduaW5nMSkwJwYDVQQDEyBTdGFydENvbSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAe Fw0xNTEyMTYwMTAwMDVaFw0zMDEyMTYwMTAwMDVaMHUxCzAJBgNVBAYTAklMMRYwFAYDVQQK Ew1TdGFydENvbSBMdGQuMSkwJwYDVQQLEyBTdGFydENvbSBDZXJ0aWZpY2F0aW9uIEF1dGhv cml0eTEjMCEGA1UEAxMaU3RhcnRDb20gQ2xhc3MgMSBDbGllbnQgQ0EwggEiMA0GCSqGSIb3 DQEBAQUAA4IBDwAwggEKAoIBAQC9fdr3w6J9g/Zbgv3bW1+uHht1wLUZr5gkrLtXedg17Ake fMyUGwrQdvwObhajcVmnKVxhrUwkZPXRAwZZosRHfEIi5FH7x6SV/8Sp5lZEuiMnvMFG2MzL A84J6Ws5T4NfXZ0qn4TPgnr3X2vPVS51M7Ua9nIJgn8jvTra4eyyQzxvuA/GZwKg7VQfDCmC S+kICslYYWgXOMt2xlsSslxLce0CGWRsT8EpMyt1iDflSjXZIsE7m1uTyHaKZspMLyIyz6my Su8j8BWWHpChNNeTrFuhVfrOAyDPFJVUvKZCLKBhibTLloyy+LatoWELrjdI4a8StZY8+dIR 9t4APXGzAgMBAAGjggFkMIIBYDAOBgNVHQ8BAf8EBAMCAQYwHQYDVR0lBBYwFAYIKwYBBQUH AwIGCCsGAQUFBwMEMBIGA1UdEwEB/wQIMAYBAf8CAQAwMgYDVR0fBCswKTAnoCWgI4YhaHR0 cDovL2NybC5zdGFydHNzbC5jb20vc2ZzY2EuY3JsMGYGCCsGAQUFBwEBBFowWDAkBggrBgEF BQcwAYYYaHR0cDovL29jc3Auc3RhcnRzc2wuY29tMDAGCCsGAQUFBzAChiRodHRwOi8vYWlh LnN0YXJ0c3NsLmNvbS9jZXJ0cy9jYS5jcnQwHQYDVR0OBBYEFCSBbDlhvkkPj7cbRivJKLUn SG1oMB8GA1UdIwQYMBaAFE4L7xqkQFulF2mHMMo0aEPQQa7yMD8GA1UdIAQ4MDYwNAYEVR0g ADAsMCoGCCsGAQUFBwIBFh5odHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3kwDQYJKoZI hvcNAQELBQADggIBAIvj94fsAYuErQ8BAluc4SMnIwS9NPBwAm5SH9uh2NCXTq7im61g7F1L IiNI/+wq37fUuaMbz4g7VarKQTgf8ubs0p7NZWcIe7Bvem2AWaXBsxsaRTYw5kG3DN8pd1hS EUuFoTa7DmNeFe8tiK1BrL3rbA/m48jp4AiFXgvxprJrW7izsyetOrRHPbkW4Y07v29MdhaP v3u1JELyszXqOzjIYo4sWlC8iDQXwgSW/ntvWy2n4LuiaozlCfXl149tKeqvwlvrla2Yklue /quWp9j9ou4T/OY0CXMuY+B8wNK0ohd2D4ShgFlMSjzAFRoHGKF81snTr2d1A7Ew02oF6UQy CkC2aNNsK5cWOojBar5c7HplX9aHYUCZouxIeU28SONJAxnATgR4cJ2jrpmYSz/kliUJ46S6 UpVDo/ebn9c6PaM/XtDYCCaM/7XX6wc3s++sbQ7CtCn1Ax7df6ufQbwyO0V+oFa9H0KAsjHM zcwk3EV2B2NLatidKE/m7G+rB9m+FlVgIiSp0mGlg43QO9Kh1+JqvTCIzv2bJJkmPMLQJNuK KwHNL8F4GGp6jbAV+WL+LDeGfVcq8DHS3LrD+xyYEXQBiqZEdiPVOMxLDSUCXsDO0uCWpaNQ 8j6y6S9p0xE/Ga0peVLadVHhqf9nXqKaxnr358VgfrxzUIrvOaOjMYIDzDCCA8gCAQEwgYkw dTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKTAnBgNVBAsTIFN0YXJ0 Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMwIQYDVQQDExpTdGFydENvbSBDbGFzcyAx IENsaWVudCBDQQIQRUZXla0RfF+RsG1dLXCwoDANBglghkgBZQMEAgEFAKCCAhMwGAYJKoZI hvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTcwMjA1MTczNTMzWjAvBgkq hkiG9w0BCQQxIgQg4NQP+omZGvsJczulvAUBlhaYlRBt9N6eXp48/EjfOKswbAYJKoZIhvcN AQkPMV8wXTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3 DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBmgYJKwYB BAGCNxAEMYGMMIGJMHUxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSkw JwYDVQQLEyBTdGFydENvbSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEjMCEGA1UEAxMaU3Rh cnRDb20gQ2xhc3MgMSBDbGllbnQgQ0ECEEVGV5WtEXxfkbBtXS1wsKAwgZwGCyqGSIb3DQEJ EAILMYGMoIGJMHUxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSkwJwYD VQQLEyBTdGFydENvbSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEjMCEGA1UEAxMaU3RhcnRD b20gQ2xhc3MgMSBDbGllbnQgQ0ECEEVGV5WtEXxfkbBtXS1wsKAwDQYJKoZIhvcNAQEBBQAE ggEARdz6AM0G9ncIBAk7l8ii/QR/W3Ovn0S97sRUobDoRu26k6byIsAl7vSgQSKAx2ExQL73 UjZtSaQQ3Bd99nPPAxGIMFIjZ/D55eB8t6+W61rTI7jhzuHifdG/XmLp4ELM0i+wfjFYMiiJ hkGm8bpBIVlfh4rwZscrmfrTOwbJJT6/tCtH185mynXP8vxCA/31M78E3L01436GI6LtaJ8z Z7HpkbKANlae4f7AIHv+aFU+tgkGbzFWcb6abDHYqANfxAeuKn6cRBEN/5mvhio7LjAM4qcU xIxGb2aA5uySOtNdLtVh3hj9q3OXhZkM20/dCQU5PZxaThl4HpqbZH2QbwAAAAAAAA== --------------ms020706080404060907060004--

1 0

(ITS#8581) slapd-meta backend SSL negociation timeout
by louis.chanouha＠univ-toulouse.fr 04 Feb '17

04 Feb '17

Full_Name: Louis Chanouha Version: 2.4.40 OS: Debian 8 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (90.76.56.40) Hello, I experience some problems with slapd-meta with ldaps backend. gnuTLS (or openssl) negociation timeout seems not to be handled, and i can't find any reference to modify this timeout on docs. My server becames unresponsive (too many connexion slots) when a ssl-secured backend server time out after TCP connexion establishment. To reproduce the error, i have an meta directory configured like this: database meta suffix "dc=localauth" rootdn "%n=Manager,dc=localauth" rootpw XXX uri "ldaps://localhost:666/ou=UT,dc=localauth" lastmod off suffixmassage "ou=UT,dc=localauth" "ou=people,dc=example,dc=fr" timeout 1 conn-ttl 1 network-timeout 1 And i launch a netcat to listen to the 666 port: nc -l -p 666 Then, this command never time out: ldapwhoami -H ldap://YYYY:9009 -D uid=me,ou=UT,dc=localauth -W Error does not happen when no ssl used ("timeout 1" option works well) OS: Debian 8 Jessie x64 slapd: 2.4.40+dfsg-1+deb8u2 gnutls: 3.3.8-6+deb8u4 Sorry for my english, and thanks for the help, Regards, Louis Chanouha University of Toulouse

1 0

(ITS#8580) force openssl use the server side cipher preference
by sca+openldap＠andreasschulze.de 03 Feb '17

03 Feb '17

Full_Name: Andreas Schulze Version: RE24 OS: Linux URL: ftp://ftp.openldap.org/incoming/andreas-schulze-20170203.patch Submission from: (NULL) (2001:a60:f0b4:e502:758b:b0b2:3fc:f121) In OpenSSL client and Server may select a cipher. The patch force the cipher preference is force by the server and not by the client, which is a openssl default Let the server select ciphers is best practice for webservers for example.

1 0

(ITS#8579) LMDB: me_fd should be O_CLOEXEC on POSIX systems
by lmb＠cloudflare.com 03 Feb '17

03 Feb '17

Full_Name: Lorenz Bauer Version: OS: Linux URL: Submission from: (NULL) (2a06:98c0:1000:8200:18fd:e772:495e:6163) This is in some ways a follow up to ITS#8505. In the issue I argued that LMDB did not deal well with fork/exec. Hallvard committed a fix in 04acac634a7b276332e2. I think the fix still has one major weakness: me_fd does not have O_CLOEXEC set. Now, Hallvard omitted this change on purpose. mdb_env_get_fd() exposes me_fd to the user, so there could conceivably be client code out there which expects the fd to persist across exec(). (Please correct my if I misunderstood your argument.) I believe that the correct action is to set O_CLOEXEC on me_fd by default, and break such client code. 1. Using mdb_env_get_fd this way is Undefined Behaviour (according to the doc) Before ITS#8505, the documentation made it sound like ANY use after fork() / exec() is disallowed. At the same time, mdb_env_get_fd made no mention / promises wrt exec() behaviour. Adopting O_CLOEXEC in my opinion does not violate the API set out so far. We can, in the opposite, clarify what is acceptable use (as Hallvard already has done). 2. mdb_env_get_fd has inconsistent semantics across OSs When creating file handles on Windows we pass NULL as the lpSecurityAttributes argument to CreateFileW: If this parameter is NULL, the handle returned by CreateFile cannot be inherited by any child processes the application may create [...] me_fd already has O_CLOEXEC on Windows. 3. Manually closing me_fd after fork() is not possible in all environments Hallvard suggests calling fork(), close(mdb_env_get_fd()) and then exec() for users which do not want to leak me_fd to child processes. We use LMDB from the Go platform, which does not expose fork and exec separately (due to the well-known pitfalls they have). We can't use Hallvard's suggestion therefore. 4. me_fd can still be passed around by dup()ing the handle If there are legitimate uses of passing the handle around, users can explicitly dup the handle and then pass it on to child processes. I hope my arguments are convincing enough to make the change before the next release. The benefits are * Consistent semantics between OS * (In my view) saner defaults * and a solution which works well across environments. The downside is that we might break unknown client code. I can'c come up with a use case of passing me_fd to children, so I suspect the risk is low. The patch itself is trivial, and I'm happy to contribute it if desired. Lorenz

1 0

(ITS#8578) remove unused-variables in RE24 testing call (2.4.45)
by sca+openldap＠andreasschulze.de 01 Feb '17

01 Feb '17

Full_Name: A. Schulze Version: RE24 testing call (2.4.45) OS: URL: ftp://ftp.openldap.org/incoming/andreas-schulze-20170201.patch Submission from: (NULL) (2001:a60:f0b4:e502:758b:b0b2:3fc:f121) the patch remove variables that are declared but unused.

1 0

(ITS#8577) Accesslog overlay hangs slapd depending on module loading order
by mj＠netauth.com 01 Feb '17

01 Feb '17

Full_Name: Mike Jackson Version: 2.4.44 OS: Oracle Linux Server release 7.2 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (194.157.185.162) Same issue as Stroeder mentioned here: http://www.openldap.org/lists/openldap-bugs/201111/msg00027.html If accesslog.la is loaded before syncprov.la, slapd will stop accepting connections immediately after accesslog overlay is added. olcModuleLoad: {0}ppolicy.la olcModuleLoad: {1}auditlog.la olcModuleLoad: {2}back_ldap.la olcModuleLoad: {3}unique.la olcModuleLoad: {4}accesslog.la olcModuleLoad: {5}syncprov.la ldapadd -f dn: oDatatabase={4}mdb,cn=config objectClass: olcDatabaseConfig objectClass: olcMdbConfig olcDatabase: {4}mdb olcDbDirectory: /var/lib/ldap/accesslog olcSuffix: cn=log olcDbIndex: default eq olcDbIndex: entryCSN,objectClass,reqEnd,reqResult,reqStart olcDbMaxSize: 1073741824 olcDbMode: 0600 olcAccess: {0}to * by dn.children="ou=global-admins,ou=admin-users,dc=foo,dc=net" read dn: olcOverlay=accesslog,olcDatabase={4}mdb,cn=config objectClass: olcOverlayConfig objectClass: olcAccessLogConfig olcOverlay: accesslog olccccessLogDB<ncn=log olcAccessLogOps: writes olcAccessLogSuccess: TRUE olcAccessLogPurge: 7+00:00 1+00:00

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs