https://bugs.openldap.org/show_bug.cgi?id=9800
Issue ID: 9800
Summary: ACL with set.expand in <who> clause does not work with
deref control
Product: OpenLDAP
Version: 2.6.1
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: ---
This ACL returns correct values with a normal search requesting the attribute
sudoUser:
access to
dn.subtree="ou=ae-dir"
attrs=sudoUser
val.regex="^%(.+)$"
by set.expand="(user/-1 | user/aeSrvGroup)/aeLoginGroups &
[ldap:///ou=ae-dir?entryDN?sub?(&(objectClass=aeGroup)(aeStatus=0)(cn=${v1}))]/entryDN"
read
by * none
But it does not work with a search like this using deref control:
ldapsearch -Q -E deref=aeVisibleSudoers:cn,sudoUser '(objectClass=aeSrvGroup)'
For completeness see docs and schema for aeSrvGroup:
https://www.ae-dir.com/docs.html#schema-oc-aeSrvGrouphttps://code.stroeder.com/AE-DIR/ansible-ae-dir-server/src/branch/master/fi…
--
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.2 |2.7.0
Assignee|hyc(a)openldap.org |bugs(a)openldap.org
--
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.2 |2.7.0
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8255
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|IN_PROGRESS |RESOLVED
--- Comment #12 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
RE26:
• 59605f9f
by OndÅ™ej KuznÃk at 2022-02-28T17:36:11+00:00
ITS#8255 Clarify "sockresps result" behaviour
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8255
--- Comment #11 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
head:
73e882c8
by OndÅ™ej KuznÃk at 2022-02-24T15:32:36+00:00
ITS#8255 Clarify "sockresps result" behaviour
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8753
--- Comment #14 from OndÅ™ej KuznÃk <ondra(a)mistotebe.net> ---
On Mon, Feb 21, 2022 at 10:46:12AM +0000, openldap-its(a)openldap.org wrote:
> => The correct values for hashalgo should be described in the man-page.
Since this depends entirely on the crypto library at runtime, not sure
how we could do any better than saying "it depends", which is what I did
in that linked commit, now at
https://git.openldap.org/openldap/openldap/-/merge_requests/499
Can you suggest an alternate wording you think explains it better?
Thanks,
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8753
--- Comment #13 from Michael Ströder <michael(a)stroeder.com> ---
On 2/21/22 11:40, openldap-its(a)openldap.org wrote:
> See the (commented) lines in the test:
> https://code.stroeder.com/pymod/python-ldap0/src/branch/main/tests/test_lda…
Ok, I've looked into the tests for TLS_PEERKEY_HASHALG to make it work.
=> The correct values for hashalgo should be described in the man-page.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8753
--- Comment #12 from Michael Ströder <michael(a)stroeder.com> ---
(In reply to OndÅ™ej KuznÃk from comment #11)
> It should be analogous to HTTP Public Key Pinning, that's why it's
> working with keys, not certificates.
Ah, ok.
For python-ldap0 tests I've used for generation the SHA-256 hash:
openssl rsa -in tests/tls/localhost.key -outform der -pubout | openssl dgst
-sha256 -binary | openssl enc -base64
But it does not work (with libldap 2.6.1):
ldap0.CONNECT_ERROR: {'result': -11, 'desc': b'Connect error', 'ctrls': [],
'info': b'error:1416F086:SSL
routines:tls_process_server_certificate:certificate verify failed (self signed
certificate in certificate chain)'}
See the (commented) lines in the test:
https://code.stroeder.com/pymod/python-ldap0/src/branch/main/tests/test_lda…
Assuming I got this right:
https://code.stroeder.com/pymod/python-ldap0/commit/1ec4ad7ada7388835d5df8c…
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8753
--- Comment #10 from Michael Ströder <michael(a)stroeder.com> ---
Is the key hash calculated over the raw public key? In which representation?
Why not use the TLS server cert's finger-print?
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8753
--- Comment #9 from Michael Ströder <michael(a)stroeder.com> ---
(In reply to Michael Ströder from comment #8)
> What are valid values or is the format of the <hashalg> field?
It seems crypto(7) should be referenced by ldap_set_option(3) in case of
OpenSSL?
https://www.openssl.org/docs/manmaster/man7/crypto.html
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8753
--- Comment #8 from Michael Ströder <michael(a)stroeder.com> ---
What are valid values or is the format of the <hashalg> field?
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9502
Issue ID: 9502
Summary: Implement TCP_USER_TIMEOUT in meta and asyncmeta
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: nivanova(a)symas.com
Target Milestone: ---
Implement TCP_USER_TIMEOUT as an option to libldap and as a configuration
option in back-meta and back-asyncmeta
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9189
Bug ID: 9189
Summary: Add GSSAPI channel-bindings support
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: libraries
Assignee: bugs(a)openldap.org
Reporter: iboukris(a)gmail.com
Target Milestone: ---
Recently MS has announce they plan to enforce channel-bindings for LDAP over
TLS (ADV190023).
To support it on client side, we need to pass "tls-endpoint" bindings (RFC
5929) to the SASL plugin, and make use of that in GSSAPI.
See also:
https://github.com/cyrusimap/cyrus-sasl/pull/601
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8753
--- Comment #7 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
RE25:
• 680affe6
by OndÅ™ej KuznÃk at 2022-02-18T23:20:09+00:00
ITS#8753 Document LDAP_OPT_X_TLS_PEERKEY_HASH
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8753
--- Comment #6 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
RE26:
• 394f6ad5
by OndÅ™ej KuznÃk at 2022-02-18T23:18:31+00:00
ITS#8753 Document LDAP_OPT_X_TLS_PEERKEY_HASH
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8753
--- Comment #5 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
head:
• a2a2ebba
by OndÅ™ej KuznÃk at 2022-02-14T20:32:29+00:00
ITS#8753 Document LDAP_OPT_X_TLS_PEERKEY_HASH
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9797
Issue ID: 9797
Summary: userPrincipalName doesn't work with OpenLDAP
Product: OpenLDAP
Version: 2.6.0
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: akshay.polji(a)gmail.com
Target Milestone: ---
Recently I was trying to perform a POC that included the Hashicorp vault.
I tried to configure Hashicorp Vault LDAP login using OpenLDAP.
However, I failed to do so as the Hashicorp vault was trying to query the
OpenLDAP with filter="(?userPrincipalName=test1(a)example.com)"
I got the query o/p as
conn=1146 op=1 SEARCH RESULT tag=101 err=32 nentries=0 text=
onn=1146 fd=12 closed (connection lost)
Even though the ldapsearch worked for the same user.
The problem seems to be the fact that OpenLDAP doesn't support
"userPrincipalName" as the attribute.
Wanted to understand if 'userPrincipalName' could be added?
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9000
--- Comment #8 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
(In reply to sebastien.chaumat from comment #7)
> This bug is still present in 2.4.49 (ubuntu).
The OpenLDAP 2.4 series is historic and out of support.
The memberof overlay is deprecated in OpenLDAP 2.5 and later and the dynlist
overlay should be used to provide memberOf support.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9000
--- Comment #7 from sebastien.chaumat(a)qspin.be ---
This bug is still present in 2.4.49 (ubuntu).
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8375
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|2.6.2 |2.7.0
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8255
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|bugs(a)openldap.org |ondra(a)mistotebe.net
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9792
Issue ID: 9792
Summary: During replication, slapd tries to modify
hasSubordinates (and fails)
Product: OpenLDAP
Version: 2.5.9
Hardware: x86_64
OS: Linux
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: christophe(a)armaghast.eu
Target Milestone: ---
During relication, this strange error occurs:
Jan 25 14:46:42 annu slapd[471040]: conn=1001 op=2796 MOD attr=userPassword
pwdChangedTime pwdHistory entryCSN modifiersName modifyTimestamp
hasSubordinates
Jan 25 14:46:42 annu slapd[471040]: conn=1001 op=2796 RESULT tag=103 err=16
qtime=0.000030 etime=0.000462 text=modify/delete: hasSubordinates: no such
attribute
Why does slapd try to modify this (virtual) attribute ?
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9350
Issue ID: 9350
Summary: Expand test suite for null base
Product: OpenLDAP
Version: 2.5
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: build
Assignee: bugs(a)openldap.org
Reporter: quanah(a)openldap.org
Target Milestone: ---
Currently we have no tests that use the empty suffix (null base).
This is an entirely valid configuration setup, and there are unique challenges
and bugs that crop up with this usage.
We need to ensure we're covering this use case, particularly with syncrepl and
delta-syncrepl configurations.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8255
OndÅ™ej KuznÃk <ondra(a)mistotebe.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |IN_PROGRESS
Ever confirmed|0 |1
--- Comment #10 from OndÅ™ej KuznÃk <ondra(a)mistotebe.net> ---
https://git.openldap.org/openldap/openldap/-/merge_requests/487 for the
clarification.
--
You are receiving this mail because:
You are on the CC list for the issue.