https://bugs.openldap.org/show_bug.cgi?id=9964
Issue ID: 9964
Summary: He and she Fitness
Product: JLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: JDBC
Assignee: bugs(a)openldap.org
Reporter: heandshefitness1(a)gmail.com
Target Milestone: ---
He and she fitness is here for you with all the secrets that can be helpful for
you in the proper maintenance of the fitness of your body. To read more:
https://www.heandshefitness.com/2021/06/01/how-many-calories-does-skipping-…
--
You are receiving this mail because:
You are on the CC list for the issue.
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.