From owner-cvs-all Tue Jan 28 18: 3:34 2003 Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 122F737B401; Tue, 28 Jan 2003 18:03:33 -0800 (PST) Received: from gw.nectar.cc (gw.nectar.cc [208.42.49.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id 707AE43F85; Tue, 28 Jan 2003 18:03:32 -0800 (PST) (envelope-from nectar@celabo.org) Received: from opus.celabo.org (opus.celabo.org [10.0.1.111]) by gw.nectar.cc (Postfix) with ESMTP id DFB3D44; Tue, 28 Jan 2003 20:03:31 -0600 (CST) Received: by opus.celabo.org (Postfix, from userid 1001) id 4E498557F; Tue, 28 Jan 2003 19:59:30 -0600 (CST) Date: Tue, 28 Jan 2003 19:59:30 -0600 From: "Jacques A. Vidrine" To: Peter Wemm Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/secure/lib/libcrypto opensslconf-alpha.h opensslconf-i386.h opensslconf-ia64.h opensslconf-powerpc.h opensslconf-sparc64.h Message-ID: <20030129015930.GA51683@opus.celabo.org> Mail-Followup-To: "Jacques A. Vidrine" , Peter Wemm , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org References: <200301290106.h0T16F6P029651@repoman.freebsd.org> <20030129013630.C31562A89E@canning.wemm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030129013630.C31562A89E@canning.wemm.org> X-Url: http://www.celabo.org/ User-Agent: Mutt/1.5.1i-ja.1 Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Jan 28, 2003 at 05:36:30PM -0800, Peter Wemm wrote: > Jacques Vidrine wrote: > > nectar 2003/01/28 17:06:15 PST > > > > Modified files: > > secure/lib/libcrypto opensslconf-alpha.h opensslconf-i386.h > > opensslconf-ia64.h opensslconf-powerpc.h > > opensslconf-sparc64.h > > Log: > > Force OPENSSL_NO_KRB5. OpenSSL's current implementation of RFC 2712 > > can only be built with MIT Kerberos. > > > > If we didn't define this here, then SSL-using applications would have > > to define OPENSSL_NO_KRB5 themselves in order to build. > > Ok, but what does this mean in the real world? Do krb5 users need to stop > building world? It just means that applications that use the base system's OpenSSL will continue to build. The OpenSSL 0.9.7 import would have broken a bunch of ports otherwise. (It may still break a bunch of ports, for other reasons :-) i.e. there was a window between the import of OpenSSL 0.9.7 and this commit where one would wind up unable to build some OpenSSL-using applications. i.e. I disabled a chunk of code that can not be built without MIT Kerberos. Cheers, -- Jacques A. Vidrine http://www.celabo.org/ NTT/Verio SME . FreeBSD UNIX . Heimdal Kerberos jvidrine@verio.net . nectar@FreeBSD.org . nectar@kth.se To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message