Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Wed, 7 Jul 2021 17:28:41 +0100
From:   Christoph Hellwig <hch@infradead.org>
To:     Eric Snowberg <eric.snowberg@oracle.com>
Cc:     Christoph Hellwig <hch@infradead.org>, keyrings@vger.kernel.org,
        linux-integrity <linux-integrity@vger.kernel.org>,
        Mimi Zohar <zohar@linux.ibm.com>,
        David Howells <dhowells@redhat.com>,
        David Woodhouse <dwmw2@infradead.org>,
        herbert@gondor.apana.org.au, davem@davemloft.net,
        jarkko@kernel.org, jmorris@namei.org, serge@hallyn.com,
        keescook@chromium.org, gregkh@linuxfoundation.org,
        torvalds@linux-foundation.org, scott.branden@broadcom.com,
        weiyongjun1@huawei.com, nayna@linux.ibm.com, ebiggers@google.com,
        ardb@kernel.org, nramas@linux.microsoft.com, lszubowi@redhat.com,
        linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
        linux-security-module@vger.kernel.org,
        James.Bottomley@hansenpartnership.com, pjones@redhat.com,
        glin@suse.com, "konrad.wilk@oracle.com" <konrad.wilk@oracle.com>
Subject: Re: [PATCH RFC 00/12] Enroll kernel keys thru MOK
Message-ID: <YOXWOaPma2dMf6fk@infradead.org>
References: <20210707024403.1083977-1-eric.snowberg@oracle.com>
 <YOVNrhxCJpfTbpVq@infradead.org>
 <E4A6A4E2-F9CB-4996-965A-772B3CA15555@oracle.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E4A6A4E2-F9CB-4996-965A-772B3CA15555@oracle.com>
Precedence: bulk

On Wed, Jul 07, 2021 at 10:23:04AM -0600, Eric Snowberg wrote:
> 
> > On Jul 7, 2021, at 12:46 AM, Christoph Hellwig <hch@infradead.org> wrote:
> > 
> > On Tue, Jul 06, 2021 at 10:43:51PM -0400, Eric Snowberg wrote:
> >> This is a follow up to the "Add additional MOK vars" [1] series I 
> >> previously sent.  This series incorporates the feedback given 
> >> both publicly on the mailing list and privately from Mimi. This 
> >> series just focuses on getting end-user keys into the kernel trust 
> >> boundary.
> > 
> > WTF is MOK?
> 
> MOK stands for Machine Owner Key.   The MOK facility can be used to 
> import keys that you use to sign your own development kernel build, 
> so that it is able to boot with UEFI Secure Boot enabled. Many Linux 
> distributions have implemented UEFI Secure Boot using these keys 
> as well as the ones Secure Boot provides.  It allows the end-user 
> a choice, instead of locking them into only being able to use keys 
> their hardware manufacture provided, or forcing them to enroll keys 
> through their BIOS.

Please spell this out in your cover letters and commit logs.