https://bugs.openldap.org/show_bug.cgi?id=6567
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |IN_PROGRESS
Assignee|bugs(a)openldap.org |quanah(a)openldap.org
--- Comment #13 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
https://git.openldap.org/openldap/openldap/-/merge_requests/28
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=6937
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |IN_PROGRESS
Ever confirmed|0 |1
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=6937
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|bugs(a)openldap.org |quanah(a)openldap.org
--- Comment #2 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
https://git.openldap.org/openldap/openldap/-/merge_requests/27
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=7335
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Error in slapo-refint man |Create process for updating
|page |man pages to handle both
| |cn=config and slapd.conf
| |configurations
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8581
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |OL_2_5_REQ
Summary|slapd-meta backend SSL |slapd-meta backend SSL
|negociation timeout |negotiation timeout
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8861
--- Comment #4 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
(In reply to Howard Chu from comment #3)
> Sounds more like the back-ldap manpage is wrong. The use of "ldaps" is
> implicit in the URI, so there's no point in supporting it here and it should
> be an error to allow it here. In particular it makes no sense to allow it
> here if it differs from the URI.
Ok, although that doesn't entirely answer the rest of my question (i.e., about
tls_reqcert etc missing from back-meta).
Ironically I would note you're literally the person who added the "ldaps"
option to back-ldap.
a6a8fb514b (Howard Chu 2007-01-08 23:36:24 +0000 511) {
BER_BVC( "ldaps" ), LDAP_BACK_F_TLS_LDAPS },
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8861
--- Comment #3 from Howard Chu <hyc(a)openldap.org> ---
(In reply to Quanah Gibson-Mount from comment #0)
> Full_Name: Quanah Gibson-Mount
> Version: HEAD
> OS: N/A
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (47.208.148.239)
>
>
> The slapd-asyncmeta(5) and slapd-meta(5) man pages are missing the fact that
> they support the "ldaps" option to the "tls" keyword. This section should be
> updated along the lines of back-ldap which also has this option as a keyword.
Sounds more like the back-ldap manpage is wrong. The use of "ldaps" is implicit
in the URI, so there's no point in supporting it here and it should be an error
to allow it here. In particular it makes no sense to allow it here if it
differs from the URI.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8861
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
CC| |nivanova(a)symas.com
Status|UNCONFIRMED |CONFIRMED
--- Comment #2 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Hi Nadya,
In looking over the back-meta man page and code and comparing it to what's in
back-ldap, I think the man page for back-meta needs significant updating for
the TLS option. Can you confirm the following?
In back-ldap, we have:
tls {none|[try-]start|[try-]propagate|ldaps} [starttls=no]
[tls_cert=<file>] [tls_key=<file>] [tls_cacert=<file>]
[tls_cacertdir=<path>]
[tls_reqcert=never|allow|try|demand] [tls_cipher_suite=<ciphers>]
[tls_crlcheck=none|peer|all]
Specify TLS settings for regular connections.
The first parameter only applies to ldap:// connections and so at
the moment, none and ldaps are equivalent.
With propagate, the proxy issues StartTLS operation only
if the original connection has a TLS layer set up. The try- prefix instructs
the proxy to
continue operations if the StartTLS operation failed; its use is
not recommended.
The TLS settings default to the same as the main slapd TLS
settings, except for tls_reqcert which defaults to "demand" and starttls which
is overshadowed
by the first keyword and thus ignored.
I believe all of the above options also apply to back-meta. Are the caveats
about tls_reqcert the same?
For back-meta, all we have currently is:
tls {[try-]start|[try-]propagate}
execute the StartTLS extended operation when the connection is
initialized; only works if the URI directive protocol scheme is not ldaps://.
propagate
issues the StartTLS operation only if the original connection
did. The try- prefix instructs the proxy to continue operations if the
StartTLS operation
failed; its use is highly deprecated. If set before any target
specification, it affects all targets, unless overridden by any per-target
directive.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8861
--- Comment #1 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
"none" is also missing
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=9156
--- Comment #9 from David Coutadeur <david.coutadeur(a)gmail.com> ---
Hello,
Thanks Ondřej for your answer to my test results.
Here are some updates!
> - pwdLastSuccess, pwdMaxIdle: KO: the user is able to authenticate after the
> pwdMaxIdle delay. Also, the pwdLastSuccess is never written (see
> https://tools.ietf.org/html/draft-behera-ldap-password-policy-10#section-5.…).
> For information, I have enabled lastbind. The slapo-ppolicy man page does not
> mention pwdLastSuccess by the way.
I finally succeeded in making it work.
Thanks for pointing test022-ppolicy, it was helpfull.
The problem was that I was using old lastbind overlay, which in some way was in
conflict with current lastbind.
If I understand correctly, the current lastbind is now completely included into
OpenLDAP 2.5?
It is very important to me, because as a maintainer of OpenLDAP-LTB, we would
have to warn people that the configuration parameters have changed (overlay
lastbind -> lastbind on) and that the overlay won't be provided any more.
> - pwdStartTime, pwdEndTime: OK, but there is no special ppolicy code returned,
> and if I read correctly the draft
> (https://tools.ietf.org/html/draft-behera-ldap-password-policy-10#section-7.1),
> an "accountLocked" extended error code should be triggered.
I was simply missing the ppolicy_use_lockout parameter.
One remark though: the reason of locking is not very explicit.
I understand that many companies/organizations will consider it is a good thing
to hide this information for security reasons. For the others, maybe could we
have some sort of level?
Configuration example:
lockout_message_description [none|minimal|verbose]
In the specification the extended error code could simply stay as it is:
"(1)Account locked", but we could add a more precise description in case the
verbose mode is enabled: "(1)Account locked (account unused for a too long
time)"
Regards,
David
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8893
Ryan Tandy <ryan(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|FIXED |DUPLICATE
--- Comment #7 from Ryan Tandy <ryan(a)openldap.org> ---
*** This bug has been marked as a duplicate of bug 8847 ***
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8847
Ryan Tandy <ryan(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sudhir.singam(a)gmail.com
--- Comment #30 from Ryan Tandy <ryan(a)openldap.org> ---
*** Bug 8893 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=9098
--- Comment #11 from maxime.besson(a)worteks.com <maxime.besson(a)worteks.com> ---
My original report mentions it: candidates[ i ].sr_msgid is -1
(META_MSGID_IGNORE)
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=9098
--- Comment #10 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Ok, it is halting on this check:
assert( candidates[ i ].sr_msgid >= 0 || candidates[ i ].sr_msgid ==
META_MSGID_CONNECTING );
So what we need is in thread 1, frame 2, to know what the value of
candidates[i].sr_msgid is.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=9098
--- Comment #8 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
(In reply to maxime.besson(a)worteks.com from comment #7)
> Created attachment 704 [details]
> assert backtrace
>
> A little bird told be this report was missing a backtrace.
What we need is a full backtrace. ;)
thr apply all bt full
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8296
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|FEEDBACK |SUSPENDED
Status|RESOLVED |VERIFIED
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8296
--- Comment #11 from maurizio.lattuada(a)gmail.com <maurizio.lattuada(a)gmail.com> ---
Hi Quanah,
unfortunately I'm not working on that project anymore (not for that company
too), so I had not anymore the chance to figure it out.
Sorry for that.
Cheers,
Maurizio
Il giorno dom 22 mar 2020 alle ore 01:53 <openldap-its(a)openldap.org> ha
scritto:
> https://bugs.openldap.org/show_bug.cgi?id=8296
>
> Quanah Gibson-Mount <quanah(a)openldap.org> changed:
>
> What |Removed |Added
>
> ----------------------------------------------------------------------------
> Status|UNCONFIRMED |RESOLVED
> Resolution|--- |FEEDBACK
>
> --- Comment #10 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
> Hi Maurizio,
>
> Do you still hit this issue with the current release? I apologize for the
> delay in response. Numerous fixes and changes have been made to syncprov
> since
> this was filed.
>
> Regards,
> Quanah
>
> --
> You are receiving this mail because:
> You reported the bug.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=9179
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.openldap.org/s
| |how_bug.cgi?id=9205
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=9121
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |TEST
Status|CONFIRMED |RESOLVED
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=9121
--- Comment #4 from Howard Chu <hyc(a)openldap.org> ---
(In reply to Quanah Gibson-Mount from comment #3)
> Current code periodically triggers a SEGV in test044:
fixed in 5bfd8d88887eff4581463cb20f9262bf51686908
>
> (gdb) cont
> Continuing.
> [New Thread 0x7fd9d2ce2700 (LWP 18294)]
> [New Thread 0x7fd9d24e1700 (LWP 18295)]
>
> Thread 3 "lt-slapd" received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7fd9d2ce2700 (LWP 18294)]
> 0x00007fd9d42a697c in comp_candidates (op=0x7fd9c4002900,
> rtxn=0x7fd9c410ad10, mra=0x7fd9c4005430, f=0x1c, ids=0x7fd9d0c5f018,
> tmp=0x7fd9d095f018, stack=0x7fd9d0d5f018)
> at filterindex.c:464
> 464 filterindex.c: No such file or directory.
>
>
> #0 0x00007fd9d42a697c in comp_candidates (op=0x7fd9c4002900,
> rtxn=0x7fd9c410ad10, mra=0x7fd9c4005430, f=0x1c, ids=0x7fd9d0c5f018,
> tmp=0x7fd9d095f018, stack=0x7fd9d0d5f018)
> at filterindex.c:464
> rc = 1409434333
> #1 0x00007fd9d42a6bb2 in ext_candidates (op=0x7fd9c4002900,
> rtxn=0x7fd9c410ad10, mra=0x7fd9c4005430, ids=0x7fd9d0c5f018,
> tmp=0x7fd9d095f018, stack=0x7fd9d0d5f018)
> at filterindex.c:507
> No locals.
> #2 0x00007fd9d42a5c0f in mdb_filter_candidates (op=0x7fd9c4002900,
> rtxn=0x7fd9c410ad10, f=0x7fd9c4005410, ids=0x7fd9d0c5f018,
> tmp=0x7fd9d095f018, stack=0x7fd9d0d5f018)
> at filterindex.c:206
> rc = 0
> aa = 0x7fd9c40016c0
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8245
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |TEST
Keywords|has_patch, OL_2_5_REQ |
Status|UNCONFIRMED |RESOLVED
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8245
--- Comment #14 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• 6d6a3300
by OndÅ™ej KuznÃk at 2020-04-06T20:44:09+00:00
ITS#8245 Use Relax control to avoid uniqueness checks
Still needs to retrieve the entry for ACL resolution until we can
restrict controls with ACLs
--
You are receiving this mail because:
You are on the CC list for the bug.