Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 06 Mar 2000 11:39:44 +0200
From:      Mark Murray <mark@grondar.za>
To:        Kris Kennaway <kris@hub.freebsd.org>
Cc:        current@freebsd.org, markm@freebsd.org, jkh@freebsd.org
Subject:   Re: NO_OPENSSL world fixes 
Message-ID:  <200003060939.LAA43479@grimreaper.grondar.za>
In-Reply-To: <Pine.BSF.4.21.0003051635130.71965-100000@hub.freebsd.org> ; from Kris Kennaway <kris@hub.freebsd.org>  "Sun, 05 Mar 2000 16:59:07 PST."
References:  <Pine.BSF.4.21.0003051635130.71965-100000@hub.freebsd.org> 

next in thread | previous in thread | raw e-mail | index | archive | help
> Okay, these patches were sufficient to allow me to build world with
> NO_OPENSSL defined. I'd like to commit these ASAP.

No objections.

> After the release, I want to look at condensing the mass of
> .if defined(...) options we have, at least with respect to crypto. At the
> moment we have to test everywhere for things like
> 
> .if !defined(NOCRYPT) && !defined(NOSECURE) && !defined(NO_OPENSSL) &&
> defined(MAKE_KERBEROS4)
> 
> when all we really want to know is whether or not OpenSSL is available to
> be linked with.
> 
> In addition to normalizing all of the NO* options to NO_* (or other way
> round if I get shouted down :), they should obey the correct covering
> hierarchy automatically so we don't have to explicitly test for all the
> covering options in each instance. For example, NO_CRYPT should imply
> NO_OPENSSL, which in turn implies NO_OPENSSH, etc. NOSECURE should be
> removed since it's nonfunctional. NO_CRYPT or NO_OPENSSL should conflict
> with MAKE_KERBEROS?, etc.

Right. Sounds good!

M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200003060939.LAA43479>