https://bugs.openldap.org/show_bug.cgi?id=8345
Ondřej Kuzník <ondra(a)mistotebe.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.openldap.org/s
| |how_bug.cgi?id=9001
--- Comment #4 from Ondřej Kuzník <ondra(a)mistotebe.net> ---
That sounds fine by me.
BTW liblutil is currently a static-only library, which is why none of the
libldap code uses it. Same issue I'm hitting with using AVL code in ITS#9001
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=9001
Ondřej Kuzník <ondra(a)mistotebe.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.openldap.org/s
| |how_bug.cgi?id=8345
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8837
--- Comment #7 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
I was really planning to get this fixed as part of 8628, which covers a bunch
of modules with the same problem.. ;)
--
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 #5 from Ondřej Kuzník <ondra(a)mistotebe.net> ---
On Fri, Mar 27, 2020 at 05:02:02PM +0000, openldap-its(a)openldap.org wrote:
> Hello,
>
> Here are the things I have basically tested:
>
> - 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.
Hi David,
could you show a configuration when this happens? I cannot reproduce
either issue on master.
I will update the manpage to mention pwdLastSuccess is used.
> - 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.
Again, can't seem to be able to reproduce that and test022-ppolicy
passes for me.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8837
Ryan Tandy <ryan(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |TEST
Status|UNCONFIRMED |RESOLVED
--- Comment #6 from Ryan Tandy <ryan(a)openldap.org> ---
Fixed in d86caacaa1772e0c9a4c856558e1c5d538c5b549
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8456
Ryan Tandy <ryan(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WORKSFORME
Status|UNCONFIRMED |RESOLVED
--- Comment #2 from Ryan Tandy <ryan(a)openldap.org> ---
Hello,
Thank you for the report, however I cannot reproduce this segfault, with 2.4.42
or with any other version I tried.
e.g.
# slapacl -D cn=admin,dc=example,dc=com -u -b uid=nonexistent,dc=example,dc=com
objectClass
authcDN: "cn=admin,dc=example,dc=com"
objectClass: manage(=mwrscxd)
Closing as WORKSFORME, feel free to reopen if you can still reproduce.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=7530
Ryan Tandy <ryan(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |CONFIRMED
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=9057
Ryan Tandy <ryan(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WORKSFORME
--- Comment #1 from Ryan Tandy <ryan(a)openldap.org> ---
Hello,
The TLS tests are passing for me on Ubuntu 18.04.
I will close this bug now. If you still reproduce this failure, please reopen
the bug and attach the file "tests/testrun/test.out".
Thank you!
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8729
Ryan Tandy <ryan(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WORKSFORME
Status|UNCONFIRMED |RESOLVED
--- Comment #1 from Ryan Tandy <ryan(a)openldap.org> ---
Hello, I'm afraid I can't reproduce this. I'm using OpenLDAP 2.4.47 and Heimdal
on Debian buster.
I've configured slapd both as a server (allowing clients to authenticate using
GSSAPI) and as a client (running a syncrepl client with GSSAPI bind). I have
broken the setup in a bunch of different ways (removing slapd's credentials
cache; stopping the KDC; entering wrong info in /etc/krb5.conf; deleting
/etc/krb5.conf) and I have not seen it fail to respect my olcAuthzRegexp rules
for EXTERNAL (tested ldapi: gidNumber/uidNumber as well as TLS client cert).
Marking WORKSFORME, but feel free to reopen if you can provide further info
about your case. Thanks!
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8376
--- Comment #13 from Ryan Tandy <ryan(a)openldap.org> ---
I may have set up my environment incorrectly for this, but I don't see how the
patch fixes the issue described, since getaddrinfo() is also backed by NSS.
With the patch applied (note getaddrinfo() at #7) I still see nss_ldap
deadlocking with itself:
(gdb) bt
#0 0x00007ffff7d1329c in __lll_lock_wait () from
/lib/x86_64-linux-gnu/libpthread.so.0
#1 0x00007ffff7d0c714 in pthread_mutex_lock () from
/lib/x86_64-linux-gnu/libpthread.so.0
#2 0x00007ffff7dd8683 in _nss_ldap_enter () at ldap-nss.c:595
#3 0x00007ffff7dd9fbc in _nss_ldap_getbyname (args=args@entry=0x7fffffffc500,
result=0x7fffffffc650, buffer=0x7fffffffc8c0 "\377\002", buflen=1024,
errnop=0x7ffff7fcb4c0,
filterprot=0x7ffff7dee980 <_nss_ldap_filt_gethostbyname>
"(&(objectClass=ipHost)(cn=%s))", sel=LM_HOSTS, parser=0x7ffff7ddc5e0
<_nss_ldap_parse_hostv4>) at ldap-nss.c:3509
#4 0x00007ffff7ddc645 in _nss_ldap_gethostbyname2_r (af=<optimized out>,
h_errnop=0x7ffff7fcb524, errnop=<optimized out>, buflen=<optimized out>,
buffer=<optimized out>, result=<optimized out>, name=<optimized out>) at
ldap-hosts.c:287
#5 _nss_ldap_gethostbyname2_r (name=<optimized out>, af=<optimized out>,
result=<optimized out>, buffer=<optimized out>, buflen=<optimized out>,
errnop=<optimized out>, h_errnop=0x7ffff7fcb524) at ldap-hosts.c:269
#6 0x00007ffff7eebfb7 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#7 0x00007ffff7eece37 in getaddrinfo () from /lib/x86_64-linux-gnu/libc.so.6
#8 0x00007ffff7db257e in ldap_pvt_get_fqdn (name=0x7fffffffcd50 "t570",
name@entry=0x0) at util-int.c:866
#9 0x00007ffff7db09c5 in ldap_int_initialize (gopts=gopts@entry=0x7ffff7dcfde0
<ldap_int_global_options>, dbglvl=dbglvl@entry=0x0) at init.c:645
#10 0x00007ffff7d97122 in ldap_create (ldp=ldp@entry=0x7fffffffcec8) at
open.c:109
#11 0x00007ffff7d9737f in ldap_initialize (ldp=ldp@entry=0x7ffff7de8360
<__session>, url=url@entry=0x7ffff7de8be8 <__configbuf+1480> "ldap://::1") at
open.c:241
#12 0x00007ffff7dd7796 in do_init_session (ld=0x7ffff7de8360 <__session>,
defport=0, uri=0x7ffff7de8be8 <__configbuf+1480> "ldap://::1") at
ldap-nss.c:1066
#13 do_init () at ldap-nss.c:1360
#14 0x00007ffff7dd8a73 in _nss_ldap_search_s (args=args@entry=0x7fffffffe8e0,
filterprot=filterprot@entry=0x7ffff7dee980 <_nss_ldap_filt_gethostbyname>
"(&(objectClass=ipHost)(cn=%s))", sel=sel@entry=LM_HOSTS,
user_attrs=user_attrs@entry=0x0, sizelimit=sizelimit@entry=1,
res=res@entry=0x7fffffffe870) at ldap-nss.c:3098
#15 0x00007ffff7dd9ff3 in _nss_ldap_getbyname (args=args@entry=0x7fffffffe8e0,
result=0x7ffff7fc8060, buffer=0x55555555e8d0 "\377\002", buflen=1024,
errnop=0x7ffff7fcb4c0,
filterprot=0x7ffff7dee980 <_nss_ldap_filt_gethostbyname>
"(&(objectClass=ipHost)(cn=%s))", sel=LM_HOSTS, parser=0x7ffff7ddc5e0
<_nss_ldap_parse_hostv4>) at ldap-nss.c:3517
#16 0x00007ffff7ddc645 in _nss_ldap_gethostbyname2_r (af=<optimized out>,
h_errnop=0x7fffffffe9ec, errnop=<optimized out>, buflen=<optimized out>,
buffer=<optimized out>, result=<optimized out>, name=<optimized out>) at
ldap-hosts.c:287
#17 _nss_ldap_gethostbyname2_r (name=<optimized out>, af=<optimized out>,
result=<optimized out>, buffer=<optimized out>, buflen=<optimized out>,
errnop=<optimized out>, h_errnop=0x7fffffffe9ec) at ldap-hosts.c:269
#18 0x00007ffff7f148b5 in gethostbyname2_r () from
/lib/x86_64-linux-gnu/libc.so.6
#19 0x00007ffff7f145ac in gethostbyname2 () from
/lib/x86_64-linux-gnu/libc.so.6
#20 0x0000555555558bc7 in ?? ()
#21 0x000055555555771c in ?? ()
#22 0x00007ffff7e2d09b in __libc_start_main () from
/lib/x86_64-linux-gnu/libc.so.6
#23 0x00005555555577ea in ?? ()
What am I missing, please?
--
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 #4 from Ryan Tandy <ryan(a)openldap.org> ---
(In reply to David Coutadeur from comment #3)
> For information, I had to fix a typo before it compiles: the manpage of
> pbkdf2 overlay was not correctly written:
> in contrib/slapd-modules/passwd/pbkdf2/Makefile:
> ```
> MANPAGES = slapd-pw-pbkdf2.5
> ```
> should be:
> ```
> MANPAGES = slapo-pw-pbkdf2.5
That's https://bugs.openldap.org/show_bug.cgi?id=8837
--
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 #3 from David Coutadeur <david.coutadeur(a)gmail.com> ---
Hello,
I have made some new tests on OpenLDAP master branch.
For information, I had to fix a typo before it compiles: the manpage of pbkdf2
overlay was not correctly written:
in contrib/slapd-modules/passwd/pbkdf2/Makefile:
```
MANPAGES = slapd-pw-pbkdf2.5
```
should be:
```
MANPAGES = slapo-pw-pbkdf2.5
```
Here are the things I have basically tested:
- pwdMaxLength: OK
- 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.
- 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.
- basic integration with ppm, and in particular the pwdCheckModuleArg
(https://github.com/ltb-project/ppm): OK (but will need some adaptation of the
check_password signature: https://github.com/ltb-project/ppm/issues/20)
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=9058
Ryan Tandy <ryan(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
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=9058
Ryan Tandy <ryan(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #1 from Ryan Tandy <ryan(a)openldap.org> ---
Already fixed in 2.5 by cd914149a665167b2c5ae16baa0c438824588819
--
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 #2 from David Coutadeur <david.coutadeur(a)gmail.com> ---
Hello,
Just for tracability, I have made some tests about this feature some time ago,
when it was available only at
https://github.com/mistotebe/openldap/tree/ppolicy10
I have basically tested these at 2020-01-20:
- pwdMaxLength
- pwdLastSuccess, pwdMaxIdle
- pwdStartTime, pwdEndTime
- basic integration with ppm (https://github.com/ltb-project/ppm)
I am planning do test again on RE25 branch of OpenLDAP soon.
David
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8676
--- Comment #12 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• 57b7003a
by Sergei Trofimovich at 2020-03-26T22:06:41+00:00
thr_posix.c: fix implicit function declaration for 'pthread_setconcurrency'
thr_posix.c: In function 'ldap_pvt_thread_set_concurrency':
thr_posix.c:96:9: error: implicit declaration of function
'pthread_setconcurrency'
return pthread_setconcurrency( n );
^~~~~~~~~~~~~~~~~~~~~~
pthread_setcanceltype
Signed-off-by: Sergei Trofimovich <slyfox(a)gentoo.org>
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8676
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|has_patch, IPR_OK, |
|OL_2_5_REQ, |
|openldap-scratch |
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8676
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |TEST
Status|IN_PROGRESS |RESOLVED
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8837
--- Comment #5 from Ryan Tandy <ryan(a)openldap.org> ---
(In reply to Howard Chu from comment #4)
> The totp module is actually an overlay. There is nothing to rename there.
OK. Sorry, that was an assumption based on it being under passwd/. Thanks for
the correction.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8837
--- Comment #4 from Howard Chu <hyc(a)symas.com> ---
(In reply to Ryan Tandy from comment #2)
> (In reply to Quanah Gibson-Mount from comment #1)
> > Actually, since it is an overlay, the slapo prefix is correct (o=overlay)
> > and the slapd prefix is incorrect (used for backends).
>
> I don't think calling a password module an "overlay" is accurate.
>
> I agree with Peter, it should be called slapd-pw-pbkdf2.5 (and slapo-totp.5
> to slapd-pw-totp.5 while we're at it). Or introduce a new "slapp-"
> convention if it must be distinguished from backends, but that seems
> overkill...
The totp module is actually an overlay. There is nothing to rename there.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=6958
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
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=6958
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WORKSFORME
Status|UNCONFIRMED |RESOLVED
--- Comment #5 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Unable to reproduce on FreeBSD 12.1 patch level 3
include ./schema/core.schema
include ./schema/cosine.schema
include ./schema/corba.schema
include ./schema/java.schema
include ./schema/inetorgperson.schema
include ./schema/misc.schema
include ./schema/nis.schema
include ./schema/openldap.schema
include ./schema/duaconf.schema
include ./schema/dyngroup.schema
pidfile /home/build/git/openldap/tests/testrun/slapd.1.pid
argsfile /home/build/git/openldap/tests/testrun/slapd.1.args
TLSCACertificatePath /home/build/git/openldap/tests/testrun/tls/ca/certs/
TLSCACertificateFile
/home/build/git/openldap/tests/testrun/tls/ca/certs/testsuiteCA.crt
TLSCertificateKeyFile
/home/build/git/openldap/tests/testrun/tls/private/localhost.key
TLSCertificateFile
/home/build/git/openldap/tests/testrun/tls/certs/localhost.crt
TLSVerifyClient allow
TLSCRLCheck all
../servers/slapd/slapindex -f testrun/slapd.1.conf -v
[build@freebsd12 ~/git/openldap/tests]$ echo $?
0
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8837
--- Comment #3 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
(In reply to Ryan Tandy from comment #2)
> (In reply to Quanah Gibson-Mount from comment #1)
> > Actually, since it is an overlay, the slapo prefix is correct (o=overlay)
> > and the slapd prefix is incorrect (used for backends).
>
> I don't think calling a password module an "overlay" is accurate.
>
> I agree with Peter, it should be called slapd-pw-pbkdf2.5 (and slapo-totp.5
> to slapd-pw-totp.5 while we're at it). Or introduce a new "slapp-"
> convention if it must be distinguished from backends, but that seems
> overkill...
Pretty sure we actually discussed slapm- for module in the past, actually.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8847
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |IN_PROGRESS
Assignee|bugs(a)openldap.org |quanah(a)openldap.org
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=8654
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|has_patch, OL_2_5_REQ, |
|openldap-scratch |
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=8654
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
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=8654
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DUPLICATE
Status|UNCONFIRMED |RESOLVED
--- Comment #10 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Missing IPR, 8847 has IPR and more recent work.
*** 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
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |daniel.le(a)exfo.com
--- Comment #28 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
*** Bug 8654 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=8675
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |TEST
Status|IN_PROGRESS |RESOLVED
--- Comment #7 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• 23af2c36
by Kurt Zeilenga at 2020-03-26T18:45:00+00:00
ITS#8675 - Fix tools to not continue on TLS error
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8376
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Assignee|bugs(a)openldap.org |quanah(a)openldap.org
Status|UNCONFIRMED |IN_PROGRESS
--- Comment #12 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
https://git.openldap.org/openldap/openldap/-/merge_requests/14
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8676
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|bugs(a)openldap.org |quanah(a)openldap.org
Ever confirmed|0 |1
Status|UNCONFIRMED |IN_PROGRESS
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8675
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |IN_PROGRESS
Ever confirmed|0 |1
Assignee|bugs(a)openldap.org |quanah(a)openldap.org
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=9003
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |IN_PROGRESS
--- Comment #3 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
https://git.openldap.org/openldap/openldap/-/merge_requests/11
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8837
--- Comment #2 from Ryan Tandy <ryan(a)openldap.org> ---
(In reply to Quanah Gibson-Mount from comment #1)
> Actually, since it is an overlay, the slapo prefix is correct (o=overlay)
> and the slapd prefix is incorrect (used for backends).
I don't think calling a password module an "overlay" is accurate.
I agree with Peter, it should be called slapd-pw-pbkdf2.5 (and slapo-totp.5 to
slapd-pw-totp.5 while we're at it). Or introduce a new "slapp-" convention if
it must be distinguished from backends, but that seems overkill...
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8837
--- Comment #1 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Actually, since it is an overlay, the slapo prefix is correct (o=overlay) and
the slapd prefix is incorrect (used for backends).
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8837
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|fix pw-pbkdf2 man-mage name |fix pw-pbkdf2 manpage name
|to get it installed |to get it installed
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=3217
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.openldap.org/s
| |how_bug.cgi?id=9197
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=4420
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.openldap.org/s
| |how_bug.cgi?id=9197
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8804
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|2.5.0 |---
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=8804
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
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=8804
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
From Klaus via direct email on 3/24/2020:
we migrated to version 2.4.48 half a year ago. With this version the issue does
not happen.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=5534
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
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=5534
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
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=5534
--- Comment #10 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Transaction support was added to OpenLDAP in 2014 (for the 2.5 release series):
commit 32f05e96f7520bc5b99b7e5302ff08d33e550199
Author: Howard Chu <hyc(a)openldap.org>
Date: Mon Sep 15 21:44:20 2014 +0100
Flesh out txn support
Only in back-mdb; back-bdb needs work but it's deprecated;
not worth the effort. In particular txn, retry after deadlocks
makes the whole thing too messy.
--
You are receiving this mail because:
You are on the CC list for the bug.