[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1556812101.4134.28.camel@linux.ibm.com>
Date: Thu, 02 May 2019 11:48:21 -0400
From: Mimi Zohar <zohar@...ux.ibm.com>
To: prakhar srivastava <prsriva02@...il.com>
Cc: linux-integrity@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-security-module <linux-security-module@...r.kernel.org>,
Paul Moore <paul@...l-moore.com>,
Casey Schaufler <casey@...aufler-ca.com>,
John Johansen <john.johansen@...onical.com>
Subject: Re: [PATCH] kexec_buffer measure
[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?
Mimi
Powered by blists - more mailing lists