From: Sumit Garg <sumit.garg@linaro.org>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>,
Eric Biggers <ebiggers@kernel.org>,
Jarkko Sakkinen <jarkko@kernel.org>,
"Theodore Y. Ts'o" <tytso@mit.edu>,
Jaegeuk Kim <jaegeuk@kernel.org>, kernel <kernel@pengutronix.de>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
James Bottomley <jejb@linux.ibm.com>,
David Howells <dhowells@redhat.com>,
linux-fscrypt@vger.kernel.org,
"open list:HARDWARE RANDOM NUMBER GENERATOR CORE"
<linux-crypto@vger.kernel.org>,
linux-integrity <linux-integrity@vger.kernel.org>,
"open list:SECURITY SUBSYSTEM"
<linux-security-module@vger.kernel.org>,
"open list:ASYMMETRIC KEYS" <keyrings@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] fscrypt: support trusted keys
Date: Wed, 18 Aug 2021 10:23:35 +0530 [thread overview]
Message-ID: <CAFA6WYOgt9JYSSHL056ZBzCY93xHB8H=9BoN8YbqeFtevfDOpg@mail.gmail.com> (raw)
In-Reply-To: <f4264f0a83c1b080ad2a22d63ecf1fcca87dfebb.camel@linux.ibm.com>
On Tue, 17 Aug 2021 at 19:54, Mimi Zohar <zohar@linux.ibm.com> wrote:
>
> On Tue, 2021-08-17 at 16:13 +0200, Ahmad Fatoum wrote:
> > On 17.08.21 15:55, Mimi Zohar wrote:
> > > I have no opinion as to whether this is/isn't a valid usecase.
> >
> > So you'd be fine with merging trusted key support as is and leave encrypted
> > key support to someone who has a valid use case and wants to argue
> > in its favor?
>
> That decision as to whether it makes sense to support trusted keys
> directly, based on the new trust sources, is a decision left up to the
> maintainer(s) of the new usecase and the new trust sources maintainer
> Jarkko.
>
I would be in favor of supporting the use of trusted keys directly
when it comes to TEE as a trust source.
-Sumit
> thanks,
>
> Mimi
>
next prev parent reply other threads:[~2021-08-18 4:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-06 15:09 [PATCH v2] fscrypt: support trusted keys Ahmad Fatoum
2021-08-09 9:44 ` Jarkko Sakkinen
2021-08-09 10:00 ` Ahmad Fatoum
2021-08-09 10:02 ` Ahmad Fatoum
2021-08-10 18:02 ` Jarkko Sakkinen
2021-08-09 20:52 ` Eric Biggers
2021-08-10 18:06 ` Jarkko Sakkinen
2021-08-10 18:46 ` Eric Biggers
2021-08-10 21:21 ` Jarkko Sakkinen
2021-08-10 21:27 ` Eric Biggers
2021-08-11 0:17 ` Jarkko Sakkinen
2021-08-11 11:34 ` Mimi Zohar
2021-08-11 17:16 ` Eric Biggers
2021-08-12 0:54 ` Mimi Zohar
2021-08-17 13:04 ` Ahmad Fatoum
2021-08-17 13:55 ` Mimi Zohar
2021-08-17 14:13 ` Ahmad Fatoum
2021-08-17 14:24 ` Mimi Zohar
2021-08-18 2:09 ` Jarkko Sakkinen
2021-08-18 4:53 ` Sumit Garg [this message]
2021-08-09 21:24 ` Eric Biggers
2021-08-10 7:41 ` Ahmad Fatoum
2021-08-10 17:35 ` Eric Biggers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFA6WYOgt9JYSSHL056ZBzCY93xHB8H=9BoN8YbqeFtevfDOpg@mail.gmail.com' \
--to=sumit.garg@linaro.org \
--cc=a.fatoum@pengutronix.de \
--cc=dhowells@redhat.com \
--cc=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=jarkko@kernel.org \
--cc=jejb@linux.ibm.com \
--cc=jmorris@namei.org \
--cc=kernel@pengutronix.de \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=tytso@mit.edu \
--cc=zohar@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).