From: Prakhar Srivastava <prsriva@microsoft.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-integrity@vger.kernel.org"
<linux-integrity@vger.kernel.org>
Subject: Adding cmldine args measure to ima
Date: Fri, 22 Mar 2019 17:27:12 +0000 [thread overview]
Message-ID: <DM5PR21MB0747326E1CAA3F66CE61B149BC430@DM5PR21MB0747.namprd21.prod.outlook.com> (raw)
Hi,
Currently Kexec (kexec_file_load) code path does not measure the cmdline
arguments passed to the next kernel.The boot_aggregate won't change since
the EFI loader hasn't been triggered. Attesting the same in K2 has no impact.
Adding the cmdline measurement will add some attestable criteria.
To account for the cmdline passed, we are looking at using IMA to measure and
pass the buffer so that it can be attested.
Do you have any alternate solutions/concerns with this approach?
Thanks,
Prakhar Srivastava
next reply other threads:[~2019-03-22 17:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 17:27 Prakhar Srivastava [this message]
2019-03-22 20:36 ` Adding cmldine args measure to ima Mimi Zohar
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=DM5PR21MB0747326E1CAA3F66CE61B149BC430@DM5PR21MB0747.namprd21.prod.outlook.com \
--to=prsriva@microsoft.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).