Date: Wed, 21 Feb 2001 20:54:25 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Roelof Osinga <roelof@nisser.com> Cc: JT <luser@ahab.com>, freebsd-stable@freebsd.org Subject: Re: 4.2 STABLE: libssl.so undef: sk_X509_NAME_value Message-ID: <20010221205425.A66731@mollari.cthul.hu> In-Reply-To: <3A942ED2.999AF22D@nisser.com>; from roelof@nisser.com on Wed, Feb 21, 2001 at 10:10:42PM %2B0100 References: <3A93C117.57D7957F@nisser.com> <20010221151123.A235@zed.unbeat.com> <3A942ED2.999AF22D@nisser.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Feb 21, 2001 at 10:10:42PM +0100, Roelof Osinga wrote: > JT wrote: > >=20 > > ... > > 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. >=20 > 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. >=20 > apachectrl startssl worked forthwith! >=20 > 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. >=20 > Roelof >=20 > 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. The OpenSSL 0.9.6 import which happened some time after 4.2-RELEASE broke binary compatibility (so you had to recompile certain apps as you discovered), but I didn't notice because none of the test applications I used happened to use those functions, and not enough people bothered to test it when I asked prior to import for it to be discovered (actually, a few people apparently did notice, but declined to inform me :-(. Oh well, I'll be more vigilant in future. Kris --cWoXeonUoKmBZSoM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6lJuBWry0BWjoQKURAhQUAKD+ZYNQMX6u8Gcm12wZpPMbZtKY6gCglkR9 1W3ODtNnqoTrTONWHZBzRGU= =sqEa -----END PGP SIGNATURE----- --cWoXeonUoKmBZSoM-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010221205425.A66731>