From owner-freebsd-security@freebsd.org Fri Aug 3 08:44:11 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 04C5E10623F6 for ; Fri, 3 Aug 2018 08:44:11 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8AC3C7719A for ; Fri, 3 Aug 2018 08:44:10 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22b.google.com with SMTP id q19-v6so4347361ioh.11 for ; Fri, 03 Aug 2018 01:44:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=BAiAO4BN65wamN90CtGrC3g8xn03btAGQa9snL4okZQ=; b=AgMTGXLK+Jm7fyXoAok+LfpFrN9+zmvWAB8v6GV1RWkMUIfzUd4+da10WpE+aPBBgu zbsUXqKSs/e3aDV1giQLrA7ElR+OFj8z2087t1FF9Eaol0cYIeDW509p2cAuVP3EZ2mN 8arVoYI9ax8IB78J4rSQebSB2plZOVvrOZZAoPxSjMtuZb/OBzEUnjfPkL1ucAge4R1O wNEy9mapC8fyfnonYrcDEb0GdFnfY1KU/YkoQc4a5IDHYhDcx64AFF/aDg0B6SsNy4dw 1BSDXVc8p8JhB0LA9tjvWFI+kQ4Oad6MaXpQV75Qy6gqq6xpSRS8c/xM/5zuwYJBu9sg XJwg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=BAiAO4BN65wamN90CtGrC3g8xn03btAGQa9snL4okZQ=; b=G0Bcy1vVbB5l8pGwspSiRT/TmVZ2gZqaS2mRS63RBku127+IVGDF0/aCoi0SEYTKyf n+5XJ0ftT5sygH4o4SBlLq2cFICUwUTfLkpRgbwi3AQSH3CPoCfTKxIzQhc6SqrAge5x Uw+CllOxIm0BKyOOs4wW1JVUQu+BtpYHfekxiPqYKuScf4ipt6S2c36QI3c6kknI1hNc ON0awa1KEukHDG85U8nd1fkPlxUmYUR3HS6tbCmZvLdKSXQQYNX2XuzMWx2mknrHd/Va BudnoYEDfc6jhQWwmbCX+3Kaf5DgKc60W3FrgxuerZu5wOGue74VBFbRE0WDzFu1C/l8 FSSg== X-Gm-Message-State: AOUpUlE9VXKQlTcZvJ156+S0IlnaUq7nLGpDaYDIftL8MsZuCHMyVN+b //FpBzOYJxbrYjxBoEuZW63+0JwLDJFSDkTMLmE4Sw== X-Google-Smtp-Source: AA+uWPxRtETiA0vQuvKOkan73dUmhjbC72QhIOzEYkHQ5bQhRNSsT2bApwIbofxOY4mxJwvfamQK9l4tbkP2Pn85yKQ= X-Received: by 2002:a6b:d004:: with SMTP id x4-v6mr5064998ioa.299.1533285849927; Fri, 03 Aug 2018 01:44:09 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:4485:0:0:0:0:0 with HTTP; Fri, 3 Aug 2018 01:44:09 -0700 (PDT) X-Originating-IP: [86.153.210.77] In-Reply-To: <20180802234519.GD68224@kduck.kaduk.org> References: <20180802234519.GD68224@kduck.kaduk.org> From: Warner Losh Date: Fri, 3 Aug 2018 02:44:09 -0600 X-Google-Sender-Auth: ij_u90ZUmAUGxcJSfLBylG5FCvM Message-ID: Subject: Re: Status of OpenSSL 1.1.1 To: Benjamin Kaduk Cc: Eric McCorkle , FreeBSD Hackers , "freebsd-arch@freebsd.org" , freebsd-current , freebsd-security X-Mailman-Approved-At: Fri, 03 Aug 2018 10:34:11 +0000 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 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 08:44:11 -0000 On Thu, Aug 2, 2018 at 5:45 PM, Benjamin Kaduk wrote: > 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 > > > 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. > > > > 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. > > > > It wouldn't be terribly easy or effective, IMO. OpenSSL wasn't designed > with such modularity in mind. > 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. Warner