Date: Wed, 1 Aug 2018 10:05:28 -0400 From: Eric McCorkle <eric@metricspace.net> To: Warner Losh <imp@bsdimp.com> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org>, freebsd-security <freebsd-security@freebsd.org>, "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: Status of OpenSSL 1.1.1 Message-ID: <dc890dce-59b0-4647-268b-6035e8fbfd31@metricspace.net> In-Reply-To: <CANCZdfpRSxKAvW=X2Fh5OM3ZxzkhPxC3ooOgLpogkMUdwpumRg@mail.gmail.com> References: <b7b8a27c-b520-dcba-e7eb-fa3fa2d78083@metricspace.net> <CANCZdfpRSxKAvW=X2Fh5OM3ZxzkhPxC3ooOgLpogkMUdwpumRg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --JA5mbHlyqvhScI7wZ6R8M1XpZcozqnJpS Content-Type: multipart/mixed; boundary="MkkRTdgKDiexhqqCfM3q3sy204CtZoNlA"; protected-headers="v1" From: Eric McCorkle <eric@metricspace.net> To: Warner Losh <imp@bsdimp.com> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org>, freebsd-security <freebsd-security@freebsd.org>, "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org>, freebsd-current <freebsd-current@freebsd.org> Message-ID: <dc890dce-59b0-4647-268b-6035e8fbfd31@metricspace.net> Subject: Re: Status of OpenSSL 1.1.1 References: <b7b8a27c-b520-dcba-e7eb-fa3fa2d78083@metricspace.net> <CANCZdfpRSxKAvW=X2Fh5OM3ZxzkhPxC3ooOgLpogkMUdwpumRg@mail.gmail.com> In-Reply-To: <CANCZdfpRSxKAvW=X2Fh5OM3ZxzkhPxC3ooOgLpogkMUdwpumRg@mail.gmail.com> --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 <eric@metricspace.net > <mailto:eric@metricspace.net>> 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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?dc890dce-59b0-4647-268b-6035e8fbfd31>