https://bugs.openldap.org/show_bug.cgi?id=7706
Ondřej Kuzník <ondra(a)mistotebe.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|overlays |slapd
--- Comment #3 from Ondřej Kuzník <ondra(a)mistotebe.net> ---
lastbind fuctionality has been integrated into core slapd to support ppolicy
draft 10 in ITS#9156, refiling.
The validity of this feature request is unaffected.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=7697
Ondřej Kuzník <ondra(a)mistotebe.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WONTFIX
See Also| |https://bugs.openldap.org/s
| |how_bug.cgi?id=9156
Status|UNCONFIRMED |RESOLVED
--- Comment #4 from Ondřej Kuzník <ondra(a)mistotebe.net> ---
lastbind fuctionality has been integrated into core slapd ti support ppolicy
draft 10 in ITS#9156
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=9156
Ondřej Kuzník <ondra(a)mistotebe.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.openldap.org/s
| |how_bug.cgi?id=7697
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=7384
Ondřej Kuzník <ondra(a)mistotebe.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DUPLICATE
Keywords|OL_2_5_REQ |
Status|UNCONFIRMED |RESOLVED
Target Milestone|2.5.0 |2.4.50
--- Comment #6 from Ondřej Kuzník <ondra(a)mistotebe.net> ---
Sounds like ITS#9171 - same assert and there are two overlays and both register
a response callback. Feel free to reopen otherwise.
*** This bug has been marked as a duplicate of bug 9171 ***
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=9171
Ondřej Kuzník <ondra(a)mistotebe.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ghola(a)rebelbase.com
--- Comment #7 from Ondřej Kuzník <ondra(a)mistotebe.net> ---
*** Bug 7384 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8802
--- Comment #2 from Ryan Tandy <ryan(a)openldap.org> ---
I don't understand what's going on here. Why do we see "replace pwdChangedTime"
and "add pwdHistory" twice for a single "replace userPassword"? I'm testing
exactly the same version as the reporter and those only occur once each for me.
I think this is an invalid configuration, with ppolicy configured _twice_ on
the database.
If I do this invalid config:
overlay ppolicy
ppolicy_default cn=ppolicy,dc=example,dc=com
overlay ppolicy
ppolicy_default cn=ppolicy,dc=example,dc=com
then I get that same result:
5e7abb2b mdb_modify_internal: replace userPassword
5e7abb2b mdb_modify_internal: replace pwdChangedTime
5e7abb2b mdb_modify_internal: add pwdHistory
5e7abb2b mdb_modify_internal: replace pwdChangedTime
5e7abb2b mdb_modify_internal: add pwdHistory
5e7abb2b mdb_modify_internal: 20 modify/add: pwdHistory: value #0 already
exists
5e7abb2b mdb_modify: modify failed (20)
Mats, can you please confirm this was a configuration error and we can close
it?
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=9195
Bug ID: 9195
Summary: Poor error messaging for TLS connect/accept with
GnuTLS
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: ---
When doing something like:
./clients/tools/ldapsearch -H ldap://171.67.218.153 -ZZ -x
With OpenSSL we get:
ldap_start_tls: Connect error (-11)
additional info: TLS: hostname does not match CN in peer certificate
With GnuTLS we just get:
ldap_start_tls: Connect error (-11)
additional info: (unknown error code)
We can do better. My thoughts right now are:
1. stash the verify status in the session;
2. return a specific value to indicate verify failed;
3. have tlsg_session_errmsg recognize that value and print the detailed
verification status.
GnuTLS 3.5 added GNUTLS_E_CERTIFICATE_VERIFICATION_ERROR, but I don't think
it's worth bumping our required version for that alone. For the time being
(i.e. 2.5) I'd like to keep 3.3 and maybe even 3.2 supported...
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8683
--- Comment #3 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• 71d4e47e
by Quanah Gibson-Mount at 2020-03-24T17:03:29+00:00
ITS#8683 - Delete client-pr information from slapd-meta(5) for RE24
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8683
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|IN_PROGRESS |RESOLVED
--
You are receiving this mail because:
You are on the CC list for the bug.