From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: Should we upgrade openssl? Date: Fri, 19 Apr 2019 12:56:35 -0400 Message-ID: <20190419165635.GA15108@jasmine.lan> References: <87wojvmk9n.fsf@dustycloud.org> <87r2a1d7s3.fsf@gnu.org> <87d0lkbyua.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="0F1p//8PRICkK4MW" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:59231) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hHWoq-0006gk-2n for guix-devel@gnu.org; Fri, 19 Apr 2019 12:56:56 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hHWom-0007YJ-AL for guix-devel@gnu.org; Fri, 19 Apr 2019 12:56:54 -0400 Content-Disposition: inline In-Reply-To: <87d0lkbyua.fsf@gnu.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ludovic =?iso-8859-1?Q?Court=E8s?= Cc: Guix-devel --0F1p//8PRICkK4MW Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 17, 2019 at 02:28:13PM +0200, Ludovic Court=C3=A8s wrote: > Merging =E2=80=98core-updates=E2=80=99 is no longer an option for 1.0: I= =E2=80=99m seriously > still aiming for around April 30th. Let=E2=80=99s get our act together! >=20 > Likewise, I don=E2=80=99t think the OpenSSL upgrade can be merged on time= =2E But > that=E2=80=99s OK: we can start working on it and have it merged as soon = as > possible, possibly with all of =E2=80=98core-updates=E2=80=99. I agree, it's not feasible to implement and test this OpenSSL upgrade for an April 30th deployment. But we do need to do the upgrade during 2019, because OpenSSL 1.0.2 will become unsupported when this year ends. It shouldn't be too bad because all the other distros are working on it too, if they have not already finished the upgrade. At this point many of the users have been adjusted to work with 1.1.1. --0F1p//8PRICkK4MW Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAly5/cAACgkQJkb6MLrK fwgRGxAAiZeeCrxsOWVRbYcwLAJAS0PiO7s2e7lpZdQv5rBf/q34qLDB9cnflqR6 Z+A9fpZVXZIwCzNdHDo8LEmA3MEmjh4dnJKoqYoVlEcQAE6ev4WkleawQ+BEdlSF eruUk769Mv5li6Map9nwECzzomvjeOYjp/tTC0sKecppUcZhzg5FoFdqwoGt+5uT HrcP6BH8n+NGI5/VPEAgs4frz2YN3vBXfPEM7iSxBGSEJk3yg6Nq4jquXgEaX53S X4AiuCt3CW2er5tIWksAnsYiN006guSRT3MgwaWqSfr0BcrohAvnIYq9fNixR/CW 6TYRvnAfDfng3M37/pWVE7dI9s73iKkxiyDgzYDqRMx1f25Wtzusduzw4kLkvTxb rWRuek8HsWVCH4UCE1vzjyPU3gJvFT5ulb3YF4c6pF1JfTReZM5D1GOdlcuCCfKn nWb5Ks2FgvPEo/RsQyjkOFpIcGdUygvnALRmO8W+3KvJf7WdLSw75d4Rm1gCDnma sro7Jt93zrd664Y0aM3QduQzVYG2MBgnye/AuoC+lgBxCdKJ0irNRMdOFpQyxdaS OhOBNNsQiP3xI1PqQKo3foYwBz6dXuoccnAnRCUnNJGPOkawR60NFJ80gJODvs6n 48rDSeNI3W5ypby4Q7F5eXcnYE4vgp10g7m8neSV8n9W7qG0Ef4= =Acdd -----END PGP SIGNATURE----- --0F1p//8PRICkK4MW--