Linux-Integrity Archive on
 help / Atom feed
* Carrying over the ima log during kexec_file_load
@ 2019-05-11  0:16 prakhar srivastava
  0 siblings, 0 replies; 1+ messages in thread
From: prakhar srivastava @ 2019-05-11  0:16 UTC (permalink / raw)
  To: linux-kernel, linux-integrity, linux-security-module, kexec
  Cc: jmorris, Mimi Zohar, dyoung, bhe, vgoyal


I am currently looking at carrying over the ima log from the current
kernel to the next kernel during soft reboot(kexec_file_load) for arm64
and x86_64.
During soft reboot(kexec_file_load) TPM boot PCR’s(PCRs 0 through 7)
are not reset or extended and thus the boot aggregate does not change,
leaving the new kernel with a sense of secure boot.
During kexec_file_load the kernel file signature is validated through PE
file signature validation.
The boot cmdline args will also be measured with
“kexec cmdline buffer measure” change which is in progress.

Looking at the powerpc implementation of kexec_file_load,  making
change to the kimage_arch as below seems most reasonable.

Struct kimage_arch {

Add respective entries in dtb/fdt and read the same in the next kernel.
No changes to the purgatory should be needed since no kernel segments
are changed.

Is anyone already looking at this?
If not, I want to understand what’s the best approach for this is?

Prakhar Srivastava

^ permalink raw reply	[flat|nested] 1+ messages in thread

only message in thread, back to index

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-05-11  0:16 Carrying over the ima log during kexec_file_load prakhar srivastava

Linux-Integrity Archive on

Archives are clonable:
	git clone --mirror linux-integrity/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-integrity linux-integrity/ \
	public-inbox-index linux-integrity

Newsgroup available over NNTP:

AGPL code for this site: git clone public-inbox