openldap-bugs May 2020

openldap-bugs@openldap.org

1 participants
134 discussions

[Bug 9255] New: make fails in 2.4.50 due to missing Debug1/Debug3 symbols
by openldap-its＠openldap.org 04 May '20

04 May '20

https://bugs.openldap.org/show_bug.cgi?id=9255 Bug ID: 9255 Summary: make fails in 2.4.50 due to missing Debug1/Debug3 symbols Product: OpenLDAP Version: 2.4.50 Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: --- Component: libraries Assignee: bugs(a)openldap.org Reporter: marcosbd(a)vmware.com Target Milestone: --- We're finding an issue building OpenLDAP due to missing Debug1/Debug3 symbols: Entering subdirectory libldap make[2]: Entering directory '/bitnami/blacksmith-sandox/openldap-2.4.50/libraries/libldap' /bin/sh ../../libtool --mode=link gcc -Wl,-z,relro,-z,now,--as-needed -DLDAP_CONNECTIONLESS -DLDAP_USE_NON_BLOCKING_TLS -Wl,-rpath=/opt/bitnami/openldap/lib -L/opt/bitnami/openldap/lib -o apitest apitest.o libldap.la ../../libraries/liblber/liblber.la ../../libraries/liblutil/liblutil.a -lsasl2 -lssl -lcrypto -lcrypt -lresolv gcc -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -DLDAP_CONNECTIONLESS -DLDAP_USE_NON_BLOCKING_TLS -Wl,-rpath=/opt/bitnami/openldap/lib -o .libs/apitest apitest.o -L/opt/bitnami/openldap/lib ./.libs/libldap.so /bitnami/blacksmith-sandox/openldap-2.4.50/libraries/liblber/.libs/liblber.so ../../libraries/liblber/.libs/liblber.so ../../libraries/liblutil/liblutil.a -lsasl2 -lssl -lcrypto -lcrypt -lresolv -Wl,--rpath -Wl,/opt/bitnami/openldap/lib /usr/bin/ld: ./.libs/libldap.so: undefined reference to `Debug1' /usr/bin/ld: ./.libs/libldap.so: undefined reference to `Debug3' collect2: error: ld returned 1 exit status make[2]: *** [Makefile:309: apitest] Error 1 make[2]: Leaving directory '/bitnami/blacksmith-sandox/openldap-2.4.50/libraries/libldap' make[1]: *** [Makefile:296: all-common] Error 1 make[1]: Leaving directory '/bitnami/blacksmith-sandox/openldap-2.4.50/libraries' make: *** [Makefile:312: all-common] Error 1 We see that in master there are a lot of references to those symbols, but in the OPENLDAP_REL_ENG_2_4_50 tag of the repo it only appears in two places. It looks like this issue was caused by commit 7cf7aa3141 in ITS#8650. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 9254] New: Datatypes boudary check on slapadd
by openldap-its＠openldap.org 03 May '20

03 May '20

https://bugs.openldap.org/show_bug.cgi?id=9254 Bug ID: 9254 Summary: Datatypes boudary check on slapadd Product: OpenLDAP Version: 2.4.42 Hardware: All OS: Linux Status: UNCONFIRMED Severity: normal Priority: --- Component: slapd Assignee: bugs(a)openldap.org Reporter: c.dosio(a)gmail.com Target Milestone: --- The import of an LDIF file containing a passwordPolicy objectClass where the attribute pwdMaxAge was populated as 50000000000000 (while the max value of that attribute should be 315360000) went fine but any editing of values on that objectClass would make slapd hang until brutally killed (it goes into error 8 where apparently the operation is waiting to be executed, but even after several hours it would still be frozen). The only way I managed to solve the situation was to take e previous dump, change the value to something within the value's range, and restore it. BTW I couldn't manage to run slapcat (neither with the -c flag) to have a full dump. There are three issues in my opinion: 1. Shouldn't slapadd make some checks on data type values and eventually either give an error or change an exceeding value to the minimum/maximum value of the range? 2. Shouldn't slapd manage the exceeding value instead of freezing (in a way coherent to point 1)? 3. Shouldn't slapcat be forced to skip over the problem of an out of range value at least if run with the "-c" flag? -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 9253] New: Access not retained when last examined olcAccess has a "break" control
by openldap-its＠openldap.org 02 May '20

02 May '20

https://bugs.openldap.org/show_bug.cgi?id=9253 Bug ID: 9253 Summary: Access not retained when last examined olcAccess has a "break" control Product: OpenLDAP Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: --- Component: slapd Assignee: bugs(a)openldap.org Reporter: kop(a)karlpinc.com Target Milestone: --- When the last examined olcAccess control is "break" then it does not matter what access rights have been granted by the rules, access is denied. Reproduce by having a database with a single access rule: to attrs=userPassword by anonymous =x Note that ldapwhoami successfully does a simple bind. Then, modify so that the single existing access rule is: to attrs=userPassword by anonymous =x break Users can no longer do a simple bind. You will see similar behavior with SASL binds, or any number of access rules. Access is denied when the the last examined access control is "break". The problem is at line 309 of: servers/slapd/acl.c (In master/HEAD, and probably all versions) -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 9252] New: OpenLDAP ldif file import issue
by openldap-its＠openldap.org 02 May '20

02 May '20

https://bugs.openldap.org/show_bug.cgi?id=9252 Bug ID: 9252 Summary: OpenLDAP ldif file import issue Product: OpenLDAP Version: 2.4.44 Hardware: x86_64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: --- Component: build Assignee: bugs(a)openldap.org Reporter: pranjit_biswas(a)infosys.com Target Milestone: --- We are trying to install openldap.x86_64 - 2.4.44-21.el7_6 on an Linux RHEL 7.7 on AWS . We have installed and made changes to the config files and did a slaptest of the config file as shown below . [root@efg-ac cn=config]# slaptest -u 5ea6064f ldif_read_file: checksum error on "/etc/openldap/slapd.d/cn=config/olcDatabase={0}config.ldif" 5ea6064f ldif_read_file: checksum error on "/etc/openldap/slapd.d/cn=config/olcDatabase={2}hdb.ldif" config file testing succeeded Now we are importing the ldif file from our current on-prem server . Even though we were getting different errors earlier , after all the changes we have made to the config , the error that we are getting now is ldap_bind error for the credentials . [root@efg-dev cn=config]# ldapadd -w xxxxxxxx -x -D "cn=Manager,dc=bpost,dc=be" -f ldap_dump-27042020-DEV.ldif ldap_bind: Invalid credentials (49) We are not sure which password to give here . We have given the same credentials in the config file : olcDatabase={2}hdb.ldif olcRootDN: cn=Manager,dc=bpost,dc=be olcRootPW: xxxxxxxx Please assist -- You are receiving this mail because: You are on the CC list for the bug.

1 2

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 May 2020