From: Casey Schaufler <casey@schaufler-ca.com>
To: Mimi Zohar <zohar@linux.ibm.com>,
prakhar srivastava <prsriva02@gmail.com>
Cc: linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-security-module <linux-security-module@vger.kernel.org>,
Paul Moore <paul@paul-moore.com>,
John Johansen <john.johansen@canonical.com>,
casey@schaufler-ca.com
Subject: Re: [PATCH] kexec_buffer measure
Date: Thu, 2 May 2019 09:26:34 -0700 [thread overview]
Message-ID: <a30f7742-8368-be0c-4bab-28bcce0966aa@schaufler-ca.com> (raw)
In-Reply-To: <1556812101.4134.28.camel@linux.ibm.com>
On 5/2/2019 8:48 AM, Mimi Zohar wrote:
> [Cc'ing Paul, John, Casey]
>
> On Mon, 2019-04-22 at 20:18 -0400, Mimi Zohar wrote:
>> [Cc'ing LSM mailing list]
>>
>> On Fri, 2019-04-19 at 17:30 -0700, prakhar srivastava wrote:
>>
>>> 2) Adding a LSM hook
>>> We are doing both the command line and kernel version measurement in IMA.
>>> Can you please elaborate on how this can be used outside of the scenario?
>>> That will help me come back with a better design and code. I am
>>> neutral about this.
>> As I said previously, initially you might want to only measure the
>> kexec boot command line, but will you ever want to verify or audit log
>> the boot command line hash?????Perhaps LSMs would be interested in the
>> boot command line. ??Should this be an LSM hook?
> From an LSM perspective, is there any interest in the boot command line?
I can imagine an LSM that cares about the command line,
but I have an interest in it for any work I have in progress.
>
> Mimi
>
next prev parent reply other threads:[~2019-05-02 16:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-20 0:30 prakhar srivastava
2019-04-23 0:18 ` Mimi Zohar
2019-05-02 15:48 ` Mimi Zohar
2019-05-02 16:26 ` Casey Schaufler [this message]
2019-05-02 16:28 ` Casey Schaufler
2019-05-03 0:53 ` Tetsuo Handa
2019-05-03 14:24 ` 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=a30f7742-8368-be0c-4bab-28bcce0966aa@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=john.johansen@canonical.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=prsriva02@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®