openldap-bugs January 2022

openldap-bugs@openldap.org

1 participants
144 discussions

[Issue 9759] New: olcRetcodeItem doesn't implement ordered values correctly
by openldap-its＠openldap.org 20 Jan '22

20 Jan '22

https://bugs.openldap.org/show_bug.cgi?id=9759 Issue ID: 9759 Summary: olcRetcodeItem doesn't implement ordered values correctly Product: OpenLDAP Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: overlays Assignee: bugs(a)openldap.org Reporter: ondra(a)mistotebe.net Target Milestone: --- olcRetcodeItem is marked X-ORDERED 'VALUES' so it has to handle ordered inserts, which is currently not implemented. -- You are receiving this mail because: You are on the CC list for the issue.

1 6

[Issue 9756] New: syncprov_play_accesslog doesn't check minCSN properly
by openldap-its＠openldap.org 20 Jan '22

20 Jan '22

https://bugs.openldap.org/show_bug.cgi?id=9756 Issue ID: 9756 Summary: syncprov_play_accesslog doesn't check minCSN properly Product: OpenLDAP Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: overlays Assignee: bugs(a)openldap.org Reporter: ondra(a)mistotebe.net Target Milestone: --- When asked to replay the accesslog database for a refresh delete, syncprov doesn't interpret the minCSN data correctly, resulting in: - an inaccurate refresh if a purge removed some important data in the meantime - potentially a very expensive query when consumer is actually up to date w.r.t. to some sids in our contextCSN -- You are receiving this mail because: You are on the CC list for the issue.

1 6

[Issue 9752] New: Improperly normalized minCSN values in accesslog
by openldap-its＠openldap.org 20 Jan '22

20 Jan '22

https://bugs.openldap.org/show_bug.cgi?id=9752 Issue ID: 9752 Summary: Improperly normalized minCSN values in accesslog Product: OpenLDAP Version: 2.5.9 Hardware: All OS: All Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: overlays Assignee: bugs(a)openldap.org Reporter: hyc(a)openldap.org Target Milestone: --- The CSN matching rules require normalized values to be provided. When normalized values are provided to attr_merge they must be distinct from the regular values. accesslog.c:1982 is providing the same berval in both regular and normalized value, which triggers an assert failure for this consistency check. -- You are receiving this mail because: You are on the CC list for the issue.

1 5

[Issue 9747] New: dynlist overlay breaks member compare operation for groups
by openldap-its＠openldap.org 20 Jan '22

20 Jan '22

https://bugs.openldap.org/show_bug.cgi?id=9747 Issue ID: 9747 Summary: dynlist overlay breaks member compare operation for groups Product: OpenLDAP Version: 2.5.8 Hardware: All OS: All Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: overlays Assignee: bugs(a)openldap.org Reporter: henson(a)acm.org Target Milestone: --- Given the following group: dn: uid=unxadmin,ou=group,dc=cpp,dc=edu objectClass: groupOfNames objectClass: cppGroup objectClass: posixGroup uid: unxadmin cn: Unix Administrators gidNumber: 17730 member: member: uid=gkuri,ou=user,dc=cpp,dc=edu member: uid=henson,ou=user,dc=cpp,dc=edu memberUid: gkuri memberUid: henson and the following dynlist config: dynlist-attrset groupOfURLs memberURL member+memberOf@groupOfNames ldap compare operations checking group membership fail erroneously: # ldapcompare -x -H ldaps://ldap-vmc-01.ldap.cpp.edu/ uid=unxadmin,ou=group,dc=cpp,dc=edu member:uid=henson,ou=user,dc=cpp,dc=edu FALSE If the dynlist-attrset configuration is removed, the compare works as expected: # ldapcompare -x -H ldaps://ldap-vmc-01.ldap.cpp.edu/ uid=unxadmin,ou=group,dc=cpp,dc=edu member:uid=henson,ou=user,dc=cpp,dc=edu TRUE -- You are receiving this mail because: You are on the CC list for the issue.

1 9

[Issue 9749] New: logoldattr documentation is misleading
by openldap-its＠openldap.org 20 Jan '22

20 Jan '22

https://bugs.openldap.org/show_bug.cgi?id=9749 Issue ID: 9749 Summary: logoldattr documentation is misleading Product: OpenLDAP Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: documentation Assignee: bugs(a)openldap.org Reporter: ondra(a)mistotebe.net Target Milestone: --- Reading the accesslog manpage, someone might expect that attributes specified in logoldattr would be logged regardless of whether the entry being modified matches any of the configured filters. This is not the case and should be clarified. -- You are receiving this mail because: You are on the CC list for the issue.

1 5

[Issue 9707] New: Documentation synchronisation ODSEE --> openldap
by openldap-its＠openldap.org 20 Jan '22

20 Jan '22

https://bugs.openldap.org/show_bug.cgi?id=9707 Issue ID: 9707 Summary: Documentation synchronisation ODSEE --> openldap Product: OpenLDAP Version: 2.5.4 Hardware: All OS: All Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: documentation Assignee: bugs(a)openldap.org Reporter: laurent.revillion(a)icloud.com Target Milestone: --- There is no documentation about the synchronisation between ODSEE and Openldap 2.5. Will there be one? -- You are receiving this mail because: You are on the CC list for the issue.

1 16

[Issue 9766] New: slapo-autogroup handling of X-VALUES ORDERED is incorrect
by openldap-its＠openldap.org 20 Jan '22

20 Jan '22

https://bugs.openldap.org/show_bug.cgi?id=9766 Issue ID: 9766 Summary: slapo-autogroup handling of X-VALUES ORDERED is incorrect Product: OpenLDAP Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: contrib Assignee: bugs(a)openldap.org Reporter: ondra(a)mistotebe.net Target Milestone: --- When adding a value to the beginning of the list (position {0}), internally, it gets added to the end instead, this is incorrect. -- You are receiving this mail because: You are on the CC list for the issue.

1 4

[Issue 9777] New: Happy new year
by openldap-its＠openldap.org 20 Jan '22

20 Jan '22

https://bugs.openldap.org/show_bug.cgi?id=9777 Issue ID: 9777 Summary: Happy new year Product: OpenLDAP Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: documentation Assignee: bugs(a)openldap.org Reporter: orel(a)melix.net Target Milestone: --- Created attachment 868 --> https://bugs.openldap.org/attachment.cgi?id=868&action=edit 2021 changed to 2022 on copyright Just bump the year to 2022 -- You are receiving this mail because: You are on the CC list for the issue.

1 6

[Issue 9781] New: regression test its4448 assertion
by openldap-its＠openldap.org 20 Jan '22

20 Jan '22

https://bugs.openldap.org/show_bug.cgi?id=9781 Issue ID: 9781 Summary: regression test its4448 assertion Product: OpenLDAP Version: 2.6.0 Hardware: All OS: All Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: backends Assignee: bugs(a)openldap.org Reporter: quanah(a)openldap.org Target Milestone: --- Starting with OpenLDAP 2.5, the ITS4448 regression case no longer passes and instead triggers an assertion: slapd: request.c:1672: ldap_find_request_by_msgid: Assertion `lr->lr_refcnt == 0' failed. -- You are receiving this mail because: You are on the CC list for the issue.

1 8

[Issue 9760] New: back-wt is not set "SLAP_DBFLAG_CLEAN"
by openldap-its＠openldap.org 20 Jan '22

20 Jan '22

https://bugs.openldap.org/show_bug.cgi?id=9760 Issue ID: 9760 Summary: back-wt is not set "SLAP_DBFLAG_CLEAN" Product: OpenLDAP Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: backends Assignee: bugs(a)openldap.org Reporter: hamano(a)osstech.co.jp Target Milestone: --- https://github.com/osstech-jp/openldap/issues/10 yasumatk says: > If "SLAP_DBFLAG_CLEAN" is not set for a backend database, the initialization process of the syncprov overlay reads all entries in the backend database. As a result, slapd startup time will increase on the back-wt database with a large number of entries. So, back-wt should be set "SLAP_DBFLAG_CLEAN" in back-wt/init.c. -- You are receiving this mail because: You are on the CC list for the issue.

1 4

← Newer
1
...
9
10
11
12
13
14
15
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 January 2022