openldap-bugs April 2020

openldap-bugs@openldap.org

2 participants
338 discussions

[Bug 6347] JLDAP: LDIFReader should use UTF-8 character set instead of US-ASCII
by openldap-its＠openldap.org 30 Apr '20

30 Apr '20

https://bugs.openldap.org/show_bug.cgi?id=6347 --- Comment #2 from drmuey+github(a)gmail.com --- Would this make it so that non-ascii strings ar enot base 64 encoded? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 9059] session log parsing triggers cascading REFRESH
by openldap-its＠openldap.org 30 Apr '20

30 Apr '20

https://bugs.openldap.org/show_bug.cgi?id=9059 --- Comment #5 from Howard Chu <hyc(a)openldap.org> --- (In reply to Ondřej Kuzník from comment #4) > The response is triggered by > https://git.openldap.org/openldap/openldap/-/blob/ > fd23680a447b9efe1a481dd64d9c57f3873f3108/servers/slapd/overlays/syncprov. > c#L2886 but it looks like the sessionlog has already been replayed correctly. > > In that case, we are either finished or have a persistent search set up and > all remaining responses are queued up to be sent, so we shouldn't even care > if we can still find the CSN in the DB... Moving that whole `if` under > `do_present == 1` should then be enough and it might not be related to bug > 8125 at all. > > But then I might be missing something. Sounds OK. the MinCSN check is to make sure the DB hasn't already moved on past the consumer's cookie, but if the sessionlog validly spans the consumer cookie then the check isn't needed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 8155] add support for cacertdir with gnutls
by openldap-its＠openldap.org 30 Apr '20

30 Apr '20

https://bugs.openldap.org/show_bug.cgi?id=8155 Ryan Tandy <ryan(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |IN_PROGRESS --- Comment #2 from Ryan Tandy <ryan(a)openldap.org> --- https://git.openldap.org/openldap/openldap/-/merge_requests/60 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 9059] session log parsing triggers cascading REFRESH
by openldap-its＠openldap.org 30 Apr '20

30 Apr '20

https://bugs.openldap.org/show_bug.cgi?id=9059 --- Comment #4 from Ondřej Kuzník <ondra(a)mistotebe.net> --- The response is triggered by https://git.openldap.org/openldap/openldap/-/blob/fd23680a447b9efe1a481dd64… but it looks like the sessionlog has already been replayed correctly. In that case, we are either finished or have a persistent search set up and all remaining responses are queued up to be sent, so we shouldn't even care if we can still find the CSN in the DB... Moving that whole `if` under `do_present == 1` should then be enough and it might not be related to bug 8125 at all. But then I might be missing something. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 9240] New: Can't log to stdout/stderr
by openldap-its＠openldap.org 28 Apr '20

28 Apr '20

https://bugs.openldap.org/show_bug.cgi?id=9240 Bug ID: 9240 Summary: Can't log to stdout/stderr Product: OpenLDAP Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: --- Component: slapd Assignee: bugs(a)openldap.org Reporter: hadmut(a)danisch.de Target Milestone: --- Hi, slapd can send its logs and messages to syslog, which is nice and good in common Unix/Linux environments, but I didn't see any way to have the logs sent to stdout/stderr instead of syslog. When run in a docker/kubernetes container, which is a typical use nowadays, it should be run as a single process, and not require a separate syslog process just to write some logs to a file. There are dirty workarounds, but if run cleanly, it should be a standalone process. Therefore, it would be nice if slap had a container mode, where - it doesn't fork (currently available only through debugging mode) - sends logging to stdout/stderr instead of syslog regards -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 9202] Should limit depth of nested filters
by openldap-its＠openldap.org 28 Apr '20

28 Apr '20

https://bugs.openldap.org/show_bug.cgi?id=9202 --- Comment #9 from Quanah Gibson-Mount <quanah(a)openldap.org> --- (In reply to Michael Ströder from comment #8) > Please add the CVE-Id to CHANGES so downstream packagers take note of it. That's currently not a tracked item in the format of the CHANGES file. I have been thinking of adding a customized field to bugzilla to track CVEs (we did that at a prior job I worked at). We may want to consider a format change for RE25 to allow for CVEs in the CHANGES file as well. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 9202] Should limit depth of nested filters
by openldap-its＠openldap.org 28 Apr '20

28 Apr '20

https://bugs.openldap.org/show_bug.cgi?id=9202 --- Comment #8 from Michael Ströder <michael(a)stroeder.com> --- Please add the CVE-Id to CHANGES so downstream packagers take note of it. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 9202] Should limit depth of nested filters
by openldap-its＠openldap.org 28 Apr '20

28 Apr '20

https://bugs.openldap.org/show_bug.cgi?id=9202 --- Comment #7 from carnil(a)debian.org --- (In reply to Quanah Gibson-Mount from comment #3) > CVE-2020-10704 FWIW: Note that there is a dedicated CVE id for this issue in OpenLDAP, which is CVE-2020-12243. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 9233] New: Add argon2 module to contrib
by openldap-its＠openldap.org 28 Apr '20

28 Apr '20

https://bugs.openldap.org/show_bug.cgi?id=9233 Bug ID: 9233 Summary: Add argon2 module to contrib Product: OpenLDAP Version: 2.4.50 Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: --- Component: contrib Assignee: bugs(a)openldap.org Reporter: quanah(a)openldap.org Target Milestone: --- Now that the argon2 module is complete, add it to contrib for 2.4.50 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 9230] New: slapindex man page states that truncate option (-t) only works with Quick Mode (-q)
by openldap-its＠openldap.org 28 Apr '20

28 Apr '20

https://bugs.openldap.org/show_bug.cgi?id=9230 Bug ID: 9230 Summary: slapindex man page states that truncate option (-t) only works with Quick Mode (-q) Product: OpenLDAP Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: --- Component: documentation Assignee: bugs(a)openldap.org Reporter: requate(a)univention.de Target Milestone: --- Created attachment 712 --> https://bugs.openldap.org/attachment.cgi?id=712&action=edit Patch proposal for doc/man/man8/slapindex.8 The slapindex man page states that truncate option (-t) only works with Quick Mode (-q), but from the source code I cannot see a reason for this restriction. Git blame shows that the statement predates back-mdb. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

← Newer
1
2
3
4
5
6
7
8
9
...
34
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs April 2020