From owner-freebsd-current Mon Mar 6 1:39:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (dhcp137.iafrica.com [196.31.1.137]) by hub.freebsd.org (Postfix) with ESMTP id 89EB337BCE5; Mon, 6 Mar 2000 01:39:45 -0800 (PST) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id LAA43479; Mon, 6 Mar 2000 11:39:44 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200003060939.LAA43479@grimreaper.grondar.za> To: Kris Kennaway Cc: current@freebsd.org, markm@freebsd.org, jkh@freebsd.org Subject: Re: NO_OPENSSL world fixes References: In-Reply-To: ; from Kris Kennaway "Sun, 05 Mar 2000 16:59:07 PST." Date: Mon, 06 Mar 2000 11:39:44 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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