X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@mail.alpinelinux.org Received: from ncopa-laptop (189-70-255-191.user.veloxzone.com.br [189.70.255.191]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: n@tanael.org) by mail.alpinelinux.org (Postfix) with ESMTPSA id AC8C7DC0073; Fri, 6 Feb 2015 13:53:20 +0000 (UTC) Date: Fri, 6 Feb 2015 14:53:15 +0100 From: Natanael Copa To: Timo Teras Cc: Alpine-devel Subject: Re: [alpine-devel] openssl-1.0.2 or libressl ? Message-ID: <20150206145315.3d996f20@ncopa-laptop> In-Reply-To: <20150205103440.3f456d65@vostro> References: <20150203192523.247fbf53@vostro> <0A02C80E-3B17-41DE-8822-250D7C0DC2E1@gmail.com> <20150205103440.3f456d65@vostro> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; x86_64-alpine-linux-musl) X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Thu, 5 Feb 2015 10:34:40 +0200 Timo Teras wrote: > On Tue, 3 Feb 2015 09:29:31 -0800 > systmkor wrote: >=20 > >=20 > > > So I'm wondering should we reconsider libressl at this point? Any > > > thoughts? > >=20 > > My vote is that we stick with openssl for version 1.0.2 but start the > > process to move to libressl. Even if we don=E2=80=99t move to it offici= ally, > > it would be nice as an alternative. >=20 > Agreed. And I just realized that 1.0.2 is ABI compatible with 1.0.1 and > 1.0.0. So no recompiles should be needed. >=20 > Find attached the upgrade commit. All patches are rebased, they ran > openssl source code through indent. Also c_rehash is updated to be > smarter. >=20 > I'm wondering if I should push this to testing, and let it be there for > few weeks until updating the package in main. We normally don't do that when ABI is compatible. I think you can push it to main if you first do basic testing, eg verify that apk does not completely breaks, test s_client against some server and test some application like curl or equvalent that https is not totally broken. Move it to testing first if you think there are some reason to believe that it might break things or if you know that you will not be able to quickly fix any potential breakages. -nc >=20 > /Timo --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---