Full_Name: Havard Eidnes
Version: 2.4.44
OS: NetBSD
URL:
Submission from: (NULL) (2001:700:1:0:eeb1:d7ff:fe59:fbaa)
Hi,
CVE-2015-3276 appears to be unfixed in 2.4.44, and from several
attempts at finding the bug reported in your mailing list archive
I came up empty. So ... The best I've found from this CVE is
RedHat's bugzilla entry at
https://bugzilla.redhat.com/show_bug.cgi?id=1238322
which contains a (suggested) patch.
Summarized:
The openldap (for NSS) emulation of the openssl cipherstring parsing code
incorrectly implements the multi-keyword mode.
As a consequence anyone using a combination like:
ECDH+SHA
will not get the expected set of ciphers [...]
(I'm somewhat dismayed that this was apparently not reported upstream
earlier...)
Best regards,
- HÃ¥vard
Full_Name: Hallvard B Furuseth
Version: LMDB_0.9.18
OS:
URL: ftp://ftp.openldap.org/incoming/Hallvard-Furuseth-161210.c
Submission from: (NULL) (81.191.45.31)
Submitted by: hallvard
...because mdb_dbi_open() does not track its cursor. Demo enclosed.
Fix: Put the mdb_cursor_put() in WITH_CURSOR_TRACKING(mc, ...).
I do wonder why failing to track one cursor apparently breaks another
cursor, instead of the un-tracked one. Though maybe the un-tracked
cursor is broken, and writing through it goes to the wrong place.
Full_Name: Quanah Gibson-Mount
Version: HEAD
OS: Linux
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (47.208.148.26)
When running test062, it sometimes core dumps in syncprov abandon. I will
directly email the backtrace as the ITS software breaks them horribly.
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 test suite should be expanded to have SSL related test. To do this, we'll
need a CA cert, server cert for "localhost", and a couple of user certs (for
babs and/or bjorn).
Test can then validate startTLS, ldaps, and client cert auth, using both an
exact matching DN for one user and one requiring an authz-regexp map.
Tests only run if SSL was enabled for the build.
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)
When running the regression suite via "make its" it will only run with the first
defined backend, rather than all compiled backends like the test suite does.
This needs to be fixed.
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 slapd.conf/slapd-config (5) man pages need to be updated to note that the
"interval" parameter to olcSyncrepl is required.
Actually, it's an invalid issue.
The problem is all in teh sequence of updates on the provider. There are
6 possible scenario, depending on which order we inject the serverID,
teh syncprov overlay and the data :
1) data, serverID, syncprov : invalid. All the data will have a wrong
entryCSN
2) data, syncprov,serverID : invalid, same reason
3) serverID, syncprov, data : All work properly
4) syncprov, serverID, data : All work properly
5) serverID, data, syncprov : the corner case scenario... Syncprov has
no way to know which contextCSN to generate. The only way for the server
to replicate is to do an update, so that the contextCSN is properly
generated.
6) syncprov, data, serverID : invalid. All the data will have a wrong
entryCSN
Bottom line, *always* inject the serverID and syncprov *before injecting
some data, or be ready to do an update after having injected syncprov
and serverID.
=20
Le 21/10/16 =C3=A0 23:45, openldap-its(a)OpenLDAP.org a =C3=A9crit :
> *** THIS IS AN AUTOMATICALLY GENERATED REPLY ***
>
> Thanks for your report to the OpenLDAP Issue Tracking System. Your
> report has been assigned the tracking number ITS#8521.
>
> One of our support engineers will look at your report in due course.
> Note that this may take some time because our support engineers
> are volunteers. They only work on OpenLDAP when they have spare
> time.
>
> If you need to provide additional information in regards to your
> issue report, you may do so by replying to this message. Note that
> any mail sent to openldap-its(a)openldap.org with (ITS#8521)
> in the subject will automatically be attached to the issue report.
>
> mailto:openldap-its@openldap.org?subject=3D(ITS#8521)
>
> You may follow the progress of this report by loading the following
> URL in a web browser:
> http://www.OpenLDAP.org/its/index.cgi?findid=3D8521
>
> Please remember to retain your issue tracking number (ITS#8521)
> on any further messages you send to us regarding this report. If
> you don't then you'll just waste our time and yours because we
> won't be able to properly track the report.
>
> Please note that the Issue Tracking System is not intended to
> be used to seek help in the proper use of OpenLDAP Software.
> Such requests will be closed.
>
> OpenLDAP Software is user supported.
> http://www.OpenLDAP.org/support/
>
> --------------
> Copyright 1998-2007 The OpenLDAP Foundation, All Rights Reserved.
>
--=20
Emmanuel Lecharny
Symas.comdirectory.apache.org