Date: Tue, 15 Jul 2014 07:44:18 +0200 From: Johan van Selst <johans@stack.nl> To: "Jens K. Loewe" <bsd@tuxproject.de> Cc: freebsd-ports <freebsd-ports@freebsd.org> Subject: Re: Some ports not compiling with security/libressl Message-ID: <20140715054418.GA27471@mud.stack.nl> In-Reply-To: <348083446.20140715002518@tuxproject.de> References: <348083446.20140715002518@tuxproject.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--/9DWx/yDrRhgMJTb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Jens, Jens K. Loewe wrote: > I'm currently trying to replace OpenSSL on my server by LibreSSL > (security/libressl). Anyway, I found some ports struggling to compile > with it, including (but not limited to) www/w3m, > security/p5-Net-SSLeay (which seems to query the OpenSSL version > directly?!) and lang/python27. >=20 > Is it planned to take care of this use case? LibreSSL is explicitly not going to be fully compatible with OpenSSL. Certain functions from OpenSSL have already been removed from LibreSSL and as rewrites contine, the difference may grow. There would not be any point in adding a compatibility layer to the FreeBSD port. Application authors may chose to update their applications to work with LibreSSL, but I do not expect this to happen very quickly, especially because LibreSSL is a fast-moving target at the moment. That said, I'm not maintaining any of the ports you mentioned, and I did not look into the current compatibility issues. But in general, if you want full OpenSSL-compatibility, I suggest sticking with OpenSSL. Regards, Johan --/9DWx/yDrRhgMJTb Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iF4EAREIAAYFAlPEv7IACgkQAEpMHW8nCPSKIwEAn4DxAwbOL0/8TdlXt8BZfwgH mX1rDCgVvF1pVU87tucBAKwZVn36dKRiSNANhMPaqwJ+u84K4jxYCP5rpaEStWCs =GPbR -----END PGP SIGNATURE----- --/9DWx/yDrRhgMJTb--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140715054418.GA27471>