Date: Thu, 17 Apr 2003 21:34:40 +0100 From: "Andy Gilligan" <andy@evo6.org> To: "Doug Silver" <dsilver@urchin.com> Cc: stable@freebsd.org Subject: Re: Problem logging in after upgrade to 4.8-Stable Message-ID: <001e01c30520$c57b4b70$0a00000a@vx> References: <200304151126.21202.dsilver@urchin.com><200304151618.21167.dsilver@urchin.com> <20030415204211.I6307@shell.inch.com> <200304171232.48652.dsilver@urchin.com>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message ----- From: "Doug Silver" <dsilver@urchin.com> To: "Charles Sprickman" <spork@inch.com> Cc: <stable@freebsd.org> Sent: Thursday, April 17, 2003 8:33 PM Subject: Re: Problem logging in after upgrade to 4.8-Stable <snip> > libcrypto is part of the openssl port, perhaps you're thinking of libcrypt? > > I just figured out where I shot myself in the foot ;\ In my attempt to strip > out libcrypto/libssl out of the build process I commented in "NOSECURE" and > "NOCRYPTO" in /etc/make.conf -- and to ensure it, I removed the source. So, > that is clearly the wrong thing to do. Is the preferred method, if I simply > want to ensure that libcrypto and libssl are used from the openssl port, to > remove & symlink them in /usr/lib? BTW -- I'm not concerned with the few > binaries in the base system that are linked against these libs (e.g. > pkg_sign, pkg_check). > > Or, is this a Pandora's box that I just shouldn't open (assuming the ports > system recognizes the various "OPENSSL" settings in /etc/make.conf)? > > -doug In /etc/make.conf, you might want to set: OPENSSL_OVERWRITE_BASE= true Then build and install /usr/ports/security/openssl as normal. This should replace openssl in the base system with the port version. Andy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001e01c30520$c57b4b70$0a00000a>