From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Mimi Zohar <zohar@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, linux-efi@vger.kernel.org
Subject: Re: [PATCH 07/11] kexec: Disable in a secure boot environment
Date: Wed, 5 Sep 2012 22:41:42 +0100 [thread overview]
Message-ID: <20120905214142.GA29288@srcf.ucam.org> (raw)
In-Reply-To: <1346879629.2054.22.camel@falcor.watson.ibm.com>
On Wed, Sep 05, 2012 at 05:13:49PM -0400, Mimi Zohar wrote:
> Normally capabilities provide additional permissions. So if you don't
> have the capability, an errno is returned. CAP_SYS_BOOT is a good
> example. With CAP_SECURE_FIRMWARE, it reads backwards - if not
> CAP_SECURE_FIRMWARE, return error. I think you want to invert the name
> to CAP_NOT_SECURE_FIRMWARE, CAP_NOT_SECURE_BOOT or perhaps
> CAP_UNSECURED_BOOT.
Yeah, I think renaming the cap is a given.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2012-09-05 21:41 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 [this message]
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
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=20120905214142.GA29288@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=zohar@linux.vnet.ibm.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.