- openldap-bugs - openldap.org

Re: (ITS#5534) Samba4 needs internal transactions/consistancy
by hyc＠symas.com 28 May '08

28 May '08

Andrew Bartlett wrote: > On Tue, 2008-05-27 at 18:43 -0700, Howard Chu wrote: >> Andrew Bartlett wrote: >>> On Tue, 2008-05-27 at 18:22 -0700, Howard Chu wrote: >>>>> This needs to occur even between databases on the server, but I won't ask that >>>>> it occur outside the known trees. >>>> It's already possible for operations in one database to reference entries in a >>>> different database, so that aspect of validation should be fine. However, as >>>> noted before, "validation" is generally bogus to begin with. In particular, >>>> how do you create entries with circular references? If you disallow references >>>> to nonexistent entries, you can't set the references until after all of the >>>> entries have been created. This means that you cannot backup a database that >>>> has these references and then later reload it in a single pass. >>> An interesting point, but I need to match the windows runtime >>> behaviour. >> Only when it has a visible impact on other clients. What software will break >> if the directory allows you to add new entries that contain dangling >> references? What will break if the directory allows you to modify a reference >> attribute to point to a nonexistent entry? > > Sure, I'm not asking for a change to default behaviours. I'm listing > the things that our testsuite finds are differences, and looking for > solutions. I don't believe your proposed solution will ever be satisfactory. Entries with circular references will also break syncrepl Refresh if the constraint you're asking for is enforced. That will clearly have visible impact in many deployments. If the only thing that complains with the current behavior is your testsuite and not any real world clients, I suggest you just note the difference and move on. >> There's a lot of Windows behavior that is clearly wrong, by any number of >> metrics. You need to be a bit more selective in prioritizing the list of >> things to chase down. > > This is the currently the top priority for an LDAP Backend for Samba4. -- -- 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#5535) smbk5pwd uses private heimdal functions
by Guillaume.Rousse＠inria.fr 28 May '08

28 May '08

Full_Name: Guillaume Rousse Version: 2.4.8 OS: linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (193.55.250.67) smbk5pwd uses two private heimdal functions: _kadm5_set_keys _kadm5_free_keys As of heimdal 1.1, those functions are not exported anymore. As a consequence, opendalp crashes as soon as I try to change password when the overlay is activated. According to heimdal maintainers, smb5pwd should rather use hdb_generate_key_set_password and hdb_free_keys to generate the key data. I tried to produce a patch myself (available at http://www.zarb.org/~guillomovitch/openldap-smbk5pwd-2.4.8-dont-use-interna…) by inlining _kadm5_set_keys function directly in smbk5pwd, but I don't know how to deal with members of private kadm_context structure.

1 0

Re: (ITS#5534) Samba4 needs internal transactions/consistancy
by abartlet＠samba.org 27 May '08

27 May '08

--=-s2sha8beM9nUssvA07HS Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2008-05-27 at 18:43 -0700, Howard Chu wrote: > Andrew Bartlett wrote: > > On Tue, 2008-05-27 at 18:22 -0700, Howard Chu wrote: >=20 > >>> This needs to occur even between databases on the server, but I won't= ask that > >>> it occur outside the known trees. > >> It's already possible for operations in one database to reference entr= ies in a > >> different database, so that aspect of validation should be fine. Howev= er, as > >> noted before, "validation" is generally bogus to begin with. In partic= ular, > >> how do you create entries with circular references? If you disallow re= ferences > >> to nonexistent entries, you can't set the references until after all o= f the > >> entries have been created. This means that you cannot backup a databas= e that > >> has these references and then later reload it in a single pass. > > > > An interesting point, but I need to match the windows runtime > > behaviour. >=20 > Only when it has a visible impact on other clients. What software will br= eak=20 > if the directory allows you to add new entries that contain dangling=20 > references? What will break if the directory allows you to modify a refer= ence=20 > attribute to point to a nonexistent entry? Sure, I'm not asking for a change to default behaviours. I'm listing the things that our testsuite finds are differences, and looking for solutions.=20 > There's a lot of Windows behavior that is clearly wrong, by any number of= =20 > metrics. You need to be a bit more selective in prioritizing the list of=20 > things to chase down. This is the currently the top priority for an LDAP Backend for Samba4. =20 Andrew Bartlett --=20 Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Red Hat Inc. --=-s2sha8beM9nUssvA07HS Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQBIPMMwz4A8Wyi0NrsRAljCAJsEsn1tsq4BdkdenNOEOF3PIGcDDACfVoUR APoU1kbv2ljwVBgjyhPbyGQ= =mXBr -----END PGP SIGNATURE----- --=-s2sha8beM9nUssvA07HS--

1 0

Re: (ITS#5534) Samba4 needs internal transactions/consistancy
by hyc＠symas.com 27 May '08

27 May '08

Andrew Bartlett wrote: > On Tue, 2008-05-27 at 18:22 -0700, Howard Chu wrote: >>> This needs to occur even between databases on the server, but I won't ask that >>> it occur outside the known trees. >> It's already possible for operations in one database to reference entries in a >> different database, so that aspect of validation should be fine. However, as >> noted before, "validation" is generally bogus to begin with. In particular, >> how do you create entries with circular references? If you disallow references >> to nonexistent entries, you can't set the references until after all of the >> entries have been created. This means that you cannot backup a database that >> has these references and then later reload it in a single pass. > > An interesting point, but I need to match the windows runtime > behaviour. Only when it has a visible impact on other clients. What software will break if the directory allows you to add new entries that contain dangling references? What will break if the directory allows you to modify a reference attribute to point to a nonexistent entry? There's a lot of Windows behavior that is clearly wrong, by any number of metrics. You need to be a bit more selective in prioritizing the list of things to chase down. -- -- 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#5534) Samba4 needs internal transactions/consistancy
by abartlet＠samba.org 27 May '08

27 May '08

--=-I6d9E5fOqbwKcJhhvz+z Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2008-05-27 at 18:22 -0700, Howard Chu wrote: > abartlet(a)samba.org wrote: > > Full_Name: Andrew Bartlett > > Version: CVS HEAD > > OS: Fedora 9 > > URL: http://www.openldap.org/lists/openldap-technical/200803/msg00101.h= tml > > Submission from: (NULL) (59.167.251.137) > > > > > > For Samba4, I need a few things, detailed in the attached URL. >=20 > The above message thread had some unanswered questions. We may need to ha= ve=20 > each point listed out again. >=20 > > This ITS is for internal transactions and validation - the ability to h= ave a > > openldap overlay roll back all the changes so far, because a preconditi= on is not > > met. >=20 > I think this one is understood, OK. Just a matter of getting the time to = do it. >=20 > > I need the memberOf and refint modules to ensure that no dangling links= ever > > exist, even over subtree renames and invalid modifies, and that a trans= action > > ensures this is always the case. >=20 > I think the proper use of memberOf still needs to be addressed. E.g., it'= s=20 > generally a bad idea to search for (memberOf=3Dfoo) when you can simply=20 > enumerate the members inside the "foo" entry. If you give us precise exam= ples=20 > of the searches and modifications that you'll be using, we may be able to= =20 > narrow the scope of this work. I'll be passing on any search that a windows client makes, and trying to return the same result a windows server would return. Bad ideas still have to be implemented in my world :-( > > This needs to occur even between databases on the server, but I won't a= sk that > > it occur outside the known trees. >=20 > It's already possible for operations in one database to reference entries= in a=20 > different database, so that aspect of validation should be fine. However,= as=20 > noted before, "validation" is generally bogus to begin with. In particula= r,=20 > how do you create entries with circular references? If you disallow refer= ences=20 > to nonexistent entries, you can't set the references until after all of t= he=20 > entries have been created. This means that you cannot backup a database t= hat=20 > has these references and then later reload it in a single pass. An interesting point, but I need to match the windows runtime behaviour.=20 Andrew Bartlett --=20 Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Red Hat Inc. --=-I6d9E5fOqbwKcJhhvz+z Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQBIPLXqz4A8Wyi0NrsRArp6AJ9OaJP8Cu4MdO69n1k1S8vlBjtPOACdHvDh t0XbDQzXaJya2LR/bhl1RlQ= =/FnH -----END PGP SIGNATURE----- --=-I6d9E5fOqbwKcJhhvz+z--

1 0

Re: (ITS#5534) Samba4 needs internal transactions/consistancy
by hyc＠symas.com 27 May '08

27 May '08

abartlet(a)samba.org wrote: > Full_Name: Andrew Bartlett > Version: CVS HEAD > OS: Fedora 9 > URL: http://www.openldap.org/lists/openldap-technical/200803/msg00101.html > Submission from: (NULL) (59.167.251.137) > > > For Samba4, I need a few things, detailed in the attached URL. The above message thread had some unanswered questions. We may need to have each point listed out again. > This ITS is for internal transactions and validation - the ability to have a > openldap overlay roll back all the changes so far, because a precondition is not > met. I think this one is understood, OK. Just a matter of getting the time to do it. > I need the memberOf and refint modules to ensure that no dangling links ever > exist, even over subtree renames and invalid modifies, and that a transaction > ensures this is always the case. I think the proper use of memberOf still needs to be addressed. E.g., it's generally a bad idea to search for (memberOf=foo) when you can simply enumerate the members inside the "foo" entry. If you give us precise examples of the searches and modifications that you'll be using, we may be able to narrow the scope of this work. > This needs to occur even between databases on the server, but I won't ask that > it occur outside the known trees. It's already possible for operations in one database to reference entries in a different database, so that aspect of validation should be fine. However, as noted before, "validation" is generally bogus to begin with. In particular, how do you create entries with circular references? If you disallow references to nonexistent entries, you can't set the references until after all of the entries have been created. This means that you cannot backup a database that has these references and then later reload it in a single pass. -- -- 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#5534) Samba4 needs internal transactions/consistancy
by abartlet＠samba.org 27 May '08

27 May '08

Full_Name: Andrew Bartlett Version: CVS HEAD OS: Fedora 9 URL: http://www.openldap.org/lists/openldap-technical/200803/msg00101.html Submission from: (NULL) (59.167.251.137) For Samba4, I need a few things, detailed in the attached URL. This ITS is for internal transactions and validation - the ability to have a openldap overlay roll back all the changes so far, because a precondition is not met. I need the memberOf and refint modules to ensure that no dangling links ever exist, even over subtree renames and invalid modifies, and that a transaction ensures this is always the case. This needs to occur even between databases on the server, but I won't ask that it occur outside the known trees.

1 0

Re: (ITS#5318) response msgid <= 0 mishandled in libldap
by hyc＠symas.com 27 May '08

27 May '08

h.b.furuseth(a)usit.uio.no wrote: > Full_Name: Hallvard B Furuseth > Version: HEAD > OS: > URL: > Submission from: (NULL) (129.240.6.233) > Submitted by: hallvard > > > libraries/libldap/result.c:try_read1msg() accesses 'lr' uninitialized > if 'id' (message ID) from line 577's 'ber_get_int( ber,&id )' is<= 0. > > I'm not sure if the client should terminate the connection when it > receives message id< 0, or if it should just toss the response like > it does with unknown message IDs. RFC4511 isn't really explicit here, although it does say that the connection should be dropped for unparsable messages. Anyway, I've patched HEAD to toss the messages for now. > With message ID 0, the code reaches this statement with 'lr' uninitialized: > Debug( LDAP_DEBUG_TRACE, > "read1msg: ld %p msgid %ld message type %s\n", > (void *)ld, (long)lr->lr_msgid, ldap_int_msgtype2str( tag ) ); > As far as I can tell, normally lr->lr_msgid == id. I haven't tracked what > those values are with LDAP_CONNECTIONLESS at the 'nextresp2:' label. For CONNECTIONLESS, it can only jump back there because there were multiple responses to the current request. So the lr is the same as for the first response. No problem there. (Remember this is all within a single datagram. Responses to multiple different requests cannot be interleaved at this point.) > A 700-line function with 5 labels, yuck. > Anyway, I wonder why taht statement and the statement below: > if ( id == 0 ) { > doesn't use the same value, either id or lr->lr_msgid for both. -- -- 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#5533) test035-meta crashes --without-threads
by h.b.furuseth＠usit.uio.no 27 May '08

27 May '08

quanah(a)zimbra.com writes: > Isn't this just a duplicate of ITS#5489? Apparently not. Got it again at 4th run with daemon.c 1.380.2.12. Also in a somewhat patched HEAD with the same configuration. Hm, the crashes happen for extended operations. So far 6 times "Passwd ExOp failed (1)!", once "WhoAmI failed (49)!". -- Hallvard

1 0

Re: (ITS#5533) test035-meta crashes --without-threads
by quanah＠zimbra.com 27 May '08

27 May '08

--On Tuesday, May 27, 2008 8:05 PM +0000 h.b.furuseth(a)usit.uio.no wrote: > Full_Name: Hallvard B Furuseth > Version: RE24 > OS: > URL: ftp://ftp.openldap.org/incoming/Hallvard-Furuseth-080527.tgz.1 > Submission from: (NULL) (129.240.6.233) > Submitted by: hallvard > Isn't this just a duplicate of ITS#5489? --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

(ITS#5533) test035-meta crashes --without-threads
by h.b.furuseth＠usit.uio.no 27 May '08

27 May '08

Full_Name: Hallvard B Furuseth Version: RE24 OS: URL: ftp://ftp.openldap.org/incoming/Hallvard-Furuseth-080527.tgz.1 Submission from: (NULL) (129.240.6.233) Submitted by: hallvard slapd crashes in test035 after 10 runs: daemon.c:979: assert( SLAP_SOCK_IS_ACTIVE( s )); RE24 + libraries/libldap_r/thr_stub.c rev 1.35 ./configure --quiet --without-threads --enable-meta --enable-ldap 'CFLAGS=-O0 -g' (declare -i n=0; while n=n+1 && echo "run #$n" && ./run test035; do sleep 5; done) Testrun directory enclosed, with files OUTPUT (from tty) and slapd.*.GDB. Removed database directories though. (Argh, I messed up with passive mode again. Oh well.)

1 0

Re: (ITS#5524) Additions to the Security section of the Admin Guide
by ghenry＠OpenLDAP.org 27 May '08

27 May '08

<quote who="Kurt(a)OpenLDAP.org"> > > On May 26, 2008, at 12:48 PM, andrew.findlay(a)skills-1st.co.uk wrote: > >> On Mon, May 26, 2008 at 01:07:22PM +0100, Gavin Henry wrote: >> >>> I've patched security.sdf and I'm abotu to clean up some typos and >>> formating. >> >> Thanks. >> >>> Should we also mention that CRYPT is platform specific? >> >> I put in a note about the glibc2 version, but I was not aware of any >> platform oddities on the traditional 13-character version. Are there >> other MD5 variants? >> >> We could also mention the LANMAN scheme which I forgot to include as >> it is a compile-time option. >> >>> Lastly, should I also put: >>> >>> Portions Copyright 2008 Andrew Findlay <andrew.findlay(a)skills-1st.co.uk >>> > >>> >>> into doc/guide/COPYRIGHT ? > > No. > > This file is a copy of the main OpenLDAP Software COPYRIGHT file. > That file is intended to contain notices of copyright holders which > hold signfiicant rights in OpenLDAP Software. Notices for copyright > holders, as noted in the COPYRIGHT file, are generally to be placed in > the individual source files which the holder holds significant rights > in. That is, this notice belongs in security.sdf itself. I have so > updated the source documents. Good, this clears things up and make it clear going forward. Thanks. > Though the preface does clearly say that admin guide is part of > OpenLDAP Software, I've also updated the preface to note that portions > of the document may be copyright by others as indicated in source files. Thanks again.

1 0

Re: (ITS#5529) test048-syncrepl-multiproxy --without-threads hangs
by h.b.furuseth＠usit.uio.no 27 May '08

27 May '08

ando(a)sys-net.it writes: >h.b.furuseth(a)usit.uio.no wrote: >> RE24 configured with --quiet --without-threads --enable-ldap 'CFLAGS=-O0 -g' Sorry, that's RE24 + the ITS#5519 (--without-thread miscompiles) patch: cvs diff -r1.34 -r1.35 -I'[$]OpenLDAP[$:]' libraries/libldap_r/thr_stub.c > Probably, sync replication should not be allowed when building > --without-threads. Or there could be a warning that --without-threads breaks some features. Looking closer I see the server replicates from itself in this test. I can see how that'd be a problem in single-threaded mode... Most other syncrepl tests succeed. Though test050 crashes: daemon.c:979: slapd_set_read: Assertion `((slap_daemon.sd_index[(s)]) != -1)' failed. (Argh, it refuses to dump core for some reason. I've done ulimit -c unlimited and put it in defines.sh too.) -- Hallvard

1 0

Re: (ITS#5524) Additions to the Security section of the Admin Guide
by Kurt＠OpenLDAP.org 27 May '08

27 May '08

On May 26, 2008, at 12:48 PM, andrew.findlay(a)skills-1st.co.uk wrote: > On Mon, May 26, 2008 at 01:07:22PM +0100, Gavin Henry wrote: > >> I've patched security.sdf and I'm abotu to clean up some typos and >> formating. > > Thanks. > >> Should we also mention that CRYPT is platform specific? > > I put in a note about the glibc2 version, but I was not aware of any > platform oddities on the traditional 13-character version. Are there > other MD5 variants? > > We could also mention the LANMAN scheme which I forgot to include as > it is a compile-time option. > >> Lastly, should I also put: >> >> Portions Copyright 2008 Andrew Findlay <andrew.findlay(a)skills-1st.co.uk >> > >> >> into doc/guide/COPYRIGHT ? No. This file is a copy of the main OpenLDAP Software COPYRIGHT file. That file is intended to contain notices of copyright holders which hold signfiicant rights in OpenLDAP Software. Notices for copyright holders, as noted in the COPYRIGHT file, are generally to be placed in the individual source files which the holder holds significant rights in. That is, this notice belongs in security.sdf itself. I have so updated the source documents. Though the preface does clearly say that admin guide is part of OpenLDAP Software, I've also updated the preface to note that portions of the document may be copyright by others as indicated in source files. -- Kurt

1 0

(ITS#5532) incorrect timestamp of slapd replica log
by hai.zhao＠gmail.com 27 May '08

27 May '08

Full_Name: Zhao Hai Version: 2.3.41 OS: Linux 2.4.21 arm URL: ftp://ftp.openldap.org/incoming/zhaohai-080527.patch Submission from: (NULL) (205.209.140.4) Problem: race condition makes incorrect timestamp in replogfile, cause certain modification of entries not replicate to slurp slaves. replica: 180.0.10.2:1234 replica: 180.0.10.3:1234 time: 1211855467 ^^^^^^^^^^ this timestamp How to reproduce the problem: 1) run under very slow machines (my environ: arm 266MHz) 2) slapd is configed to generate replogfile 3) ldapadd about 5 entries, then ldapmodify 2 entries without delay. Patch: Please look the attached patch. It works for me.

1 0

Re: (ITS#5530) OpenLDAP fails to compile
by hyc＠symas.com 26 May '08

26 May '08

mike(a)tedder.cc wrote: > Full_Name: Mike Tedder > Version: 2.4.9 > OS: powerpc-linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (210.170.158.22) > > > The back-bdb backend for the OpenLDAP slapd server fails to compile when being > built using Berkeley DB 4.7: This was already reported in ITS#5523. -- -- 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#5524) Additions to the Security section of the Admin Guide
by ghenry＠OpenLDAP.org 26 May '08

26 May '08

<quote who="Andrew Findlay"> > On Mon, May 26, 2008 at 01:07:22PM +0100, Gavin Henry wrote: > >> I've patched security.sdf and I'm abotu to clean up some typos and >> formating. > > Thanks. > >> Should we also mention that CRYPT is platform specific? > > I put in a note about the glibc2 version, but I was not aware of any > platform oddities on the traditional 13-character version. Are there > other MD5 variants? See http://www.openldap.org/faq/index.cgi?_highlightWords=crypt&file=344 > > We could also mention the LANMAN scheme which I forgot to include as > it is a compile-time option. Sure, could do. > >> Lastly, should I also put: >> >> Portions Copyright 2008 Andrew Findlay <andrew.findlay(a)skills-1st.co.uk> >> >> into doc/guide/COPYRIGHT ? > > Yes please. Done. Check in HEAD -- Kind Regards, Gavin Henry. OpenLDAP Engineering Team. E ghenry(a)OpenLDAP.org Community developed LDAP software. http://www.openldap.org/project/

1 0

Re: (ITS#5524) Additions to the Security section of the Admin Guide
by andrew.findlay＠skills-1st.co.uk 26 May '08

26 May '08

On Mon, May 26, 2008 at 01:07:22PM +0100, Gavin Henry wrote: > I've patched security.sdf and I'm abotu to clean up some typos and > formating. Thanks. > Should we also mention that CRYPT is platform specific? I put in a note about the glibc2 version, but I was not aware of any platform oddities on the traditional 13-character version. Are there other MD5 variants? We could also mention the LANMAN scheme which I forgot to include as it is a compile-time option. > Lastly, should I also put: > > Portions Copyright 2008 Andrew Findlay <andrew.findlay(a)skills-1st.co.uk> > > into doc/guide/COPYRIGHT ? Yes please. Andrew -- ----------------------------------------------------------------------- | From Andrew Findlay, Skills 1st Ltd | | Consultant in large-scale systems, networks, and directory services | | http://www.skills-1st.co.uk/ +44 1628 782565 | -----------------------------------------------------------------------

1 0

Re: (ITS#5531) Use MAXPATHLEN, not PATH_MAX
by ando＠sys-net.it 26 May '08

26 May '08

rra(a)debian.org wrote: > servers/slapd/back-bdb/monitor.c uses PATH_MAX rather than MAXPATHLEN. GNU Hurd > doesn't have PATH_MAX. OpenLDAP defines MAXPATHLEN portably, so that should be > used instead. Here is the trivial patch: That portion of code was moved to back-bdb from back-monitor/database.c, where PATH_MAX was (naively) redefined. Thanks for spotting it. It is now fixed in HEAD, re24 and re23. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

(ITS#5531) Use MAXPATHLEN, not PATH_MAX
by rra＠debian.org 26 May '08

26 May '08

Full_Name: Russ Allbery Version: 2.4.9 OS: Debian GNU/Linux URL: Submission from: (NULL) (171.66.157.16) servers/slapd/back-bdb/monitor.c uses PATH_MAX rather than MAXPATHLEN. GNU Hurd doesn't have PATH_MAX. OpenLDAP defines MAXPATHLEN portably, so that should be used instead. Here is the trivial patch: --- openldap.orig/servers/slapd/back-bdb/monitor.c +++ openldap/servers/slapd/back-bdb/monitor.c @@ -395,7 +395,7 @@ { struct berval bv, nbv; ber_len_t pathlen = 0, len = 0; - char path[ PATH_MAX ] = { '\0' }; + char path[ MAXPATHLEN ] = { '\0' }; char *fname = bdb->bi_dbenv_home, *ptr; This is http://bugs.debian.org/475744

1 0

Re: (ITS#5530) OpenLDAP fails to compile
by mike＠tedder.cc 26 May '08

26 May '08

On Tue, 27 May 2008 03:15:09 +0900, Pierangelo Masarati <ando(a)sys-net.it> wrote: > mike(a)tedder.cc wrote: > >> The back-bdb backend for the OpenLDAP slapd server fails to compile >> when being >> built using Berkeley DB 4.7: > > Berkeley DB 4.7 is not supported (yet). That would explain why. :) I will downgrade to 4.6.21. Thanks for the quick response!

1 0

Re: (ITS#5529) test048-syncrepl-multiproxy --without-threads hangs
by ando＠sys-net.it 26 May '08

26 May '08

h.b.furuseth(a)usit.uio.no wrote: > Full_Name: Hallvard B Furuseth > Version: HEAD, RE24 > OS: Linux > URL: ftp://ftp.openldap.org/incoming/Hallvard-Furuseth-080526.tgz.1 > Submission from: (NULL) (129.240.6.233) > Submitted by: hallvard > > > RE24 configured with --quiet --without-threads --enable-ldap 'CFLAGS=-O0 -g' > > $ ./run test048 > Cleaning up test run directory leftover from previous run. > Running ./scripts/test048-syncrepl-multiproxy... > running defines.sh > Starting master slapd on TCP/IP port 9011... > Using ldapsearch to check that master slapd is running... > > gdb shows both slapd and ldapsearch waiting in poll(). > testrun with backtraces enclosed. Probably, sync replication should not be allowed when building --without-threads. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

Re: (ITS#5528) Problem compiling openldap 2.4.9
by rra＠stanford.edu 26 May '08

26 May '08

pierre42d(a)9online.fr writes: > /bin/sh ../..//libtool --mode=link gcc -s -O3 -march=i686 > -L/usr/local/BerkeleyDB.4.6/lib -o apitest apitest.o libldap.la > ../../libraries/liblber/liblber.la ../../libraries/liblutil/liblutil.a -lsasl2 > -lgnutls -lcrypt -lresolv > gcc -s -O3 -march=i686 -o .libs/apitest apitest.o > -L/usr/local/BerkeleyDB.4.6/lib ./.libs/libldap.so > /tmp/openldap-2.4.9/libraries/liblber/.libs/liblber.so -L/usr/local/lib > ../../libraries/liblber/.libs/liblber.so ../../libraries/liblutil/liblutil.a > /usr/local/lib/libsasl2.so -ldl /usr/local/lib/libgnutls.so > /usr/local/lib/libtasn1.so /usr/local/lib/libgcrypt.so -lnsl -lcap > /usr/local/lib/libgpg-error.so -lz -lcrypt -lresolv > ./.libs/libldap.so: undefined reference to `gnutls_cipher_suite_info' What version of GnuTLS do you have installed? I wonder if the one you have is too old. -- Russ Allbery (rra(a)stanford.edu) <http://www.eyrie.org/~eagle/>

1 0

Re: (ITS#5530) OpenLDAP fails to compile
by ando＠sys-net.it 26 May '08

26 May '08

mike(a)tedder.cc wrote: > The back-bdb backend for the OpenLDAP slapd server fails to compile when being > built using Berkeley DB 4.7: Berkeley DB 4.7 is not supported (yet). p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

(ITS#5530) OpenLDAP fails to compile
by mike＠tedder.cc 26 May '08

26 May '08

Full_Name: Mike Tedder Version: 2.4.9 OS: powerpc-linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (210.170.158.22) The back-bdb backend for the OpenLDAP slapd server fails to compile when being built using Berkeley DB 4.7: cd back-bdb; make -w all make[3]: Entering directory `/mnt/home/bpoint/src/openldap-2.4.9/servers/slapd/back-bdb' rm -f version.c ../../../build/mkversion -v "2.4.9" back_bdb > version.c /bin/sh ../../..//libtool --tag=disable-shared --mode=compile cc -g -O2 -I../../../include -I../../../include -I.. -I./.. -c init.c cc -g -O2 -I../../../include -I../../../include -I.. -I./.. -c init.c -o init.o init.c: In function `bdb_db_open': init.c:509: error: structure has no member named `lk_handle' init.c: In function `bdb_back_initialize': init.c:752: warning: passing arg 1 of `db_env_set_func_yield' from incompatible pointer type make[3]: *** [init.lo] Error 1 make[3]: Leaving directory `/mnt/home/bpoint/src/openldap-2.4.9/servers/slapd/back-bdb' make[2]: *** [.backend] Error 1 make[2]: Leaving directory `/mnt/home/bpoint/src/openldap-2.4.9/servers/slapd' make[1]: *** [all-common] Error 1 make[1]: Leaving directory `/mnt/home/bpoint/src/openldap-2.4.9/servers' make: *** [all-common] Error 1 The reason for this error is because there is no longer a "lk_handle" member inside the DB_ENV structure in /usr/include/db.h. I checked the mailing list archives, and there's not a sign of anyone having this compile error anywhere. I also checked the HEAD revision in CVS, and init.c still uses the lk_handle member variable. I guess no one's upgraded to Berkeley 4.7 yet...? :) To work around the compile error, I have changed: #if DB_VERSION_FULL >= 0x04060012 ...to... #if 0 && DB_VERSION_FULL >= 0x04060012 in all places in init.c and cache.c (the only two files affected), and slapd compiles successfully. I'm not sure if this is the proper way to fix it or not, however...

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs