From: Mimi Zohar <zohar@linux.ibm.com>
To: Jordan Hand <jorhand@linux.microsoft.com>,
Lakshmi <nramas@linux.microsoft.com>,
Ken Goldman <kgold@linux.ibm.com>,
Linux Integrity <linux-integrity@vger.kernel.org>,
David Howells <dhowells@redhat.com>
Cc: James Morris <jamorris@linux.microsoft.com>,
Prakhar Srivastava <prsriva@linux.microsoft.com>,
Balaji Balasubramanyan <balajib@linux.microsoft.com>,
Matthew Garrett <mjg59@google.com>,
James Bottomley <jejb@linux.ibm.com>
Subject: Re: [PATCH 0/2] [IMA] Measure public keys of BuiltIn Trusted Keys
Date: Wed, 12 Jun 2019 14:32:00 -0400 [thread overview]
Message-ID: <1560364320.4578.83.camel@linux.ibm.com> (raw)
In-Reply-To: <b3fbbe78-423f-b48d-b32c-ede3841bf936@linux.microsoft.com>
On Wed, 2019-06-12 at 09:47 -0700, Jordan Hand wrote:
> I don't understand why measuring the keyring is more restrictive.
It's more restrictive because of which keyring you're measuring.
You're not measuring the IMA keyring, but the builtin keyring.
Mimi
next prev parent reply other threads:[~2019-06-12 18:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 0:16 [PATCH 0/2] [IMA] Measure public keys of BuiltIn Trusted Keys Lakshmi
2019-06-06 12:44 ` Mimi Zohar
2019-06-06 16:58 ` Lakshmi
2019-06-07 14:14 ` Ken Goldman
2019-06-07 17:15 ` Lakshmi
2019-06-10 17:02 ` Lakshmi
2019-06-11 12:22 ` Mimi Zohar
2019-06-11 17:13 ` Mimi Zohar
2019-06-12 16:47 ` Jordan Hand
2019-06-12 18:32 ` Mimi Zohar [this message]
2019-06-17 17:04 ` Ken Goldman
2019-06-17 23:42 ` Lakshmi
2019-06-18 1:31 ` Matthew Garrett
2019-06-10 16:57 ` Jordan Hand
2019-06-18 17:31 ` Ken Goldman
2019-06-18 17:52 ` Jordan Hand
2019-06-25 20:27 ` Lakshmi
2019-07-16 16:33 ` Lakshmi
2019-07-16 17:51 ` Mimi Zohar
2019-07-16 23:39 ` Lakshmi
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=1560364320.4578.83.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=balajib@linux.microsoft.com \
--cc=dhowells@redhat.com \
--cc=jamorris@linux.microsoft.com \
--cc=jejb@linux.ibm.com \
--cc=jorhand@linux.microsoft.com \
--cc=kgold@linux.ibm.com \
--cc=linux-integrity@vger.kernel.org \
--cc=mjg59@google.com \
--cc=nramas@linux.microsoft.com \
--cc=prsriva@linux.microsoft.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).