From owner-freebsd-security@freebsd.org Fri Aug 3 11:02:24 2018 Return-Path: Delivered-To: freebsd-security@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 03AB31065CDE; Fri, 3 Aug 2018 11:02:24 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from mail.metricspace.net (static-98-116-200-172.nycmny.fios.verizon.net [98.116.200.172]) by mx1.freebsd.org (Postfix) with ESMTP id A0FD67C467; Fri, 3 Aug 2018 11:02:23 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from [172.16.0.23] (unknown [172.16.0.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id 89930619A; Fri, 3 Aug 2018 11:02:22 +0000 (UTC) Subject: Re: Status of OpenSSL 1.1.1 To: Warner Losh , Benjamin Kaduk Cc: FreeBSD Hackers , "freebsd-arch@freebsd.org" , freebsd-current , freebsd-security References: <20180802234519.GD68224@kduck.kaduk.org> From: Eric McCorkle Openpgp: preference=signencrypt Autocrypt: addr=eric@metricspace.net; prefer-encrypt=mutual; keydata= mDMEWue2FBYJKwYBBAHaRw8BAQdAP/qVPlXodV6pYO5b1Jw0eFyMhyDD7B5y5eFsciutEfS0 JEVyaWMgTWNDb3JrbGUgPGVyaWNAbWV0cmljc3BhY2UubmV0PoiWBBMWCAA+FiEEDxi/0rkj zd6Uc6cFCN/CKRbBwmwFAlrnthQCGwMFCQHhM4AFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AA CgkQCN/CKRbBwmyGKAD/XTSBOItCKcYCPTlsaS1aQYVEwWXXFgdjWE+WsNdZUS8A/AhYAbQZ kNZNimE2rQLoklkfTA74qF/V257NuQi4QDcLuDgEWue2FBIKKwYBBAGXVQEFAQEHQKpZVyCG ync/xqejm2C1HKGXLJTUu38RvnrR3UYECz9nAwEIB4h+BBgWCAAmFiEEDxi/0rkjzd6Uc6cF CN/CKRbBwmwFAlrnthQCGwwFCQHhM4AACgkQCN/CKRbBwmyi2wEAmvaGt8QMjGELzm27gP4c jJGUi7oigsLmTiFPkpJqPz0A+QFBSCvxJaxCMyoVru/xB6bunpJ+Wtsj8HD1EuJOn4EJ Message-ID: Date: Fri, 3 Aug 2018 07:02:18 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="3Jlf5EtgHrBUwuVED8RcynGXM8EBmN3FH" X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Aug 2018 11:02:24 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --3Jlf5EtgHrBUwuVED8RcynGXM8EBmN3FH Content-Type: multipart/mixed; boundary="SgFMOIbWT0nMndG6NllvpPpohfXOlolaP"; protected-headers="v1" From: Eric McCorkle To: Warner Losh , Benjamin Kaduk Cc: FreeBSD Hackers , "freebsd-arch@freebsd.org" , freebsd-current , freebsd-security Message-ID: Subject: Re: Status of OpenSSL 1.1.1 References: <20180802234519.GD68224@kduck.kaduk.org> In-Reply-To: --SgFMOIbWT0nMndG6NllvpPpohfXOlolaP Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 08/03/2018 04:44, Warner Losh wrote: >=20 >=20 > On Thu, Aug 2, 2018 at 5:45 PM, Benjamin Kaduk > wrote: >=20 > On Wed, Aug 01, 2018 at 10:05:28AM -0400, Eric McCorkle wrote: > > On 08/01/2018 09:02, Warner Losh wrote: > > > > > > > > > On Wed, Aug 1, 2018, 12:31 PM Eric McCorkle > > > > >> wr= ote: > > > > > >=C2=A0 =C2=A0 =C2=A0Hi folks, > > > > > >=C2=A0 =C2=A0 =C2=A0I'm wondering what's the status of OpenSSL 1= =2E1.1 integration > into base? > > >=C2=A0 =C2=A0 =C2=A0More specifically, is there a repo or a bran= ch that's > started the > > >=C2=A0 =C2=A0 =C2=A0integration?=C2=A0 I'm aware of the wiki pag= e and the list of > port build > > >=C2=A0 =C2=A0 =C2=A0issues, but that seems to be based on replac= ing the base > OpenSSL with a > > >=C2=A0 =C2=A0 =C2=A0port build (similar to the way one replaces = it with LibreSSL). > > > > > >=C2=A0 =C2=A0 =C2=A0I have some work I'd like to do that's gatin= g on sorting out the > > >=C2=A0 =C2=A0 =C2=A0kernel/loader crypto situation, and I'd very= much like to > see OpenSSL > > >=C2=A0 =C2=A0 =C2=A01.1.1 get merged, so I can start to look int= o doing that. > > > > > > > > > There are patches to use bear SSL for the loader. OpenSSL is > simply too > > > large to use due to limits the loader operates under. > > > > I was going to look into the feasibility of doing something like = what > > LibreSSL does with portable, where they extract a subset of the f= ull > > library designed to be embedded in the kernel, loader, etc. > > > > I think it ought to be possible to do something like that, but it= > really > > ought to be done in a tree with 1.1.1 integrated. > > >=20 > It wouldn't be terribly easy or effective, IMO.=C2=A0 OpenSSL wasn'= t designed > with such modularity in mind. >=20 >=20 > Others that have tried have found OpenSSL to be way too large for the > boot loader and a completely impossible to subset enough to get things > small enough due to the intertwingled nature of things. To what extent, if any, does this change in 1.1.1, though? --SgFMOIbWT0nMndG6NllvpPpohfXOlolaP-- --3Jlf5EtgHrBUwuVED8RcynGXM8EBmN3FH Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQQPGL/SuSPN3pRzpwUI38IpFsHCbAUCW2Q2OgAKCRAI38IpFsHC bHx7AQCF1Yu898/tbKfMJvXrPaJmDmV2wf66gtK5k+KJ1ulKmgEAuuXdSuUriYuK n3pc4P82OqfT9LnymaHfY6T9KM/6QAg= =tWx/ -----END PGP SIGNATURE----- --3Jlf5EtgHrBUwuVED8RcynGXM8EBmN3FH--