linux-kernel - Re: Adding cmldine args measure to ima

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <1553286984.5291.2.camel@linux.ibm.com>
Date:   Fri, 22 Mar 2019 16:36:24 -0400
From:   Mimi Zohar <zohar@...ux.ibm.com>
To:     Prakhar Srivastava <prsriva@...rosoft.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-integrity@...r.kernel.org" <linux-integrity@...r.kernel.org>
Subject: Re: Adding cmldine args measure to ima

On Fri, 2019-03-22 at 17:27 +0000, Prakhar Srivastava wrote:
> 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?

I started looking at this a couple of years ago, but haven't had time.
I definitely don't have problems with extending IMA to measure the
boot command line.

Mimi