From: Shuah Khan <shuahkhan@gmail.com> To: Matthew Garrett <mjg@redhat.com> Cc: linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org, linux-efi@vger.kernel.org, Josh Boyer <jwboyer@redhat.com> Subject: Re: [PATCH 10/11] acpi: Ignore acpi_rsdp kernel parameter in a secure boot environment Date: Tue, 4 Sep 2012 10:30:46 -0600 [thread overview] Message-ID: <CAKocOONvci0Otb9wDgw6he48HkCvvhh+TMrv63AwgZLtmv4_Kg@mail.gmail.com> (raw) In-Reply-To: <1346774117-2277-11-git-send-email-mjg@redhat.com> On Tue, Sep 4, 2012 at 9:55 AM, Matthew Garrett <mjg@redhat.com> wrote: > From: Josh Boyer <jwboyer@redhat.com> > > This option allows userspace to pass the RSDP address to the kernel. This > could potentially be used to circumvent the secure boot trust model. > We ignore the setting if we don't have the CAP_SECURE_FIRMWARE capability. Does this mean, acpi_rsdp is disabled on all current platforms that don't support CAP_SECURE_FIRMWARE? -- Shuah > > Signed-off-by: Josh Boyer <jwboyer@redhat.com> > --- > drivers/acpi/osl.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/acpi/osl.c b/drivers/acpi/osl.c > index 9eaf708..50c94e4 100644 > --- a/drivers/acpi/osl.c > +++ b/drivers/acpi/osl.c > @@ -246,7 +246,7 @@ early_param("acpi_rsdp", setup_acpi_rsdp); > acpi_physical_address __init acpi_os_get_root_pointer(void) > { > #ifdef CONFIG_KEXEC > - if (acpi_rsdp) > + if (acpi_rsdp && capable(CAP_SECURE_FIRMWARE)) > return acpi_rsdp; > #endif > > -- > 1.7.11.4 > > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2012-09-04 16:30 UTC|newest] Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-04 15:55 [RFC] First attempt at kernel secure boot support Matthew Garrett 2012-09-04 15:55 ` [PATCH 01/11] Secure boot: Add new capability Matthew Garrett 2012-09-04 15:55 ` [PATCH 02/11] PCI: Lock down BAR access in secure boot environments Matthew Garrett 2012-10-01 21:00 ` Pavel Machek 2012-09-04 15:55 ` [PATCH 03/11] x86: Lock down IO port " Matthew Garrett 2012-09-04 16:16 ` Alan Cox 2012-09-04 16:16 ` Matthew Garrett 2012-09-04 15:55 ` [PATCH 04/11] ACPI: Limit access to custom_method Matthew Garrett 2012-09-04 15:55 ` [PATCH 05/11] asus-wmi: Restrict debugfs interface Matthew Garrett 2012-09-04 16:12 ` Alan Cox 2012-09-04 16:13 ` Matthew Garrett 2012-09-04 15:55 ` [PATCH 06/11] Restrict /dev/mem and /dev/kmem in secure boot setups Matthew Garrett 2012-09-04 15:55 ` [PATCH 07/11] kexec: Disable in a secure boot environment Matthew Garrett 2012-09-04 20:13 ` Eric W. Biederman 2012-09-04 20:22 ` Matthew Garrett 2012-09-04 21:13 ` Eric W. Biederman 2012-09-04 21:27 ` Matthew Garrett 2012-09-04 22:12 ` Eric W. Biederman 2012-09-04 23:25 ` Matthew Garrett 2012-09-05 4:33 ` Eric W. Biederman 2012-09-05 5:16 ` Matthew Garrett 2012-09-05 7:00 ` Eric W. Biederman 2012-09-05 7:03 ` Matthew Garrett 2012-09-04 21:39 ` Alan Cox 2012-09-04 21:40 ` Matthew Garrett 2012-09-05 15:43 ` Roland Eggner 2012-09-05 15:46 ` Matthew Garrett 2012-09-05 21:13 ` Mimi Zohar 2012-09-05 21:41 ` Matthew Garrett 2012-09-05 21:49 ` Eric Paris 2012-09-04 15:55 ` [PATCH 08/11] Secure boot: Add a dummy kernel parameter that will switch on Secure Boot mode Matthew Garrett 2012-09-04 15:55 ` [PATCH 09/11] efi: Enable secure boot lockdown automatically when enabled in firmware Matthew Garrett 2012-09-04 15:55 ` [PATCH 10/11] acpi: Ignore acpi_rsdp kernel parameter in a secure boot environment Matthew Garrett 2012-09-04 16:30 ` Shuah Khan [this message] 2012-09-04 16:38 ` Matthew Garrett 2012-09-04 16:44 ` Shuah Khan 2012-09-04 20:37 ` Alan Cox 2012-09-04 20:37 ` Matthew Garrett 2012-09-04 20:50 ` Josh Boyer 2012-09-04 15:55 ` [PATCH 11/11] SELinux: define mapping for new Secure Boot capability Matthew Garrett 2012-09-04 16:08 ` [RFC] First attempt at kernel secure boot support Alan Cox 2012-09-04 16:12 ` Matthew Garrett 2012-10-01 21:07 ` Pavel Machek
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=CAKocOONvci0Otb9wDgw6he48HkCvvhh+TMrv63AwgZLtmv4_Kg@mail.gmail.com \ --to=shuahkhan@gmail.com \ --cc=jwboyer@redhat.com \ --cc=linux-efi@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-security-module@vger.kernel.org \ --cc=mjg@redhat.com \ --subject='Re: [PATCH 10/11] acpi: Ignore acpi_rsdp kernel parameter in a secure boot environment' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).