Date: Wed, 1 Aug 2018 14:02:46 +0100 From: Warner Losh <imp@bsdimp.com> To: Eric McCorkle <eric@metricspace.net> 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: <CANCZdfpRSxKAvW=X2Fh5OM3ZxzkhPxC3ooOgLpogkMUdwpumRg@mail.gmail.com> In-Reply-To: <b7b8a27c-b520-dcba-e7eb-fa3fa2d78083@metricspace.net> References: <b7b8a27c-b520-dcba-e7eb-fa3fa2d78083@metricspace.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Aug 1, 2018, 12:31 PM Eric McCorkle <eric@metricspace.net> wrote: > Hi folks, > > I'm wondering what's the status of OpenSSL 1.1.1 integration into base? > More specifically, is there a repo or a branch that's started the > integration? 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 with a > port build (similar to the way one replaces it with LibreSSL). > > 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 OpenSSL > 1.1.1 get merged, so I can start to look into 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. Warner Incidentally, if there's something I can do to help out with integrating > 1.1.1 into base, I'd potentially be interested. > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfpRSxKAvW=X2Fh5OM3ZxzkhPxC3ooOgLpogkMUdwpumRg>