Problem logging in after upgrade to 4.8-Stable
andy at evo6.org
Thu Apr 17 13:34:54 PDT 2003
----- Original Message -----
From: "Doug Silver" <dsilver at urchin.com>
To: "Charles Sprickman" <spork at inch.com>
Cc: <stable at freebsd.org>
Sent: Thursday, April 17, 2003 8:33 PM
Subject: Re: Problem logging in after upgrade to 4.8-Stable
> libcrypto is part of the openssl port, perhaps you're thinking of
> I just figured out where I shot myself in the foot ;\ In my attempt to
> out libcrypto/libssl out of the build process I commented in "NOSECURE"
> "NOCRYPTO" in /etc/make.conf -- and to ensure it, I removed the source.
> that is clearly the wrong thing to do. Is the preferred method, if I
> want to ensure that libcrypto and libssl are used from the openssl port,
> 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)?
In /etc/make.conf, you might want to set:
Then build and install /usr/ports/security/openssl as normal.
This should replace openssl in the base system with
the port version.
More information about the freebsd-stable