[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <D10Y0V64JXG8.1F6S3OZDACCGF@kernel.org>
Date: Sat, 04 May 2024 17:51:33 +0300
From: "Jarkko Sakkinen" <jarkko@...nel.org>
To: "Ben Boeckel" <me@...boeckel.net>
Cc: "Ignat Korchagin" <ignat@...udflare.com>, "James Bottomley"
<James.Bottomley@...senpartnership.com>, "Mimi Zohar"
<zohar@...ux.ibm.com>, "David Howells" <dhowells@...hat.com>, "Paul Moore"
<paul@...l-moore.com>, "James Morris" <jmorris@...ei.org>,
<serge@...lyn.com>, <linux-integrity@...r.kernel.org>,
<keyrings@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<kernel-team@...udflare.com>
Subject: Re: [RFC PATCH 0/2] TPM derived keys
On Sat May 4, 2024 at 4:55 PM EEST, Ben Boeckel wrote:
> On Sat, May 04, 2024 at 03:21:11 +0300, Jarkko Sakkinen wrote:
> > I have no idea for what the key created with this is even used, which
> > makes this impossible to review.
>
> Additionally, there is nothing in Documentation/ for how userspace might
> use or create them. This includes things like their description format
> and describing available options.
The whole user story is plain out broken. Documenting a feature that has
no provable use case won't fix that part.
So it is better to start with the cover letter. With the *existing*
knowledge of the *real* issue I don't think we need this tbh.
BR, Jarkko
Powered by blists - more mailing lists