Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Subject: Re: Adding cmldine args measure to ima
From:   Mimi Zohar <zohar@linux.ibm.com>
To:     Prakhar Srivastava <prsriva@microsoft.com>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "linux-integrity@vger.kernel.org" <linux-integrity@vger.kernel.org>
Date:   Fri, 22 Mar 2019 16:36:24 -0400
In-Reply-To: <DM5PR21MB0747326E1CAA3F66CE61B149BC430@DM5PR21MB0747.namprd21.prod.outlook.com>
References: <DM5PR21MB0747326E1CAA3F66CE61B149BC430@DM5PR21MB0747.namprd21.prod.outlook.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Message-Id: <1553286984.5291.2.camel@linux.ibm.com>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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