https://bugs.openldap.org/show_bug.cgi?id=9963
Issue ID: 9963
Summary: Wheels Inpak
Product: JLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: JDBC
Assignee: bugs(a)openldap.org
Reporter: wheelsinpak1(a)gmail.com
Target Milestone: ---
Wheelsinpak.com is the right place for you if you are looking for some kind of
services, here you can search for the right providers of many needed services
along with car and bike info. To read more:
https://www.wheelsinpak.com/2021/12/08/kia-cars-price-in-pakistan-2021/
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9600
Issue ID: 9600
Summary: Rework lloadd's cn=monitor interface (connections)
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: lloadd
Assignee: bugs(a)openldap.org
Reporter: ondra(a)mistotebe.net
Target Milestone: ---
At the moment, most of the lloadd's monitor entries are generated on demand for
the search. To support management of the server and its connections, an entry
should be created when a connection is set up and torn down accordingly.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9958
Issue ID: 9958
Summary: Problem extracting openldap-2.5.5.tgz
Product: OpenLDAP
Version: 2.5.5
Hardware: x86_64
OS: Windows
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: build
Assignee: bugs(a)openldap.org
Reporter: harshad.ghorpade(a)gmail.com
Target Milestone: ---
Created attachment 931
--> https://bugs.openldap.org/attachment.cgi?id=931&action=edit
7zip extracting issue
Hello,
we have downloaded the the openldap version
2.5.5(https://www.openldap.org/software/download/OpenLDAP/openldap-release/…
from the given link but we are seeing a problem unzipping those tgz files via 7
zip on windows platform, seems like symlinks are broken(find attached
screenshot).
This is causing us a issue in one of our tool used for software composition
analysis when it unzips the archive, if the archives are fixed that would be
great.
if you see in screenshot, it points to 2 files in "servers\lload\design.md" and
"servers\lload\nt_svc.c". we tried removing these files(as they are of 0 size)
and tar it back again and creating a tgz file out of it, it works.
but we would like to use the official released version rather than one changed
by us.
Thank you.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9948
Issue ID: 9948
Summary: tls_ciphers with TLSv1.2 cipher_suite gives list of
TLSv1.3 ciphers in TLS Client Hello message
Product: OpenLDAP
Version: 2.4.57
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: client tools
Assignee: bugs(a)openldap.org
Reporter: nikigen68(a)gmail.com
Target Milestone: ---
Created attachment 928
--> https://bugs.openldap.org/attachment.cgi?id=928&action=edit
TLS server only supports TLSv1.3 in this case, and I would expect it to be
rejected.
For example:
ldap.conf::
tls_ciphers ECDHE-ECDSA-CHACHA20-POLY1305
will give ClientHello with these cipher suites:
TLS_AES_256_GCM_SHA384
TLS_AES_128_GCM_SHA256
TLS_CHACHA20_POLY1305_SHA256
ECDHE-ECDSA-CHACHA20-POLY1305
and supported versions:
TLSv1.0, TLSv1.1, TLSv1.2, TLSv1.3
Why do we have listed default TLSv1.3 ciphers? I would expect only
ECDHE-ECDSA-CHACHA20-POLY1305. Also, why do we have listed TLSv1.0 and TLSv1.1
as supported versions when those are considered vulnerable?
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9955
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|IN_PROGRESS |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Note:
Not exploitable, no operational or security impact.
head:
• 31e6efeb
by Howard Chu at 2022-12-01T14:58:37+00:00
ITS#9955 liblunicode: fix buffer size in UTF8bvnormalize
RE26:
• 261a4185
by Howard Chu at 2022-12-05T16:29:07+00:00
ITS#9955 liblunicode: fix buffer size in UTF8bvnormalize
RE25:
• cd1d0886
by Howard Chu at 2022-12-05T16:30:29+00:00
ITS#9955 liblunicode: fix buffer size in UTF8bvnormalize
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9955
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Group|OpenLDAP-devs |
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9916
Issue ID: 9916
Summary: slapd crashes due to unaligned access in mdb.c on
Linux SPARC
Product: OpenLDAP
Version: 2.6.3
Hardware: Other
OS: Linux
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: glaubitz(a)physik.fu-berlin.de
Target Milestone: ---
The testsuite of the openldap package in Debian unstable fails on sparc64 with
a "bus error" which indicates an unaligned access [1]:
>>>>> Test succeeded
>>>>> 00:00:02 Finished test000-rootdse for mdb after 1 seconds.
>>>>> 00:00:02 Starting test001-slapadd for mdb...
running defines.sh
Running slapadd to build slapd database...
Bus error
slapadd failed (138)!
>>>>> 00:00:03 Failed test001-slapadd for mdb after 1 seconds
(exit 138)
Building openldap from git and running the affected test with GDB results in
the following backtrace:
(gdb) bt
#0 0x00000100000cc36c in mdb_node_add (mc=0x100004316e8, indx=<optimized out>,
key=0x7feffffe570, data=0x7feffffe560, pgno=0, flags=0)
at ./../../../libraries/liblmdb/mdb.c:7358
#1 0x00000100000d0894 in mdb_cursor_put (mc=0x100004316e8, key=0x7feffffe570,
data=0x7feffffe560, flags=16) at ./../../../libraries/liblmdb/mdb.c:6960
#2 0x00000100000d1224 in mdb_cursor_put (mc=0x10000431560, key=0x7feffffe6b0,
data=0x7feffffe6c0, flags=36) at ./../../../libraries/liblmdb/mdb.c:7007
#3 0x00000100000f0d24 in mdb_dn2id_add (op=0x7feffffea28, mcp=0x10000431560,
mcd=0x100004267a0, pid=<optimized out>, nsubs=<optimized out>,
upsub=<optimized out>, e=0x1000044c6b8) at dn2id.c:141
#4 0x00000100000dd79c in mdb_tool_next_id (op=0x7feffffea28, tid=<optimized
out>, e=0x1000044c6b8, text=0x7feffffec78, hole=<optimized out>)
at tools.c:519
#5 0x00000100000de67c in mdb_tool_entry_put (be=0x100003d9080,
e=0x1000044c6b8, text=0x7feffffec78) at tools.c:731
#6 0x00000100000b72f4 in slapadd (argc=<optimized out>, argv=<optimized out>)
at slapadd.c:453
#7 0x0000010000016858 in main (argc=<optimized out>, argv=0x7fefffff438) at
main.c:540
(gdb)
This was reproduced with:
$ gdb --args /home/glaubitz/openldap/servers/slapd/slapd -Ta -d 0 -f
/home/glaubitz/openldap/tests/testrun/slapadd.conf -l
./testdata/test-ordered.ldif
On the machine gcc202 running Debian on sparc64 in the GCC compile farm. Access
to the machines in the GCC compile farm can be obtained by any developer [2].
> [1] https://buildd.debian.org/status/fetch.php?pkg=openldap&arch=sparc64&ver=2.…
> [2] https://gcc.gnu.org/wiki/CompileFarm
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9806
Issue ID: 9806
Summary: MDB_PAGE_FULL on mdb_put
Product: LMDB
Version: unspecified
Hardware: Other
OS: Mac OS
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: liblmdb
Assignee: bugs(a)openldap.org
Reporter: casey(a)rodarmor.com
Target Milestone: ---
I'm using the using latest lmdb from OpenLDAP, commit
e8813b12b6188d5ba5f174ff8726c438c8ca4bfd.
I'm getting an MDB_PAGE_FULL error after calling `mdb_put`. If I delete the
database and perform the same sequence of inserts, I get the same error in on
the same mdb_put.
If there's any information I can provide to help debug this, let me know.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9954
Issue ID: 9954
Summary: RE26 make test fails on riscv64
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: michael(a)stroeder.com
Target Milestone: ---
Created attachment 929
--> https://bugs.openldap.org/attachment.cgi?id=929&action=edit
Excerpt of OBS' build log
In openSUSE build system make test fails for RE26 on riscv64 (see attached file
including tests/testrun/slapd.1.log).
--
You are receiving this mail because:
You are on the CC list for the issue.