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] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 10 Sep 2013 15:52:24 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Vivek Goyal <vgoyal@...hat.com>
CC:	linux-kernel@...r.kernel.org,
	linux-security-module@...r.kernel.org, kexec@...ts.infradead.org,
	akpm@...ux-foundation.org, zohar@...ux.vnet.ibm.com,
	d.kasatkin@...sung.com, ebiederm@...ssion.com,
	matthew.garrett@...ula.com, Borislav Petkov <bp@...en8.de>
Subject: Re: [PATCH 15/16] bootparam: Pass acpi_rsdp pointer in bootparam

On 09/10/2013 02:44 PM, Vivek Goyal wrote:
> Currently kexec does not enables EFI and its tables in second kernel. Hence
> acpi rsdp root pointer is passed on command line. But secureboot does not trust
> acpi_rsdp on command line as kernel can execute some of the code as retrieved
> by following acpi_rsdp and root can modify command line. So in secureboot
> mode we ignore acpi_rsdp on command line.
> 
> Start passing it in bootparams for the time being. kexec-tools will prepare
> the bootparams and put acpi_rsdp pointer there.
> 
> Peter Jones suggested that scan all ACPI memory for acpi_rsdp if EFI is
> not enabled. This probably is a better fix and most likely this patch will
> change and adopt that approach down the line.
> 
> In fact if we figure out how to make UEFI run time calls in second kernel,
> we will not need acpi_rsdp at all.
> 

Borislav Petkov has been working on a fixed mapping of UEFI memory,
which should allow UEFI runtime calls across kexec.

	-hpa


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ