Date: Fri, 10 Nov 2006 09:11:34 -0600 From: Eric <heli@mikestammer.com> To: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> Cc: FreeBSD-questions@freebsd.org Subject: Re: NO_OPENSSL= true? Message-ID: <455496A6.2080306@mikestammer.com> In-Reply-To: <44bqnfe4hs.fsf@be-well.ilk.org> References: <45520224.4050002@mikestammer.com> <44bqnfe4hs.fsf@be-well.ilk.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Lowell Gilbert wrote: > Eric <heli@mikestammer.com> writes: > >> No bites on this yesterday. can anyone shed some light on it? > > Most of us assume that one would only use non-standard security > configurations if one *really* knew exactly what one was doing... > >> is this something i should or shouldnt have in my make.conf? >> >> I use openssh-portable-4.4.p1 on my machines and cannot recall when >> NO_OPENSSL= true was added to make.conf. >> >> is this something I should keep in my make.conf? what are the >> implications if i keep it vs removing it? > > Are you getting SSL from a port? If not, you should remove it to get > updates to the base system version. [SSH uses SSL, but doesn't > include its own version; it uses the base or ports version, as > directed by some port makefile logic that I haven't looked through > very carefully.] > thanks for the reply. i have cleaned up the entry for it. again, i dont recall how it ever got there. I use openssh-portable, but everything else is from the base system. maybe it was an artifact from the 5.x days when I did run openssl from the ports tree. Eric
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?455496A6.2080306>