From owner-freebsd-stable Wed Feb 21 13:11:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nisser.com (c0039.upc-c.chello.nl [212.187.0.39]) by hub.freebsd.org (Postfix) with ESMTP id B86E837B491 for ; Wed, 21 Feb 2001 13:11:15 -0800 (PST) (envelope-from roelof@nisser.com) Received: from nisser.com (roelof [10.0.0.2]) by nisser.com (8.9.3/8.9.2) with ESMTP id WAA99289; Wed, 21 Feb 2001 22:10:42 +0100 (CET) (envelope-from roelof@nisser.com) Message-ID: <3A942ED2.999AF22D@nisser.com> Date: Wed, 21 Feb 2001 22:10:42 +0100 From: Roelof Osinga Organization: Nisser - Nr. 1 in Veiligheid X-Mailer: Mozilla 4.72 [en] (Windows NT 5.0; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: JT Cc: freebsd-stable@freebsd.org Subject: Re: 4.2 STABLE: libssl.so undef: sk_X509_NAME_value References: <3A93C117.57D7957F@nisser.com> <20010221151123.A235@zed.unbeat.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG JT wrote: > > ... > mod_ssl tends to be sensitive to (non-bugfix) changes in openssl and > they should usually be kept in sync. Since openssl is now in the > source tree you will probably want to delete any openssl port before > rebuilding. You can say that again. Went into the *13-modssl port's ssl subdir, deleted the *lo and *so (well, mvd to BACKUP/ actually :), gave a make and copied the new one to the designated libexec directory. apachectrl startssl worked forthwith! Makes me think about a) that missing line I found, could be my eyesight who knows? and b) what more ports might suffer from this very same problem. With which I'm not referring to potential eye problems but to sensitivities to openssl changes. Roelof PS I'll not put in a PR since by now I'm not sure about the state prior to my patching. Kris'll probably read this sooner or later anyway. -- Home is where the (@) http://eboa.com/ is. Nisser home -- http://www.Nisser.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message