latest 4.0 snapshot breaks tcpdump
I just installed the latest 4.0 snap off of ftp2.freebsd.org. Didn't install the DES libraries... I get this when trying to run tcpdump on the system: unstable# tcpdump /usr/libexec/ld-elf.so.1: Shared object "libcrypto.so.1" not found enjoy -- Jason Garman http://web.wedgie.org/ Student, University of Maryland [EMAIL PROTECTED] From fortune(1): Whois: JAG145 "... Had this been an actual emergency, we would have fled in terror, and you would not have been informed." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: latest 4.0 snapshot breaks tcpdump
On Mon, 13 Mar 2000, Jason Garman wrote: I just installed the latest 4.0 snap off of ftp2.freebsd.org. Didn't install the DES libraries... I get this when trying to run tcpdump on the system: unstable# tcpdump /usr/libexec/ld-elf.so.1: Shared object "libcrypto.so.1" not found Hmm. I think you'll find several other things are broken in the same way - the crypto collection has effectively become mandatory thesedays. For example, ppp and pppd both link against libcrypto as well, and I can't think of an easy way to make the same binary work correctly with and without libcrypto. Either we make a binary which doesn't require libcrypto, in which case there's no way for someone to obtain the full functionality from a binary install, or we make one which does and people have to install the crypto collection to use it. It's a different matter if you compile from source yourself, but with a binary distribution you only have one possible set of binaries and can't mix and match dependencies. IMO (and I suggested this the other day), we should make the crypto collection mandatory, and have sysinstall ask a question about whether to point the libcrypt symlinks at libscrypt or libdescrypt (libdescrypt is the only real reason people wouldn't want to install the crypto collection). Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: latest 4.0 snapshot breaks tcpdump
IMO (and I suggested this the other day), we should make the crypto collection mandatory, and have sysinstall ask a question about whether to point the libcrypt symlinks at libscrypt or libdescrypt (libdescrypt is I'm still waiting for your diffs which do this. :) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: latest 4.0 snapshot breaks tcpdump
On Mon, 13 Mar 2000, Jordan K. Hubbard wrote: IMO (and I suggested this the other day), we should make the crypto collection mandatory, and have sysinstall ask a question about whether to point the libcrypt symlinks at libscrypt or libdescrypt (libdescrypt is I'm still waiting for your diffs which do this. :) Well yeah, that's fun to say, but my days have been literally completely full with getting other things ready for 4.0, without trying to figure out sysinstall on top of it all. All I can do is warn you to expect bug reports about this once people start upgrading to 4.0. Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: latest 4.0 snapshot breaks tcpdump
IMO (and I suggested this the other day), we should make the crypto collection mandatory, and have sysinstall ask a question about whether to point the libcrypt symlinks at libscrypt or libdescrypt (libdescrypt is I'm still waiting for your diffs which do this. :) Well yeah, that's fun to say, but my days have been literally completely full with getting other things ready for 4.0, without trying to figure out sysinstall on top of it all. All I can do is warn you to expect bug reports about this once people start upgrading to 4.0. Can't it be handled the same way init, ppp and a few others are? The binary shipped in the bin distribution is compiled/linked without crypto, but then a version compiled/linked with it is included in the crypto distribution. John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: latest 4.0 snapshot breaks tcpdump
On Mon, 13 Mar 2000, John Hay wrote: Can't it be handled the same way init, ppp and a few others are? The binary shipped in the bin distribution is compiled/linked without crypto, but then a version compiled/linked with it is included in the crypto distribution. Hmm. I didn't know that - probably it could. The question is then whether make release correctly compiles everything without libcrypto (the original poster suggests not). Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: latest 4.0 snapshot breaks tcpdump
On Mon, 13 Mar 2000, Kris Kennaway wrote:
Hmm. I didn't know that - probably it could. The question is then whether
make release correctly compiles everything without libcrypto (the original
poster suggests not).
Looks like it needs the following patch:
Index: usr.sbin/tcpdump//tcpdump/Makefile
===
RCS file: /home/ncvs/src/usr.sbin/tcpdump/tcpdump/Makefile,v
retrieving revision 1.25
diff -u -r1.25 Makefile
--- usr.sbin/tcpdump//tcpdump/Makefile 2000/03/02 13:27:25 1.25
+++ usr.sbin/tcpdump//tcpdump/Makefile 2000/03/13 10:54:05
@@ -21,7 +21,7 @@
CLEANFILES+= version.c
DPADD+=${LIBL} ${LIBPCAP}
LDADD+=-ll -lpcap
-.if exists(../../../crypto) !defined(NOSECURE) !defined(NO_OPENSSL)
+.if exists(../../../crypto) !defined(NOCRYPT) !defined(NOSECURE)
+!defined(NO_OPENSSL) !defined(RELEASE_CRUNCH)
DPADD+= ${LIBCRYPTO}
LDADD+= -lcrypto
CFLAGS+= -I${DESTDIR}/usr/include/openssl -DCRYPTO -DHAVE_LIBCRYPTO -DHAVE_RC5_H
-DHAVE_CAST_H
In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: latest 4.0 snapshot breaks tcpdump
It also needs DISTRIBUTION=crypto inside that .if so that it will end up
in the crypto distribution. And maybe the exists(../../../crypto should
be exists(${.CURDIR}/../../secure) like the ppp/Makefile?
Hmm. I didn't know that - probably it could. The question is then whether
make release correctly compiles everything without libcrypto (the original
poster suggests not).
Looks like it needs the following patch:
Index: usr.sbin/tcpdump//tcpdump/Makefile
===
RCS file: /home/ncvs/src/usr.sbin/tcpdump/tcpdump/Makefile,v
retrieving revision 1.25
diff -u -r1.25 Makefile
--- usr.sbin/tcpdump//tcpdump/Makefile2000/03/02 13:27:25 1.25
+++ usr.sbin/tcpdump//tcpdump/Makefile2000/03/13 10:54:05
@@ -21,7 +21,7 @@
CLEANFILES+= version.c
DPADD+= ${LIBL} ${LIBPCAP}
LDADD+= -ll -lpcap
-.if exists(../../../crypto) !defined(NOSECURE) !defined(NO_OPENSSL)
+.if exists(../../../crypto) !defined(NOCRYPT) !defined(NOSECURE)
!defined(NO_OPENSSL) !defined(RELEASE_CRUNCH)
DPADD+= ${LIBCRYPTO}
LDADD+= -lcrypto
CFLAGS+= -I${DESTDIR}/usr/include/openssl -DCRYPTO -DHAVE_LIBCRYPTO -DHAVE_RC5_H
-DHAVE_CAST_H
In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe [EMAIL PROTECTED]
John
--
John Hay -- [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: latest 4.0 snapshot breaks tcpdump
Well yeah, that's fun to say, but my days have been literally completely full with getting other things ready for 4.0. And you think mine haven't been? :) My point is simply that I'm going to need a lot more than rough suggestions at this point if people want to help. I don't have time to go implement all these little ideas myself. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
