openldap-bugs December 2021

openldap-bugs@openldap.org

1 participants
143 discussions

[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 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

[Issue 9753] New: back-mdb index incorrect on modify/replace
by openldap-its＠openldap.org 20 Jan '22

20 Jan '22

https://bugs.openldap.org/show_bug.cgi?id=9753 Issue ID: 9753 Summary: back-mdb index incorrect on modify/replace Product: OpenLDAP Version: 2.4.6 Hardware: All OS: All Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: backends Assignee: bugs(a)openldap.org Reporter: hyc(a)openldap.org Target Milestone: --- When doing a modify/replace on an indexed attribute, back-mdb only deletes the old values from the index and doesn't add the new values into the index. -- You are receiving this mail because: You are on the CC list for the issue.

1 24

[Issue 9538] New: Accesslog entryCSN ordering is not always monotonous
by openldap-its＠openldap.org 12 Jan '22

12 Jan '22

https://bugs.openldap.org/show_bug.cgi?id=9538 Issue ID: 9538 Summary: Accesslog entryCSN ordering is not always monotonous Product: OpenLDAP Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: --- Component: overlays Assignee: bugs(a)openldap.org Reporter: ondra(a)mistotebe.net Target Milestone: --- For delta-sync replication, we rely on CSN order being preserved at all times. When logops includes anything more than "writes", we don't use li_op_rmutex to maintain serialisation. A concurrent write and another operation (like bind) can have the write have its csn assigned before the bind. But before the write finishes on the main DB and is logged, the bind has already hit accesslog. This entry out of order doesn't match the usual filter, so non-persist sessions will not notice, however running persist sessions could get a new cookie sent, depending on how things are ordered when they hit syncprov. A sample: ---- 8< ---- Apr 26 19:56:04 localhost slapd[43930]: conn=1003 op=41 ADD dn="uid=dm01-R1H2-41660,ou=People,dc=example,dc=com" Apr 26 19:56:04 localhost slapd[43930]: conn=1003 op=41 syncprov_matchops: recording uuid for dn=reqStart=20210426195604.000350Z,cn=accesslog on opc=0x7d3d2800dc50 Apr 26 19:56:04 localhost slapd[43930]: slap_get_csn: conn=1003 op=42 generated new csn=20210426195604.556053Z#000000#002#000000 manage=1 Apr 26 19:56:04 localhost slapd[43930]: slap_queue_csn: queueing 0x7d3d38148f60 20210426195604.556053Z#000000#002#000000 Apr 26 19:56:04 localhost slapd[43930]: conn=1005 op=1 BIND dn="dc=example,dc=com" method=128 Apr 26 19:56:04 localhost slapd[43930]: conn=1005 op=1 BIND dn="dc=example,dc=com" mech=SIMPLE bind_ssf=0 ssf=256 Apr 26 19:56:04 localhost slapd[43930]: conn=1003 op=41 RESULT tag=105 err=0 qtime=0.005874 etime=0.015182 text= Apr 26 19:56:04 localhost slapd[43930]: slap_get_csn: conn=1005 op=1 generated new csn=20210426195604.558683Z#000000#002#000000 manage=1 Apr 26 19:56:04 localhost slapd[43930]: slap_queue_csn: queueing 0x561f09113f80 20210426195604.558683Z#000000#002#000000 Apr 26 19:56:04 localhost slapd[43930]: conn=1005 op=1 syncprov_matchops: recording uuid for dn=reqStart=20210426195604.000364Z,cn=accesslog on opc=0x561f0900fcf0 Apr 26 19:56:04 localhost slapd[43930]: conn=1002 op=2 syncprov_qresp: set up a new syncres mode=4 csn=20210426195604.558683Z#000000#002#000000 Apr 26 19:56:04 localhost slapd[43930]: conn=1001 op=2 syncprov_qresp: set up a new syncres mode=4 csn=20210426195604.558683Z#000000#002#000000 Apr 26 19:56:04 localhost slapd[43930]: conn=1000 op=2 syncprov_qresp: set up a new syncres mode=4 csn=20210426195604.558683Z#000000#002#000000 Apr 26 19:56:04 localhost slapd[43930]: slap_graduate_commit_csn: removing 0x561f09113f80 20210426195604.558683Z#000000#002#000000 Apr 26 19:56:04 localhost slapd[43930]: conn=1005 op=1 RESULT tag=97 err=0 qtime=0.000020 etime=0.004297 text= Apr 26 19:56:04 localhost slapd[43930]: slap_queue_csn: queueing 0x7d3d38148250 20210426195604.556053Z#000000#002#000000 Apr 26 19:56:04 localhost slapd[43930]: slap_graduate_commit_csn: removing 0x7d3d38148250 20210426195604.556053Z#000000#002#000000 Apr 26 19:56:04 localhost slapd[43930]: slap_graduate_commit_csn: removing 0x7d3d38148f60 20210426195604.556053Z#000000#002#000000 ---- 8< ---- Example entries in the order slapcat sees them: ---- 8< ---- dn: reqStart=20210426195604.000364Z,cn=accesslog objectClass: auditBind reqStart: 20210426195604.000364Z reqEnd: 20210426195604.000365Z reqType: bind entryCSN: 20210426195604.558683Z#000000#002#000000 dn: reqStart=20210426195604.000351Z,cn=accesslog objectClass: auditAdd reqStart: 20210426195604.000351Z reqEnd: 20210426195604.000366Z reqType: add entryCSN: 20210426195604.556053Z#000000#002#000000 ---- 8< ---- -- You are receiving this mail because: You are on the CC list for the issue.

1 20

[Issue 9576] New: Add ConfigTable link into ConfigArgs
by openldap-its＠openldap.org 12 Jan '22

12 Jan '22

https://bugs.openldap.org/show_bug.cgi?id=9576 Issue ID: 9576 Summary: Add ConfigTable link into ConfigArgs Product: OpenLDAP Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: --- Component: slapd Assignee: bugs(a)openldap.org Reporter: ondra(a)mistotebe.net Target Milestone: --- Would make it possible to examine defaults if necessary. -- You are receiving this mail because: You are on the CC list for the issue.

1 7

[Issue 9773] New: slapo-allowed should also list "operational" attributes
by openldap-its＠openldap.org 03 Jan '22

03 Jan '22

https://bugs.openldap.org/show_bug.cgi?id=9773 Issue ID: 9773 Summary: slapo-allowed should also list "operational" attributes Product: OpenLDAP Version: 2.6.0 Hardware: All OS: All Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: contrib Assignee: bugs(a)openldap.org Reporter: michael(a)stroeder.com Target Milestone: --- When using slapo-allowed a client may disable input fields for attributes not listed in 'allowedAttributesEffective'. This helps the user to understand that he/she should not even try to modify the attribute (better UX). But slapo-allowed never shows operational attributes in allowedAttributesEffective. In most use-cases this is understandable but there are some nice use-cases (e.g. setting pwdPolicySubentry) where it should be possible for the client to display an enabled input field even for operational attributes. See also: * Discussion in ITS#9671 * https://code.stroeder.com/ldap/web2ldap/issues/24 -- You are receiving this mail because: You are on the CC list for the issue.

1 1

[Issue 8988] Undefined Behavior in slapadd
by openldap-its＠openldap.org 16 Dec '21

16 Dec '21

https://bugs.openldap.org/show_bug.cgi?id=8988 --- Comment #22 from noloader(a)gmail.com <noloader(a)gmail.com> --- On Fri, Jun 7, 2019 at 9:59 AM Howard Chu <hyc(a)symas.com> wrote: > > noloader(a)gmail.com wrote: > > On Fri, Jun 7, 2019 at 9:32 AM Howard Chu <hyc(a)symas.com> wrote: > >> > >> noloader(a)gmail.com wrote: > >> ... > >>> I encourage OpenLDAP to fix the undefined behavior. OpenLDAP is an > >>> important project, and the undefined behavior is causing too many > >>> tangential problems. > >> > >> Undefined behavior is not a bug, nor is it prohibited by the C spec. It is a necessary > >> part of the language for its intended use as a system programming language, writing > >> machine-specific programs. Anyone who says it is prohibited by the spec is wrong. The kernel recently got bitten using the same pattern of unaligned short pointers through casts. GCC produced code which corrupted initramfs during unpacking. See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100363. OpenLDAP should fix that code. -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 9771] New: ./.libs/libldap.so: undefined reference to `ber_sockbuf_io_udp'
by openldap-its＠openldap.org 15 Dec '21

15 Dec '21

https://bugs.openldap.org/show_bug.cgi?id=9771 Issue ID: 9771 Summary: ./.libs/libldap.so: undefined reference to `ber_sockbuf_io_udp' Product: OpenLDAP Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: build Assignee: bugs(a)openldap.org Reporter: shoober420(a)gmail.com Target Milestone: --- Created attachment 861 --> https://bugs.openldap.org/attachment.cgi?id=861&action=edit openldap build log When trying to build openldap from current master commit (https://github.com/openldap/openldap/commit/75636a407e38f1502c592566b5bf4c3…), I get the following error. Full build log attached. libtool: link: x86_64-pc-linux-gnu-gcc -m32 -march=native -O3 -pipe -fno-plt -fno-common -fipa-pta -falign-functions=32 -fdevirtualize-at-ltrans -fuse-linker-plugin -floop-nest-optimize -fgraphite-identity -fexcess-precision=fast -w -flto=auto -Wl,-O1 -o .libs/ftest ftest.o -Wl,--as-needed ./.libs/libldap.so /var/tmp/portage/net-nds/openldap-9999/work/openldap-9999-abi_x86_32.x86/libraries/liblber/.libs/liblber.so ../../libraries/liblber/.libs/liblber.so ../../libraries/liblutil/liblutil.a -lgnutls -luuid /usr/lib/gcc/x86_64-pc-linux-gnu/12.0.0/../../../../x86_64-pc-linux-gnu/bin/ld: ./.libs/libldap.so: undefined reference to `ber_sockbuf_io_udp' collect2: error: ld returned 1 exit status make[2]: *** [Makefile:338: urltest] Error 1 make[2]: *** Waiting for unfinished jobs.... /usr/lib/gcc/x86_64-pc-linux-gnu/12.0.0/../../../../x86_64-pc-linux-gnu/bin/ld: ./.libs/libldap.so: undefined reference to `ber_sockbuf_io_udp' /usr/lib/gcc/x86_64-pc-linux-gnu/12.0.0/../../../../x86_64-pc-linux-gnu/bin/ld: ./.libs/libldap.so: undefined reference to `ber_sockbuf_io_udp' collect2: error: ld returned 1 exit status collect2: error: ld returned 1 exit status make[2]: *** [Makefile:326: apitest] Error 1 make[2]: *** [Makefile:334: testavl] Error 1 /usr/lib/gcc/x86_64-pc-linux-gnu/12.0.0/../../../../x86_64-pc-linux-gnu/bin/ld: ./.libs/libldap.so: undefined reference to `ber_sockbuf_io_udp' collect2: error: ld returned 1 exit status make[2]: *** [Makefile:330: ftest] Error 1 /usr/lib/gcc/x86_64-pc-linux-gnu/12.0.0/../../../../x86_64-pc-linux-gnu/bin/ld: ./.libs/libldap.so: undefined reference to `ber_sockbuf_io_udp' collect2: error: ld returned 1 exit status make[2]: *** [Makefile:328: dntest] Error 1 /usr/lib/gcc/x86_64-pc-linux-gnu/12.0.0/../../../../x86_64-pc-linux-gnu/bin/ld: ./.libs/libldap.so: undefined reference to `ber_sockbuf_io_udp' collect2: error: ld returned 1 exit status make[2]: *** [Makefile:332: ltest] Error 1 make[2]: Leaving directory '/var/tmp/portage/net-nds/openldap-9999/work/openldap-9999-abi_x86_32.x86/libraries/libldap' make[1]: *** [Makefile:312: all-common] Error 1 make[1]: Leaving directory '/var/tmp/portage/net-nds/openldap-9999/work/openldap-9999-abi_x86_32.x86/libraries' make: *** [Makefile:320: all-common] Error 1 -- You are receiving this mail because: You are on the CC list for the issue.

1 2

[Issue 9282] New: Syncrepl re-creates deleted entry
by openldap-its＠openldap.org 13 Dec '21

13 Dec '21

https://bugs.openldap.org/show_bug.cgi?id=9282 Issue ID: 9282 Summary: Syncrepl re-creates deleted entry Product: OpenLDAP Version: 2.4.50 Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: --- Component: slapd Assignee: bugs(a)openldap.org Reporter: quanah(a)openldap.org Target Milestone: --- Scenario: 2 node Multi-provider replication Add database to provider A ensure database replicates to provider B Stop provider A delete entry on provider B Start provider A Wait for provider B to reconnect to provider A Deleted entry re-appears -- You are receiving this mail because: You are on the CC list for the issue.

1 22

[Issue 9765] New: slapd crash
by openldap-its＠openldap.org 08 Dec '21

08 Dec '21

https://bugs.openldap.org/show_bug.cgi?id=9765 Issue ID: 9765 Summary: slapd crash Product: OpenLDAP Version: 2.4.46 Hardware: All OS: Linux Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: overlays Assignee: bugs(a)openldap.org Reporter: shivaprasadtp(a)yahoo.in Target Milestone: --- Start-up two slapd server instances. Configure syncreply overlay with one of the servers as a provider and the other one as consumer. Create around 100 users. Now start changing syncrepl configuration for one of the slapd servers, lets say the consumer server, in a loop with 5 seconds delay. After few mins the slapd server crashes. -- You are receiving this mail because: You are on the CC list for the issue.

1 4

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs December 2021