openldap-bugs

openldap-bugs@openldap.org

1 participants
20963 discussions

ITS#8223 Windows replication error
by hyc＠symas.com 28 Oct '15

28 Oct '15

> Hello, > > I have additional information. The problem is the entryCSN. > User 1, which got replicated has entryCSN: > 20150827083333.751721Z#000000#001#000000 > user 2, which got NOT replicated has entryCSN: > 20150827083333.119585Z#000000#001#000000, which seems to be in the past > user 3, replicated, 20150827083334.847604Z#000000#001#000000 > user 4, not replicated 20150827083334.228113Z#000000#001#000000, which > seems to be in the past > user 5, replicated 20150827083335.588191Z#000000#001#000000 > user 6, replicated 20150827083335.946835Z#000000#001#000000 > user 7 not replicated 20150827083335.282686Z#000000#001#000000, which > seems to be in the past > > So in previous posts I got the answer, that microseconds exact time > synchronization is only important with master master and concurrent > writes. But now it also seems to be important with delta-synrepl. > > So I suppose this ITS can be closed, since it is not a bug, but worked as > designed? > So how to get a good enough time synchronization with windows (since the > normal time synchronization of windows seems to be not enough)? > Of course, if you close the ITS I can ask this question again in the > technical list. > > Regards, > Frank ITS#8295 may be the problem here. Fixed in git master. Please test and followup to that ticket, thanks. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#8294) slappasswd can use SHA256 for hash but not SHA384 or SHA512...segfault
by ktmdms＠gmail.com 28 Oct '15

28 Oct '15

--089e0115ec1091312605232ac99f Content-Type: text/plain; charset=UTF-8 To add fuel to the fire, if I use pw-sha2 libraries that were built on a 2.6 kernel (specifically 2.6.32-358.el6.x86_64) on the 3.18 machine I can generate SHA512/384 hashed passwords with no issues. What should I be looking for between the two platforms that might cause the core? Thanks. Kevin Martin --- Regards, Kevin Martin On Tue, Oct 27, 2015 at 3:11 PM, <openldap-its(a)openldap.org> wrote: > > *** THIS IS AN AUTOMATICALLY GENERATED REPLY *** > > Thanks for your report to the OpenLDAP Issue Tracking System. Your > report has been assigned the tracking number ITS#8294. > > One of our support engineers will look at your report in due course. > Note that this may take some time because our support engineers > are volunteers. They only work on OpenLDAP when they have spare > time. > > If you need to provide additional information in regards to your > issue report, you may do so by replying to this message. Note that > any mail sent to openldap-its(a)openldap.org with (ITS#8294) > in the subject will automatically be attached to the issue report. > > mailto:openldap-its@openldap.org?subject=(ITS#8294) > > You may follow the progress of this report by loading the following > URL in a web browser: > http://www.OpenLDAP.org/its/index.cgi?findid=8294 > > Please remember to retain your issue tracking number (ITS#8294) > on any further messages you send to us regarding this report. If > you don't then you'll just waste our time and yours because we > won't be able to properly track the report. > > Please note that the Issue Tracking System is not intended to > be used to seek help in the proper use of OpenLDAP Software. > Such requests will be closed. > > OpenLDAP Software is user supported. > http://www.OpenLDAP.org/support/ > > -------------- > Copyright 1998-2007 The OpenLDAP Foundation, All Rights Reserved. > > --089e0115ec1091312605232ac99f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">To add fuel to the fire, if I use pw-sha2 libraries that w= ere built on a 2.6 kernel (specifically=C2=A02.6.32-358.el6.x86_64) on the = 3.18 machine I can generate SHA512/384 hashed passwords with no issues.=C2= =A0 What should I be looking for between the two platforms that might cause= the core?<div><br></div><div>Thanks.</div><div><br></div><div>Kevin Martin= </div></div><div class=3D"gmail_extra"><br clear=3D"all"><div><div class=3D= "gmail_signature"><div dir=3D"ltr">---<div><span style=3D"font-size:12.8px"= ><br></span></div><div><span style=3D"font-size:12.8px"><br></span></div><d= iv><span style=3D"font-size:12.8px">Regards,</span></div><div><div><br></di= v><div>Kevin Martin</div></div></div></div></div> <br><div class=3D"gmail_quote">On Tue, Oct 27, 2015 at 3:11 PM, <span dir= =3D"ltr"><<a href=3D"mailto:openldap-its@openldap.org" target=3D"_blank"= >openldap-its(a)openldap.org</a>></span> wrote:<br><blockquote class=3D"gm= ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le= ft:1ex"><br> *** THIS IS AN AUTOMATICALLY GENERATED REPLY ***<br> <br> Thanks for your report to the OpenLDAP Issue Tracking System.=C2=A0 Your<br= > report has been assigned the tracking number ITS#8294.<br> <br> One of our support engineers will look at your report in due course.<br> Note that this may take some time because our support engineers<br> are volunteers.=C2=A0 They only work on OpenLDAP when they have spare<br> time.<br> <br> If you need to provide additional information in regards to your<br> issue report, you may do so by replying to this message.=C2=A0 Note that<br= > any mail sent to <a href=3D"mailto:openldap-its@openldap.org">openldap-its@= openldap.org</a> with (ITS#8294)<br> in the subject will automatically be attached to the issue report.<br> <br> =C2=A0 =C2=A0 =C2=A0 =C2=A0 mailto:<a href=3D"mailto:openldap-its@openldap.= org">openldap-its(a)openldap.org</a>?subject=3D(ITS#8294)<br> <br> You may follow the progress of this report by loading the following<br> URL in a web browser:<br> =C2=A0 =C2=A0 <a href=3D"http://www.OpenLDAP.org/its/index.cgi?findid=3D829= 4" rel=3D"noreferrer" target=3D"_blank">http://www.OpenLDAP.org/its/index.c= gi?findid=3D8294</a><br> <br> Please remember to retain your issue tracking number (ITS#8294)<br> on any further messages you send to us regarding this report.=C2=A0 If<br> you don't then you'll just waste our time and yours because we<br> won't be able to properly track the report.<br> <br> Please note that the Issue Tracking System is not intended to<br> be used to seek help in the proper use of OpenLDAP Software.<br> Such requests will be closed.<br> <br> OpenLDAP Software is user supported.<br> =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"http://www.OpenLDAP.org/support/" re= l=3D"noreferrer" target=3D"_blank">http://www.OpenLDAP.org/support/</a><br> <br> --------------<br> Copyright 1998-2007 The OpenLDAP Foundation, All Rights Reserved.<br> <br> </blockquote></div><br></div> --089e0115ec1091312605232ac99f--

1 0

(ITS#8295) Windows ldap_pvt_gettime is broken
by hyc＠openldap.org 28 Oct '15

28 Oct '15

Full_Name: Howard Chu Version: 2.4 OS: Win32 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (78.155.231.14) Submitted by: hyc ldap_pvt_gettime is used to to generate CSNs with microsecond precision. On Windows it goes thru some gyrations to calculate microseconds since the normal SystemTime only has a resolution of 10-15 milliseconds. Unfortunately it doesn't properly detect when the microsecond counter wraps around back to zero, so it can occasionally return timestamps 1 second in the past.

1 0

(ITS#8294) slappasswd can use SHA256 for hash but not SHA384 or SHA512...segfault
by ktmdms＠gmail.com 27 Oct '15

27 Oct '15

Full_Name: Kevin Martin Version: 2.4.42 OS: 3.8.13-55.1.6.el7uek.x86_64 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (137.254.4.10) Compiled 2.4.42 from source with the following configure options: ./configure --enable-ppolicy --enable-crypt --with-tls --enable-bdb --enable-ldap --enable-slapd --enable-slapi --enable-syslog --enable-modules compiles and installs fine. Built the pw-sha2 contrib module and installed with no problems. The following works fine: /usr/local/sbin/slappasswd -v -v -v -h '{SHA256}' -o module-path=/usr/local/libexec/openldap -o module-load=pw-sha2 -s secret {SHA256}K7gNU3sdo+OL0wNhqoVWhr3g6s1xYv72ol/pe/Unols= /usr/local/sbin/slappasswd -v -v -v -h '{CRYPT}' -c '$6$!4&&.' -s secret {CRYPT}$6$!4&&.$oINsiq8QMkQheQrdy0.qk7qKr7tNVNCX387QMrp8Y/w2y7JcazTvfKhG0mSGIAB1jWZ4xsDbsehH/4yPIns6I. The following create segfaults: /usr/local/sbin/slappasswd -v -v -v -h '{SHA384}' -o module-path=/usr/local/libexec/openldap -o module-load=pw-sha2 -s secret Segmentation fault (core dumped) /usr/local/sbin/slappasswd -v -v -v -h '{SHA512}' -o module-path=/usr/local/libexec/openldap -o module-load=pw-sha2 -s secret Segmentation fault (core dumped) I shouldn't need to use CRYPT with a salt to create a SHA512 hashed password. Bug or something on my machine? Regards, Kevin Martin

1 0

Re: (ITS#8293) ldappasswd error text
by hyc＠symas.com 27 Oct '15

27 Oct '15

samueldarwin(a)yahoo.com wrote: > Full_Name: Sam Darwin > Version: openldap-2.4.31 > OS: Ubuntu 14.04 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (82.169.106.169) > > > Showing informative error messages is very important, especially with complex > software. In this case, the error was misleading, so maybe it can be > updated. > > $ ldappasswd -D "uid=exampleuser,ou=users,dc=example,dc=net"h h ldap01 -W -e > ppolicy > Enter LDAP Password: > Result: Constraint violation (19) > Additional info: Password fails quality checking policy > control: 1.3.6.1.4.1.42.2.27.8.5.1 false MAOBAQY= > ppolicy: error=6 (Password is too short for policy) > > It looks like the password is too short, right? > > Actually, the problem is completely different, which I discovered after some > time. > > -S "uid=exampleuser,ou=users,dc=example,dc=net" should also be added to that > command. > > So, the real error was either that no password at all had been provided, or no > user had been provided, or both. It had not even requested a new password. > The new password was not too short, it was non-existent, which is something else > entirely. > > So, my request is to make the error reporting more sophisticated here, and any > place else that is analogous to this case. make the answer a bit more obvious. Your report is invalid. The ldappasswd(1) manpage clearly states that if you don't provide a new password, the server will be asked to generate one. In this particular case, the password the server generated was too short for your policy. The manpage also states clearly that if you don't specify [user] DN, it will change the password of the user that bound to the server. The error message was correct. Closing this ITS. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

(ITS#8293) ldappasswd error text
by samueldarwin＠yahoo.com 27 Oct '15

27 Oct '15

Full_Name: Sam Darwin Version: openldap-2.4.31 OS: Ubuntu 14.04 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (82.169.106.169) Showing informative error messages is very important, especially with complex software. In this case, the error was misleading, so maybe it can be updated. $ ldappasswd -D "uid=exampleuser,ou=users,dc=example,dc=net"h h ldap01 -W -e ppolicy Enter LDAP Password: Result: Constraint violation (19) Additional info: Password fails quality checking policy control: 1.3.6.1.4.1.42.2.27.8.5.1 false MAOBAQY= ppolicy: error=6 (Password is too short for policy) It looks like the password is too short, right? Actually, the problem is completely different, which I discovered after some time. -S "uid=exampleuser,ou=users,dc=example,dc=net" should also be added to that command. So, the real error was either that no password at all had been provided, or no user had been provided, or both. It had not even requested a new password. The new password was not too short, it was non-existent, which is something else entirely. So, my request is to make the error reporting more sophisticated here, and any place else that is analogous to this case. make the answer a bit more obvious.

1 0

(ITS#8292) Broken option parsing in tests:ldif-filter
by h.b.furuseth＠usit.uio.no 27 Oct '15

27 Oct '15

Full_Name: Hallvard B Furuseth Version: 2.4.42 OS: URL: Submission from: (NULL) (81.191.45.5) Submitted by: hallvard 'tests/progs/ldif-filter -s SPEC' fails if SPEC has no 'BACKEND='. Fixing.

1 0

Re: (ITS#8291) ./run -b hdb test007 fails
by michael＠stroeder.com 27 Oct '15

27 Oct '15

ondra(a)mistotebe.net wrote: > On Tue, Oct 27, 2015 at 08:24:08AM +0000, michael(a)stroeder.com wrote: >> Currently this test fails with git master >> 0d9b8ebe4bfe584e796f683be6203d4a4eb421a2: >> >> michael@nb2:.../openldap/tests> ./run -b hdb test007 >> Cleaning up test run directory leftover from previous run. >> Running ./scripts/test007-slapmodify for hdb... >> running defines.sh >> Running slapadd to build slapd database... >> Testing modify, add, and delete using slapmodify... >> slapmodify failed (1)! >> >> I can provide more logs if needed. > > Yes please. I am curious which modify/delete failed as I can't > reproduce this failure. Strange: testrun/test.out has zero bytes. :-/ But the DB files are created. Other tests with -b hdb seem to work ok. Maybe it's just the test script? $ git status On branch master Your branch is up-to-date with 'origin/master'. nothing to commit, working directory clean Can't see a problem on my side. BTW: It works with mdb though. Ciao, Michael.

1 0

Re: (ITS#8291) ./run -b hdb test007 fails
by ondra＠mistotebe.net 27 Oct '15

27 Oct '15

On Tue, Oct 27, 2015 at 08:24:08AM +0000, michael(a)stroeder.com wrote: > Currently this test fails with git master > 0d9b8ebe4bfe584e796f683be6203d4a4eb421a2: > > michael@nb2:.../openldap/tests> ./run -b hdb test007 > Cleaning up test run directory leftover from previous run. > Running ./scripts/test007-slapmodify for hdb... > running defines.sh > Running slapadd to build slapd database... > Testing modify, add, and delete using slapmodify... > slapmodify failed (1)! > > I can provide more logs if needed. Yes please. I am curious which modify/delete failed as I can't reproduce this failure. Cheers, Ondrej

1 0

(ITS#8291) ./run -b hdb test007 fails
by michael＠stroeder.com 27 Oct '15

27 Oct '15

Full_Name: Michael Str.der Version: master 0d9b8ebe4bfe584e796f683be6203d4a4eb421a2 OS: openSUSE Linux URL: Submission from: (NULL) (213.240.180.113) Currently this test fails with git master 0d9b8ebe4bfe584e796f683be6203d4a4eb421a2: michael@nb2:/usr/src/michael/openldap-git/master/openldap/tests> ./run -b hdb test007 Cleaning up test run directory leftover from previous run. Running ./scripts/test007-slapmodify for hdb... running defines.sh Running slapadd to build slapd database... Testing modify, add, and delete using slapmodify... slapmodify failed (1)! I can provide more logs if needed.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs