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.