X-Original-To: alpine-devel@lists.alpinelinux.org Received: from mx1.tetrasec.net (mx1.tetrasec.net [74.117.190.25]) by lists.alpinelinux.org (Postfix) with ESMTP id 90F295C5809 for ; Fri, 12 Oct 2018 18:13:04 +0000 (GMT) Received: from mx1.tetrasec.net (mail.local [127.0.0.1]) by mx1.tetrasec.net (Postfix) with ESMTP id 65A3A9E1C24; Fri, 12 Oct 2018 18:13:04 +0000 (GMT) Received: from ncopa-desktop.copa.dup.pw (67.63.200.37.customer.cdi.no [37.200.63.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: alpine@tanael.org) by mx1.tetrasec.net (Postfix) with ESMTPSA id 8847B9E037C; Fri, 12 Oct 2018 18:13:03 +0000 (GMT) Date: Fri, 12 Oct 2018 20:12:58 +0200 From: Natanael Copa To: "Laurent Bercot" Cc: Alpine-devel Subject: Re: [alpine-devel] Switching back to OpenSSL Message-ID: <20181012201258.6c048e41@ncopa-desktop.copa.dup.pw> In-Reply-To: References: <20181011171746.4c01f758@ncopa-desktop.copa.dup.pw> X-Mailer: Claws Mail 3.17.1 (GTK+ 2.24.32; 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=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Fri, 12 Oct 2018 17:30:04 +0000 "Laurent Bercot" wrote: > >But, I can split out the LibreSSL libtls as a standalone package and > >adapt it to use with our OpenSSL packages. It is something we plan to > >do in Ad=E9lie anyway, so it may as well be incubated upstream. =20 >=20 > >Would the above solution be sufficient to resolve your concerns? =20 >=20 > Yes, an alternative implementation of libtls works for me. > Thanks! We use libtls for our ssl_client for busybox wget, so yes, we need some sort of libtls implementation. I think there are some port of it to OpenSSL out there, but I don't know what the state is. -nc --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---