https://bugs.openldap.org/show_bug.cgi?id=9678
Issue ID: 9678
Summary: slapadd prints “olcRootPW: value #0: <olcRootPW> can
only be set when rootdn is under suffix” and then
crashes
Product: OpenLDAP
Version: 2.5.7
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: dpa-openldap(a)aegee.org
Target Milestone: ---
Created attachment 840
--> https://bugs.openldap.org/attachment.cgi?id=840&action=edit
Valgrind output
Calling
```
slapadd -n0 -F/home/d/ldap/conf <<ABC
dn: cn=config
objectClass: olcGlobal
cn: config
olcAuthzRegexp: uid=([^@,]+)@example.org,cn=[^,]*,cn=auth
uid=$1,cn=users,dc=example,dc=org
dn: olcDatabase=frontend,cn=config
objectClass: olcDatabaseConfig
objectClass: olcFrontendConfig
olcDatabase: frontend
dn: olcDatabase=config,cn=config
objectClass: olcDatabaseConfig
olcDatabase: config
olcRootDN: uid=yyy,cn=users,dc=example,dc=org
olcRootPW: zzz
ABC
```
prints
PROXIED attributeDescription "DC" inserted.
olcRootPW: value #0: <olcRootPW> can only be set when rootdn is under suffix
slapadd: could not add entry dn="olcDatabase={0}config,cn=config" (line=12):
Segmentation fault (core dumped)
The output of valgrind, when it runs the above command, is attached.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9671
Issue ID: 9671
Summary: pwdPolicySubentry: no user modification allowed
Product: OpenLDAP
Version: 2.5.7
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: michael(a)stroeder.com
Target Milestone: ---
Without using Relax Rules control it is not possible to set attribute
pwdPolicySubentry anymore. This was possible with 2.4.x.
# ldapadd -Q -f aehost.ldif
adding new entry "host=foobar42.example.com,cn=test-hosts-1,cn=test,ou=ae-dir"
ldap_add: Constraint violation (19)
additional info: pwdPolicySubentry: no user modification allowed
This is a really serious regression for existing admin processes.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9664
Issue ID: 9664
Summary: Hiding namingContexts in the root DSE, when these are
not in small letters
Product: OpenLDAP
Version: 2.5.6
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: dpa-openldap(a)aegee.org
Target Milestone: ---
Below are the ACL for the frontend database. They are supposed to hide the
cn=krbconfig from the namingContexts on the root DSE.
dn: olcDatabase=frontend,cn=config
objectClass: olcDatabaseConfig
objectClass: olcFrontendConfig
olcDatabase: frontend
#olcAccess: to dn.base="" attrs=namingContexts
val/distinguishedNameMatch="cn=krbcontainer" by * none
olcAccess: to dn.base="" attrs=namingContexts val="cn=krbcontainer" by * none
olcAccess: to dn.exact="" by * read
dn: olcDatabase=mdb,cn=config
objectClass: olcDatabaseConfig
objectClass: olcMdbConfig
olcDatabase: mdb
olcDbMaxSize: 10485760
olcSuffix: cn=krbcontainer
olcRootDN: uid=zzz,cn=krbcontainer
olcRootPW: zzz
olcDbDirectory: ldap/uuu
olcDbIndex: objectClass eq
olcAccess: to dn.sub="cn=krbContainer"
by * read
It does work!
However, if change the case in (container ⇒ Container):
olcSuffix: cn=krbContainer
no matter how I set olcAccess in the frontend database,
$ ldapsearch -xb "" -s base namingContexts
always prints
dn:
namingContexts: cn=krbContainer
In particular
olcAccess: to dn.base="" attrs=namingContexts
val/distinguishedNameMatch="cn=krbcontainer" by * none
does not hide it.
• It shall be possible to find olcSuffix from the DSE/namingContexts, even if
the suffix is mixCased.
Since the case is known at the time, when the rules are written, OpenLDAP shall
offer an option for exact match, without converting data to lowercase. (as
shown by sladp -d -1 )
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9659
Issue ID: 9659
Summary: slapd fails to compile with LDAP_PF_LOCAL_SENDMSG:
redefinition of 'peerbv'
Product: OpenLDAP
Version: 2.5.7
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: ryan(a)openldap.org
Target Milestone: ---
Thanks for fixing issue 9658. The same test environment (Debian GNU/Hurd 11.0)
now fails to compile slapd (RE25 and master):
cc -g -O2 -I../../include -I. -I./slapi -I. -I../../include -c -o
daemon.o daemon.c
daemon.c: In function 'slap_listener':
daemon.c:2113:16: error: redefinition of 'peerbv'
2113 | struct berval peerbv = BER_BVNULL;
| ^~~~~~
daemon.c:2110:16: note: previous definition of 'peerbv' was here
2110 | struct berval peerbv = BER_BVC(peername);
| ^~~~~~
<builtin>: recipe for target 'daemon.o' failed
make[2]: *** [daemon.o] Error 1
The relevant code in daemon.c:
char peername[LDAP_IPADDRLEN];
struct berval peerbv = BER_BVC(peername);
#ifdef LDAP_PF_LOCAL_SENDMSG
char peerbuf[8];
struct berval peerbv = BER_BVNULL;
#endif
When LDAP_PF_LOCAL_SENDMSG is defined, the variable 'peerbv' is declared twice.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9696
Issue ID: 9696
Summary: OpenSSL implementation of LDAP_OPT_X_TLS_PEERCERT
leaks memory
Product: OpenLDAP
Version: 2.4.57
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: libraries
Assignee: bugs(a)openldap.org
Reporter: cheimes(a)redhat.com
Target Milestone: ---
The OpenSSL implementation of ldap_get_option() LDAP_OPT_X_TLS_PEERCERT leaks
memory. The internal function tlso_session_peercert() uses
SSL_get_peer_certificate() to access the server certificate.
SSL_get_peer_certificate() increases the reference counter of the peer cert by
one. The code is missing a X509_free() call to decref the internal reference
counter by one.
I also recommend that you check the return value of SSL_get_peer_certificate()
for NULL. There are cases when a TLS session does not have access to a peer
certificate, e.g. session resumption.
Valgrind log:
==586962== 16,044 (1,056 direct, 14,988 indirect) bytes in 3 blocks are
definitely lost in loss record 6,355 of 6,374
==586962== at 0x484086F: malloc (vg_replace_malloc.c:380)
==586962== by 0x16981A4D: CRYPTO_zalloc (mem.c:230)
==586962== by 0x168CC823: asn1_item_embed_new (tasn_new.c:122)
==586962== by 0x168CE12A: asn1_item_embed_d2i (tasn_dec.c:325)
==586962== by 0x168CE341: ASN1_item_ex_d2i (tasn_dec.c:124)
==586962== by 0x168CE3CE: ASN1_item_d2i (tasn_dec.c:114)
==586962== by 0x1744B7CC: tls_process_server_certificate
(statem_clnt.c:1853)
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9668
Issue ID: 9668
Summary: undefined behavior for isdigit in tls2.c
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: libraries
Assignee: bugs(a)openldap.org
Reporter: roland.illig(a)gmx.de
Target Milestone: ---
tls2.c says:
> isdigit( *c )
This invokes undefined behavior if someone manages to pass a non-ASCII
character. Depending on the platform, the process may crash or wrongly classify
the host name as either numeric or non-numeric.
While here, I noticed that both sni and c have type 'char *', but they should
rather be 'const char *'. Was there a specific reason to suggest to the reader
the host name would be modifiable?
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9706
Issue ID: 9706
Summary: monitoringslapd.sdf: typo Backends
Product: OpenLDAP
Version: 2.5.7
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: documentation
Assignee: bugs(a)openldap.org
Reporter: dpa-openldap(a)aegee.org
Target Milestone: ---
doc/guide/admin/monitoringslapd.sdf contains:
H3: Backends
The {{EX:cn=Backends,cn=Monitor}} object, itself, provides a list
of available backends. The list of available backends all builtin
backends, as well as backends loaded by modules. For example: …
The second sentence has no verb.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9699
Issue ID: 9699
Summary: doc/admin25/loadbalancer.html: typo “between a a set
of running slapd instances”
Product: OpenLDAP
Version: 2.5.7
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: documentation
Assignee: bugs(a)openldap.org
Reporter: dpa-openldap(a)aegee.org
Target Milestone: ---
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9693
Issue ID: 9693
Summary: Section 9.6 html formatting issue
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: documentation
Assignee: bugs(a)openldap.org
Reporter: mnormann(a)symas.com
Target Milestone: ---
Section 9.6 of documentation is missing a closing anchor tag and closing title
tag (Glued/Subordinate database configurations)
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9689
Issue ID: 9689
Summary: Redundancy in the description of syncprov-nopresent
Product: OpenLDAP
Version: 2.5.7
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: documentation
Assignee: bugs(a)openldap.org
Reporter: dpa-openldap(a)aegee.org
Target Milestone: ---
https://www.openldap.org/devel/admin/replication.html#Set%20up%20the%20prov…
says:
“““
The nonpresent option **should only be configured if the overlay is being
placed on top of a log database**, such as when used with delta-syncrepl.
The nonpresent option is configured by the
syncprov-nopresent <TRUE|FALSE>
directive. This value **should only be set TRUE for a syncprov instance on top
of a log database** (such as one managed by the accesslog overlay). The default
is FALSE.
”””
I think, the circumstances when the option shall be used, are repeated twice.
One of the repetitions can be shortened.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9688
Issue ID: 9688
Summary: Is EQ index on entryCSN mandatory for replication?
Product: OpenLDAP
Version: 2.5.7
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: documentation
Assignee: bugs(a)openldap.org
Reporter: dpa-openldap(a)aegee.org
Target Milestone: ---
https://www.openldap.org/devel/admin/replication.html says about the EQ index
on entryCSN: “On databases which support inequality indexing, setting an eq
index on the entryCSN attribute and configuring contextCSN checkpoints will
greatly speed up this scanning step.” → The index is recommended, but not
mandatory, and not always possible.
man 5 slapo-syncprov /
https://www.openldap.org/software/man.cgi?query=slapo-syncprov&apropos=0&se…
says “On databases that support inequality indexing, it is mandatory to set an
eq index on the entryCSN attribute when using this overlay.”
Between both documents there is a discrepancy, whether the EQ index is
mandatory or not.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9687
Issue ID: 9687
Summary: olcTLSECName is not required in order to use
ECDHE-based cipher suites in OpenSSL
Product: OpenLDAP
Version: 2.5.7
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: documentation
Assignee: bugs(a)openldap.org
Reporter: dpa-openldap(a)aegee.org
Target Milestone: ---
SLAPD-CONFIG(5) says that olcTLSECName is used to set the names of the Elliptic
Curves. It does not say, that the option is required, nor does it say what
happens, when the option is not set.
https://www.openldap.org/doc/admin25/tls.html#TLS%20Configuration says for
TLSECName: This is required in order to use ECDHE-based cipher suites in
OpenSSL.
I do not set TLSECName and call
./testssl.sh ldap.aegee.org:636
which prints:
Hexcode Cipher Suite Name (OpenSSL) KeyExch. Encryption Bits
Cipher Suite Name (IANA/RFC)
-----------------------------------------------------------------------------------------------------------------------------
TLSv1 (server order)
xc014 ECDHE-RSA-AES256-SHA ECDH 256 AES 256
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
xc013 ECDHE-RSA-AES128-SHA ECDH 256 AES 128
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
TLSv1.1 (server order)
xc014 ECDHE-RSA-AES256-SHA ECDH 256 AES 256
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
xc013 ECDHE-RSA-AES128-SHA ECDH 256 AES 128
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
TLSv1.2 (server order)
xc030 ECDHE-RSA-AES256-GCM-SHA384 ECDH 253 AESGCM 256
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
xcca8 ECDHE-RSA-CHACHA20-POLY1305 ECDH 253 ChaCha20 256
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
xc02f ECDHE-RSA-AES128-GCM-SHA256 ECDH 253 AESGCM 128
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
xc028 ECDHE-RSA-AES256-SHA384 ECDH 253 AES 256
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
xc027 ECDHE-RSA-AES128-SHA256 ECDH 253 AES 128
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
xc014 ECDHE-RSA-AES256-SHA ECDH 253 AES 256
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
xc013 ECDHE-RSA-AES128-SHA ECDH 253 AES 128
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
TLSv1.3 (server order)
x1302 TLS_AES_256_GCM_SHA384 ECDH 253 AESGCM 256
TLS_AES_256_GCM_SHA384
x1303 TLS_CHACHA20_POLY1305_SHA256 ECDH 253 ChaCha20 256
TLS_CHACHA20_POLY1305_SHA256
x1301 TLS_AES_128_GCM_SHA256 ECDH 253 AESGCM 128
TLS_AES_128_GCM_SHA256
Testing robust forward secrecy (FS) -- omitting Null
Authentication/Encryption, 3DES, RC4
Elliptic curves offered: prime256v1 secp384r1 secp521r1 X25519 X448
This means, that when olcTLSECName is not set, OpenSSL defaults are used, and
ECDHE-based cipher suites are still offered.
testssl.sh can be obtianed from https://github.com/drwetter/testssl.sh .
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9674
Issue ID: 9674
Summary: Is olcMonitoring enabled by default for MDB?
Product: OpenLDAP
Version: 2.5.7
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: documentation
Assignee: bugs(a)openldap.org
Reporter: dpa-openldap(a)aegee.org
Target Milestone: ---
The manual page doc/man/man5/slapd-config.5 misses a .TP before .B
olcMonitoring. In turn at
https://www.openldap.org/software/man.cgi?query=slapd-config&apropos=0&sekt…
olcMonitoring appears in the description of olcMultiProvider .
The same man page says, that only MBD supports the olcMonitoring mechanims and
the default for olcMonitoring depends on the backend. The documentation for
mdb does not say, if olcMonitoring is by default enabled or disabled
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9669
Issue ID: 9669
Summary: Incorrect Heimdal download site in OpenLDAP
Administrator's Guide
Product: OpenLDAP
Version: 2.5.7
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: documentation
Assignee: bugs(a)openldap.org
Reporter: dewayne.geraghty(a)heuristicsystems.com.au
Target Milestone: ---
In section 4.2.3 page 18 of latest OpenLDAP 2.5 Admin Guide has Heimdal
available from http://www.pdc.kth.se/heimdal/ which is a dead link.
The more correct location is
https://github.com/heimdal/heimdal
(Thank-you for your great software!)
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9646
Issue ID: 9646
Summary: slapd-meta: deprecations in 2.4: “try-propagate is
highly deprecated”
Product: OpenLDAP
Version: 2.5.4
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: documentation
Assignee: bugs(a)openldap.org
Reporter: dpa-openldap(a)aegee.org
Target Milestone: ---
The upgrade instructions from 2.4 at
https://www.openldap.org/doc/admin25/appendix-upgrading.html says
> B.4. ldap and meta backends
>
> Several deprecated configuration directives for slapd-ldap(5) and slapd-meta(5) have been removed. Configurations using those directive must be updated to use supported directives prior to upgrade. See the slapd-ldap(5) and slapd-meta(5) man pages from OpenLDAP 2.4 for a list of deprecated directives.
The slapd-meta(5) for 2.4 says at
https://www.openldap.org/software/man.cgi?query=slapd-meta&apropos=0&sektio…
, when I search for “deprecated”:
> tls {[try-]start|[try-]propagate}
> The try- prefix instructs the proxy to continue operations if the StartTLS operation failed; its use is highly deprecated.
...
> DEPRECATED STATEMENTS
> The following statements have been deprecated and should no longer be used.
> pseudorootdn <substitute DN in case of rootdn bind>
> Use idassert-bind instead.
>
> pseudorootpw <substitute password in case of rootdn bind>
> Use idassert-bind instead.
I object the wording “highly deprecated”. It should be “highly discouraged”.
With the current wording it is not very clear, whether the try- variants
disappeared in 2.5
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9656
Issue ID: 9656
Summary: slapd (2.5.7) crashes when ppm settings don't exist in
the schema
Product: OpenLDAP
Version: unspecified
Hardware: x86_64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: ktmdms(a)gmail.com
Target Milestone: ---
using ppolicy with ppm causes slapd to crash (2.5.7. I would have selected
that as the version but it's not available to be selected) when
pwdCheckModuleArg doesn't exist in the schema and/or the full path to ppm.so
isn't defined in pwdCheckModule. at the time slapd would crash, pwdCheckModule
was set to ppm.so not the full path of /usr/local/libexec/openldap/ppm.so and
the pwdCheckModuleArg attribute didn't exist at all. whenever I would attempt
to change my user password, slapd would crash. setting the full path and
creating and setting the Arg attribute has stopped that behavior but I'm unsure
if it was simply added the attribute or some combination of setting the full
path, creating the attribute, and populating the attribute. fwiw, the
attribute is set as:
bWluUXVhbGl0eSA0Cm1heExlbmd0aCAwCmNoZWNrUkROIDEKZm9yYmlkZGVuQ2hhcnMgCmNsYXNz
LXVwcGVyQ2FzZSBBQkNERUZHSElKS0xNTk9QUVJTVFVWV1hZWiAxIDEKY2xhc3MtbG93ZXJDYXNl
IGFiY2RlZmdoaWprbG1ub3BxcnN0dXZ3eHl6IDEgMQpjbGFzcy1kaWdpdCAwMTIzNDU2Nzg5IDEg
MQpjbGFzcy1zcGVjaWFsIDw+LD87LjovIcKnw7klKsK1XsKoJMKjwrImw6l+IiMneyhbLXzDqGBf
XMOnXsOgQCldwrA9fSsgMSAxCgo=
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9644
Issue ID: 9644
Summary: provide a man page for ppm
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: contrib
Assignee: bugs(a)openldap.org
Reporter: david.coutadeur(a)gmail.com
Target Milestone: ---
Provide a man page for ppm
proposed PR is coming
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9648
Issue ID: 9648
Summary: 'MAXPATHLEN' undeclared on some systems
Product: OpenLDAP
Version: 2.5.4
Hardware: All
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: libraries
Assignee: bugs(a)openldap.org
Reporter: git(a)freundtech.com
Target Milestone: ---
Created attachment 834
--> https://bugs.openldap.org/attachment.cgi?id=834&action=edit
Docker reproduction
I'm trying to compile OpenLDAP 2.5.7 on Alpine Linux, but have verified that
the problem exists since 2.5.4. Version 2.4.59 compiles correctly with
everything else equal.
Compilation fails with
In file included from ldap-int.h:119,
from request.c:53:
request.c: In function 'ldap_dump_connection':
../../include/ldap_pvt.h:181:25: error: 'MAXPATHLEN' undeclared (first use in
this function)
181 | #define LDAP_IPADDRLEN (MAXPATHLEN + sizeof("PATH="))
| ^~~~~~~~~~
request.c:859:17: note: in expansion of macro 'LDAP_IPADDRLEN'
859 | char from[LDAP_IPADDRLEN];
| ^~~~~~~~~~~~~~
../../include/ldap_pvt.h:181:25: note: each undeclared identifier is reported
only once for each function it appears in
181 | #define LDAP_IPADDRLEN (MAXPATHLEN + sizeof("PATH="))
| ^~~~~~~~~~
request.c:859:17: note: in expansion of macro 'LDAP_IPADDRLEN'
859 | char from[LDAP_IPADDRLEN];
| ^~~~~~~~~~~~~~
make[2]: Leaving directory '/tmp/openldap/libraries/libldap'
Thanks to JoBbZ on IRC I found out that including <ac/param.h> in ldap_pvt.h
seems to fix the issue.
My best guess as to why this fails on Alpine Linux and not on other
distributions is that Alpine uses musl instead of glibc as it's libc
implementation.
I have attacked an (unfinished) dockerfile for reproduction of the issue.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9712
Issue ID: 9712
Summary: back-mdb multival delete isn't deleting
Product: OpenLDAP
Version: 2.5.7
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 deleting an entry that has multival-related attributes, those attribute
values weren't getting deleted.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9631
Issue ID: 9631
Summary: slapd-wt tests often fail/timeout
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: backends
Assignee: bugs(a)openldap.org
Reporter: ondra(a)mistotebe.net
Target Milestone: ---
Since merging wt into master, tests started to fail ~80-90% of the time, partly
due to bugs in wt (https://git.openldap.org/openldap/openldap/-/jobs/8458) or
timeouts in CI.
I am about to remove the backend from make test for now (keeping it in
alltests), opening this issue to discuss further.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9463
Issue ID: 9463
Summary: back-wt: cumulative fix
Product: OpenLDAP
Version: 2.5
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: backends
Assignee: bugs(a)openldap.org
Reporter: hamano(a)osstech.co.jp
Target Milestone: ---
Hi,
This is cumulative fix for back-wt.
I'm sorry to making 2.5 patch has been delayed due to we're
still using 2.4.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=7335
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|2.6.0 |2.6.1
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=6097
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|2.6.0 |2.6.1
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=6949
--- Comment #22 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
RE26:
• ce073522
by Ondřej Kuzník at 2021-10-05T01:42:43+00:00
ITS#6949 Fix and emit error messages
• 15ac53a7
by Ondřej Kuzník at 2021-10-05T01:42:48+00:00
ITS#6949 Remove dead code from lloadd
• 466e0321
by Ondřej Kuzník at 2021-10-05T01:42:52+00:00
ITS#6949 Port rest of the features to lloadd
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=6949
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|IN_PROGRESS |RESOLVED
Resolution|--- |TEST
--- Comment #21 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
• a3dea08c
by Ondřej Kuzník at 2021-10-04T14:46:22+01:00
ITS#6949 Fix and emit error messages
• 8894f00f
by Ondřej Kuzník at 2021-10-04T14:46:26+01:00
ITS#6949 Remove dead code from lloadd
• 3c07544b
by Ondřej Kuzník at 2021-10-04T14:46:26+01:00
ITS#6949 Port rest of the features to lloadd
--
You are receiving this mail because:
You are on the CC list for the issue.