openldap-bugs

openldap-bugs@openldap.org

1 participants
20895 discussions

[Issue 6467] syncrepl enhancements
by openldap-its＠openldap.org 20 May '21

20 May '21

https://bugs.openldap.org/show_bug.cgi?id=6467 --- Comment #9 from Quanah Gibson-Mount <quanah(a)openldap.org> --- Commits: • c216ef53 by Ondřej Kuzník at 2021-05-15T10:01:18+01:00 ITS#6467 Reset avl root after releasing the tree • 5943a334 by Ondřej Kuzník at 2021-05-15T10:01:51+01:00 ITS#6467 Adjust log message -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 7335] Create process for updating man pages to handle both cn=config and slapd.conf configurations
by openldap-its＠openldap.org 20 May '21

20 May '21

https://bugs.openldap.org/show_bug.cgi?id=7335 Quanah Gibson-Mount <quanah(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords|OL_2_5_REQ | Target Milestone|2.5.5 |2.6.0 -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 8882] Null Attribute Value Overlay
by openldap-its＠openldap.org 20 May '21

20 May '21

https://bugs.openldap.org/show_bug.cgi?id=8882 --- Comment #9 from tamim.ziai(a)daasi.de <tamim.ziai(a)daasi.de> --- The attached file is derived from OpenLDAP Software. All of the modifications to OpenLDAP Software represented in the following patch(es) were developed by DAASI International. DAASI International has not assigned rights and/or interest in this work to any party. I, Tamim Ziai is authorized by DAASI International to release this work under the following terms. The attached modifications to OpenLDAP Software are subject to the following notice: Copyright 2019 DAASI International Redistribution and use in source and binary forms, with or without modification, are permitted only as authorized by the OpenLDAP Public License. -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 8679] Update release download page
by openldap-its＠openldap.org 19 May '21

19 May '21

https://bugs.openldap.org/show_bug.cgi?id=8679 Quanah Gibson-Mount <quanah(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |VERIFIED -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 8679] Update release download page
by openldap-its＠openldap.org 19 May '21

19 May '21

https://bugs.openldap.org/show_bug.cgi?id=8679 Quanah Gibson-Mount <quanah(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 9487] New: Committed changes not saved to accesslog during shutdown
by openldap-its＠openldap.org 17 May '21

17 May '21

https://bugs.openldap.org/show_bug.cgi?id=9487 Issue ID: 9487 Summary: Committed changes not saved to accesslog during shutdown Product: OpenLDAP Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Keywords: replication Severity: normal Priority: --- Component: overlays Assignee: bugs(a)openldap.org Reporter: ondra(a)mistotebe.net Target Milestone: --- If there is inbound write traffic when slapd is asked to shut down, some of these operations get written to the main database but accesslog might be prevented from ADDing the log entry into its own database (presumably since slapd is shutting down already). This prevents these updates from being replicated in a deltasync scenario and silently desync. -- You are receiving this mail because: You are on the CC list for the issue.

1 6

[Issue 9553] New: Segfault in mdb_txn_abort handler caused by uninitialized pointer in mdb_reader_flush
by openldap-its＠openldap.org 17 May '21

17 May '21

https://bugs.openldap.org/show_bug.cgi?id=9553 Issue ID: 9553 Summary: Segfault in mdb_txn_abort handler caused by uninitialized pointer in mdb_reader_flush Product: OpenLDAP Version: 2.4.58 Hardware: x86_64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: --- Component: backends Assignee: bugs(a)openldap.org Reporter: jrddunbr(a)amazon.com Target Milestone: --- This is for OpenLDAP 2.4.58, git commit 350ede08564ab14a45884c6f7c32419d98a75468 best I can tell. I have located an issue in mdb_reader_flush where it appears that an uninitialized pointer causes segfaults when threading is disabled. In the following function: https://git.openldap.org/openldap/openldap/-/blob/350ede08564ab14a45884c6f7… ``` void mdb_reader_flush( MDB_env *env ) { void *data; void *ctx = ldap_pvt_thread_pool_context(); if ( !ldap_pvt_thread_pool_getkey( ctx, env, &data, NULL ) ) { ldap_pvt_thread_pool_setkey( ctx, env, NULL, 0, NULL, NULL ); mdb_reader_free( env, data ); } } ``` the `void *data;` gets random values and is not initialized to NULL; when there is no thread pool the functions after it return without doing anything, and that pointer is passed down into mdb_reader_free, which passes down to mdb_txn_abort, where it is (recursively) de-referenced until the pointer is NULL. This causes a segfault, as that condition is not reached before it tries reading invalid memory addresses. The fix appears to be to make the following modification: Change `void *data;` to `void *data = NULL;`. I don't actually know much about the internals of this application, so I wanted to make sure that this is the correct solution before making a pull request for it. Apologies if my C terminology is not up to snuff; this is not my forte. -- You are receiving this mail because: You are on the CC list for the issue.

1 3

[Issue 8820] ldap_get_attribute_ber() function needs to be documented
by openldap-its＠openldap.org 14 May '21

14 May '21

https://bugs.openldap.org/show_bug.cgi?id=8820 Quanah Gibson-Mount <quanah(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|hyc(a)openldap.org |ondra(a)mistotebe.net -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 8820] ldap_get_attribute_ber() function needs to be documented
by openldap-its＠openldap.org 14 May '21

14 May '21

https://bugs.openldap.org/show_bug.cgi?id=8820 Quanah Gibson-Mount <quanah(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords|OL_2_5_REQ | Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Quanah Gibson-Mount <quanah(a)openldap.org> --- Commits: • 363f1056 by Ondřej Kuzník at 2021-05-14T08:18:05+01:00 ITS#8820 Document ldap_get_attribute_ber() -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 9540] New: userSMIMECertificate needs to be binary
by openldap-its＠openldap.org 12 May '21

12 May '21

https://bugs.openldap.org/show_bug.cgi?id=9540 Issue ID: 9540 Summary: userSMIMECertificate needs to be binary Product: OpenLDAP Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: --- Component: backends Assignee: bugs(a)openldap.org Reporter: openldap.ms(a)savignano.net Target Milestone: --- OpenLDAP uses inetOrgPerson.schema with the following note on userSMIMECertificate attribute: # userSMIMECertificate # [...] Values for # this attribute are to be stored and requested in binary form, as # 'userSMIMECertificate;binary'. [...] but a line is added saying specifically ## OpenLDAP note: ";binary" transfer should NOT be used as syntax is binary This seems to make no sense. According to RFC 2798 which define inetOrgPerson and the useSMIMECertificate (first comment is quoted from there), this attribute must be stored and requested as userSMIMECertificate;binary. OpenLDAP does not do so. I don't understand the explanation "as syntax is binary". This leads to problems with clients following RFC 2798 and requesting the attribute as userSMIMECertificate;binary because OpenLDAP does not send userSMIMECertificate instead, but sends nothing at all (as if attribute would not exist). I think this is a bug. OpenLDAP does not follow RFC 2798 and this causes compatibility problems. -- You are receiving this mail because: You are on the CC list for the issue.

1 8

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs