From owner-freebsd-security@freebsd.org Wed Aug 1 14:05:34 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 60F1C105D3E4; Wed, 1 Aug 2018 14:05:34 +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 0773B754A8; Wed, 1 Aug 2018 14:05:33 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from [192.168.43.57] (mobile-107-107-59-242.mycingular.net [107.107.59.242]) (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 7B9BF5D4F; Wed, 1 Aug 2018 14:05:32 +0000 (UTC) Subject: Re: Status of OpenSSL 1.1.1 To: Warner Losh Cc: FreeBSD Hackers , freebsd-security , "freebsd-arch@freebsd.org" , freebsd-current References: 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: Wed, 1 Aug 2018 10:05:28 -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="JA5mbHlyqvhScI7wZ6R8M1XpZcozqnJpS" 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: Wed, 01 Aug 2018 14:05:34 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --JA5mbHlyqvhScI7wZ6R8M1XpZcozqnJpS Content-Type: multipart/mixed; boundary="MkkRTdgKDiexhqqCfM3q3sy204CtZoNlA"; protected-headers="v1" From: Eric McCorkle To: Warner Losh Cc: FreeBSD Hackers , freebsd-security , "freebsd-arch@freebsd.org" , freebsd-current Message-ID: Subject: Re: Status of OpenSSL 1.1.1 References: In-Reply-To: --MkkRTdgKDiexhqqCfM3q3sy204CtZoNlA Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 08/01/2018 09:02, Warner Losh wrote: >=20 >=20 > On Wed, Aug 1, 2018, 12:31 PM Eric McCorkle > wrote: >=20 > Hi folks, >=20 > I'm wondering what's the status of OpenSSL 1.1.1 integration into b= ase? > More specifically, is there a repo or a branch that's started the > integration?=C2=A0 I'm aware of the wiki page and the list of port = build > issues, but that seems to be based on replacing the base OpenSSL wi= th a > port build (similar to the way one replaces it with LibreSSL). >=20 > I have some work I'd like to do that's gating on sorting out the > kernel/loader crypto situation, and I'd very much like to see OpenS= SL > 1.1.1 get merged, so I can start to look into doing that. >=20 >=20 > 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 full 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. --MkkRTdgKDiexhqqCfM3q3sy204CtZoNlA-- --JA5mbHlyqvhScI7wZ6R8M1XpZcozqnJpS Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQQPGL/SuSPN3pRzpwUI38IpFsHCbAUCW2G+KAAKCRAI38IpFsHC bGLuAPwJYpPYYEmpGeu6HQnVaM9iakWHN8vM2OAGNoySUSn01QD/UfTooHun+QlI wvSpvUvJ1rCt+H5m6Ho6w49tHObnUgs= =jIbP -----END PGP SIGNATURE----- --JA5mbHlyqvhScI7wZ6R8M1XpZcozqnJpS--