From owner-freebsd-stable@FreeBSD.ORG Thu Apr 17 13:34:54 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F1EB37B401 for ; Thu, 17 Apr 2003 13:34:54 -0700 (PDT) Received: from mx1.evo6.net (mx1.evo6.net [80.76.194.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 345D043F93 for ; Thu, 17 Apr 2003 13:34:53 -0700 (PDT) (envelope-from andy@evo6.org) Received: from vx (vx.noc.evo6.net [10.0.0.10]) by mx1.evo6.net (8.12.9/8.12.9) with SMTP id h3HKYmeh086713; Thu, 17 Apr 2003 21:34:48 +0100 (BST) (envelope-from andy@evo6.org) Message-ID: <001e01c30520$c57b4b70$0a00000a@vx> From: "Andy Gilligan" To: "Doug Silver" References: <200304151126.21202.dsilver@urchin.com><200304151618.21167.dsilver@urchin.com> <20030415204211.I6307@shell.inch.com> <200304171232.48652.dsilver@urchin.com> Date: Thu, 17 Apr 2003 21:34:40 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Spam-Status: No, hits=-12.9 required=5.0 tests=ORIGINAL_MESSAGE,QUOTED_EMAIL_TEXT,REFERENCES version=2.53 X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp) cc: stable@freebsd.org Subject: Re: Problem logging in after upgrade to 4.8-Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Apr 2003 20:34:54 -0000 ----- Original Message ----- From: "Doug Silver" To: "Charles Sprickman" Cc: 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 libcrypt? > > I just figured out where I shot myself in the foot ;\ In my attempt to strip > out libcrypto/libssl out of the build process I commented in "NOSECURE" and > "NOCRYPTO" in /etc/make.conf -- and to ensure it, I removed the source. So, > that is clearly the wrong thing to do. Is the preferred method, if I simply > want to ensure that libcrypto and libssl are used from the openssl port, to > 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)? > > -doug In /etc/make.conf, you might want to set: OPENSSL_OVERWRITE_BASE= true Then build and install /usr/ports/security/openssl as normal. This should replace openssl in the base system with the port version. Andy