https://bugs.openldap.org/show_bug.cgi?id=9181
--- Comment #6 from Howard Chu <hyc(a)openldap.org> ---
(In reply to Ryan Tandy from comment #5)
> Hi Howard, I'm testing my patch for ITS#8383 and this one seems to have
> broken the build in my MSYS2/MinGW environment:
>
> cc -g -O2 -I../../include -I../../include -c -o ntservice.o
> ntservice.c
> In file included from ../../include/portable.h:1173,
> from ntservice.c:20:
> ../../include/ldap_int_thread.h:156:43: error: unknown type name
> 'ldap_pvt_thread_mutex_t'; did you mean 'ldap_int_thread_mutex_t'?
> 156 | ldap_pvt_thread_mutex_init_first LDAP_P(( ldap_pvt_thread_mutex_t
> *mutex ));
> | ^~~~~~~~~~~~~~~~~~~~~~~
> ../../include/ldap_cdefs.h:32:25: note: in definition of macro 'LDAP_P'
> 32 | # define LDAP_P(protos) protos
> | ^~~~~~
> make[2]: *** [<builtin>: ntservice.o] Error 1
>
> ldap_int_thread.h is included at the top of ldap_pvt_thread.h, so this
> declaration is seen before the ldap_pvt_* typedefs.
Can you retry, changing that declaration to use ldap_int_thread_mutex_t
instead?
--
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
----------------------------------------------------------------------------
Keywords|OL_2_5_REQ |
Resolution|--- |TEST
Status|IN_PROGRESS |RESOLVED
--- Comment #3 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• a97eed06
by Quanah Gibson-Mount at 2020-04-15T19:32:28+00:00
ITS#6937 - Remove unused proctitle bits
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=6531
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |OL_2_5_REQ
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=6166
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |OL_2_5_REQ
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=7878
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |2.5.0
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=7878
Ryan Tandy <ryan(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|IN_PROGRESS |RESOLVED
Resolution|--- |TEST
--- Comment #6 from Ryan Tandy <ryan(a)openldap.org> ---
Commits:
38f9dd2f
by Ryan Tandy at 2020-04-14T10:04:33-07:00
ITS#7878 Replace uint32_t with unsigned in back-mdb
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=9043
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Keywords|OL_2_5_REQ |
Resolution|--- |TEST
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=9043
--- Comment #1 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• f6d9fdc4
by Ondřej Kuzník at 2020-04-14T09:58:03+01:00
ITS#9043 Improve replication loggging
--
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 #10 from Ondřej Kuzník <ondra(a)mistotebe.net> ---
On Thu, Apr 09, 2020 at 02:41:54PM +0000, openldap-its(a)openldap.org wrote:
> 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?
No, features you might want to configure lastbind with do not (yet) have
an equivalent in the core implementation, so I haven't removed it from
2.5 yet.
> 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]
The message is output by the client, the only information provided is
the ppolicy response control:
https://tools.ietf.org/html/draft-behera-ldap-password-policy-10#section-6.2
(or rather
https://git.openldap.org/openldap/openldap/-/blob/master/doc/drafts/draft-b…)
Providing any more information would need to be integrated into the
draft as well.
> 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)"
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8731
--- Comment #3 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
• bbe20cbf
by Ryan Tandy at 2020-04-13T18:57:50+00:00
ITS#8731 cleanup unused logbuf
--
You are receiving this mail because:
You are on the CC list for the bug.