https://bugs.openldap.org/show_bug.cgi?id=6749
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |TEST
--- Comment #4 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• bc021bb2
by Quanah Gibson-Mount at 2020-09-18T14:56:43+00:00
ITS#6749 - Change configure monitor warning to DEBUG CONFIG instead of DEBUG
ANY
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9317
Issue ID: 9317
Summary: LDAPS connection fails to multi-IP DNS using
DIGEST-MD5 mechanism
Product: OpenLDAP
Version: 2.4.46
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: libraries
Assignee: bugs(a)openldap.org
Reporter: paul.raines(a)gmail.com
Target Milestone: ---
Our MS AD ldap servers are in DNS using alias ldap.example.org at multiple IP
addresses like so:
# host ldap.example.orgldap.example.org has address 172.18.1.10
ldap.example.org has address 172.21.1.10
ldap.example.org has address 172.24.1.10
ldap.example.org has address 172.30.1.10
For CentOS 6 this was not a problem. But with CentOS 7 (2.4.44) and CentOS 8
(2.4.46) the following fails
# ldapwhoami -d -1 -H ldaps://ldap.example.org -Y DIGEST-MD5 -U username -W
with the error:
ldap_sasl_interactive_bind_s: Invalid credentials (49)
additional info: 80090303: LdapErr: DSID-0C090574, comment: The
digest-uri does not match any LDAP SPN's registered for this server., data 0,
v3839
ldap_free_connection 1 1
ldap_send_unbind
If one reverse DNS IP lookups one of the IPs and uses the unique name (e.g.
ldap01.example.org) instead it works fine
I think openldap should work in this case with DNS aliases.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9315
Issue ID: 9315
Summary: FR: Support SPIFFE Certificate Provisioner
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: libraries
Assignee: bugs(a)openldap.org
Reporter: dar(a)xoe.solutions
Target Milestone: ---
Created attachment 754
--> https://bugs.openldap.org/attachment.cgi?id=754&action=edit
A SPIFFE samle certificate
SPIFFE is a protocol for attesting workload identities.
It implements a pull based workflow where clients request ad-hoc certificates
about their identity from a unix domain socket.
While there is a helper that can wrap clients it is uncertain
how certificate rolls, which happen by default every few minutes,
shall be signalled to the ldap client: https://github.com/spiffe/spiffe-helper
I assume there is no signal which induces graceful reloading of the
certificates.
Therefore, it might be considerable adding direct spiffe support
to the ldap client. See example:
https://github.com/spiffe/c-spiffe/blob/master/c-spiffe.cc
Please find attached a spiffe sample cert, for mere information. Note it does
convey identity (exclusively) through SAN, which currently seems not be
supported in OpenLDAP. I'm going to open another issue for that.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9286
Issue ID: 9286
Summary: mdb_cursor_get MDB_GET_MULTIPLE key not populated
Product: LMDB
Version: 0.9.25
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: liblmdb
Assignee: bugs(a)openldap.org
Reporter: corey(a)kaylors.net
Target Milestone: ---
Reading the docs it says "Return key and up to a page of duplicate data items
from current cursor position." when MDB_GET_MULTIPLE is used. I don't see the
key being populated, but when I call MDB_GET_CURRENT after the use of
MDB_GET_MULTIPLE the key is the value I expect. Looking through the code I
don't see the key getting used in this path. Granted, I'm not proficient with C
so I may have overlooked something.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9268
Issue ID: 9268
Summary: Test065 fails due to invalid log level
Product: OpenLDAP
Version: 2.4.50
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: build
Assignee: bugs(a)openldap.org
Reporter: andy(a)asjohnson.com
Target Milestone: ---
Line #109 of tests/scripts/test065-proxyauthz:
$SLAPD -f $CONF2 -h $URI2 -d $LVL -d pcache > $LOG2 2>&1 &
Results in this:
must compile with LDAP_DEBUG for debugging
unrecognized log level "pcache" (deferred)
After which the test fails.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9250
Bug ID: 9250
Summary: librewrite only supports up to 9 submatches
Product: OpenLDAP
Version: 2.4.49
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: libraries
Assignee: bugs(a)openldap.org
Reporter: ryan(a)openldap.org
Target Milestone: ---
libraries/librewrite$ cat nine.conf
rewriteEngine on
rewriteContext default
rewriteRule "(.)(.)(.)(.)(.)(.)(.)(.)(.)" "$9$8$7$6$5$4$3$2$1" :
libraries/librewrite$ ./rewrite -f nine.conf abcdefghijklmnop
abcdefghijklmnop -> ihgfedcba [0:ok]
libraries/librewrite$ cat eleven.conf
rewriteEngine on
rewriteContext default
rewriteRule "(.)(.)(.)(.)(.)(.)(.)(.)(.)(.)(.)" "$11$10$9$8$7$6$5$4$3$2$1" :
libraries/librewrite$ ./rewrite -f eleven.conf abcdefghijklmnop
abcdefghijklmnop -> a1a0ihgfedcba [0:ok]
I guess no one has needed that many yet... :)
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=9185
Bug ID: 9185
Summary: glue entry
Product: OpenLDAP
Version: 2.4.48
Hardware: All
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: client tools
Assignee: bugs(a)openldap.org
Reporter: gnoe(a)symas.com
Target Milestone: ---
--
You are receiving this mail because:
You are watching someone on the CC list of the bug.
https://bugs.openldap.org/show_bug.cgi?id=8805
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
--
You are receiving this mail because:
You are on the CC list for the issue.