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-next>] [day] [month] [year] [list]
Message-ID: <DM5PR21MB0747326E1CAA3F66CE61B149BC430@DM5PR21MB0747.namprd21.prod.outlook.com>
Date:   Fri, 22 Mar 2019 17:27:12 +0000
From:   Prakhar Srivastava <prsriva@...rosoft.com>
To:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-integrity@...r.kernel.org" <linux-integrity@...r.kernel.org>
Subject: Adding cmldine args measure to ima

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ