[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191209194715.GD19243@linux.intel.com>
Date: Mon, 9 Dec 2019 21:47:15 +0200
From: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To: James Bottomley <jejb@...ux.ibm.com>
Cc: "Zhao, Shirley" <shirley.zhao@...el.com>,
Mimi Zohar <zohar@...ux.ibm.com>,
Jonathan Corbet <corbet@....net>,
"linux-integrity@...r.kernel.org" <linux-integrity@...r.kernel.org>,
"keyrings@...r.kernel.org" <keyrings@...r.kernel.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
'Mauro Carvalho Chehab' <mchehab+samsung@...nel.org>,
"Zhu, Bing" <bing.zhu@...el.com>,
"Chen, Luhai" <luhai.chen@...el.com>
Subject: Re: One question about trusted key of keyring in Linux kernel.
On Mon, Dec 02, 2019 at 10:55:32AM -0800, James Bottomley wrote:
> blob but it looks like we need to fix the API. I suppose the good news
> is given this failure that we have the opportunity to rewrite the API
> since no-one else can have used it for anything because of this. The
I did successfully run this test when I wrote it 5 years ago:
https://github.com/jsakkine-intel/tpm2-scripts/blob/master/keyctl-smoke.sh
Given that there is API a way must be found that backwards compatibility
is not broken. New format is fine but it must co-exist.
/Jarkko
Powered by blists - more mailing lists