From: Lakshmi <nramas@linux.microsoft.com>
To: Mimi Zohar <zohar@linux.ibm.com>,
Linux Integrity <linux-integrity@vger.kernel.org>,
David Howells <dhowells@redhat.com>,
James Morris <jamorris@linux.microsoft.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Balaji Balasubramanyan <balajib@linux.microsoft.com>,
Prakhar Srivastava <prsriva@linux.microsoft.com>
Subject: Re: [PATCH 0/2] public key: IMA signer logging: Log public key of IMA Signature signer in IMA log
Date: Wed, 15 May 2019 11:17:52 -0700 [thread overview]
Message-ID: <715a9b39-0cde-1ce0-2d01-68d4fc0f5333@linux.microsoft.com> (raw)
In-Reply-To: <1557854992.4139.69.camel@linux.ibm.com>
Hi Mimi,
I would like to make sure I understood your feedback.
>
> Why duplicate the certificate info on each record in the measurement
> list? Why not add the certificate info once, as the key is loaded
> onto the .ima and .platform keyrings?
>
> Mimi
>
key_create_or_update function in security/keys/key.c is called to
add\update a key to a keyring. Are you suggesting that an IMA function
be called from here to add the certificate info to the IMA log?
Our requirement is that the key information is available in the IMA log
which is TPM backed.
Thanks,
-lakshmi
next prev parent reply other threads:[~2019-05-15 18:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 17:14 [PATCH 0/2] public key: IMA signer logging: Log public key of IMA Signature signer in IMA log Lakshmi
2019-05-14 17:29 ` Mimi Zohar
2019-05-15 18:17 ` Lakshmi [this message]
2019-05-16 22:45 ` Mimi Zohar
2019-05-16 14:34 ` Ken Goldman
2019-05-17 1:29 ` Lakshmi
2019-05-17 14:41 ` Ken Goldman
2019-05-20 23:15 ` Lakshmi
2019-05-22 18:57 ` Ken Goldman
2019-05-22 19:37 ` 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=715a9b39-0cde-1ce0-2d01-68d4fc0f5333@linux.microsoft.com \
--to=nramas@linux.microsoft.com \
--cc=balajib@linux.microsoft.com \
--cc=dhowells@redhat.com \
--cc=jamorris@linux.microsoft.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prsriva@linux.microsoft.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.