From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Chris Jones <chrisjones@spin.net.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: UEFI and custom kernel
Date: Wed, 27 Jun 2012 00:19:25 +0100 [thread overview]
Message-ID: <20120627001925.56e350f8@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <4FEA4102.2080900@spin.net.au>
On Wed, 27 Jun 2012 09:08:50 +1000
Chris Jones <chrisjones@spin.net.au> wrote:
> I've been following the news on UEFI and Secureboot pretty closely.
> Currently Ubuntu, Fedora and OpenSUSE have pretty in-depth discussion
> going on the mailing lists about it all.
>
> Although my technical knowledge about UEFI is pretty vague at current, I
> know a little bit of what it's about.
For x86 the UEFI "secure" boot requirement is that the user can disable
secure boot. For ARM it is that the user *cannot* disable secure boot.
So in the PC space at least it's "business as usual" providing you jump
that hoop, and hopefully with the tools sorted it'll be viable to sign
your own kernels and use your own keys.
Alan
next prev parent reply other threads:[~2012-06-26 23:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 23:08 Chris Jones
2012-06-26 23:19 ` Alan Cox [this message]
2012-06-26 23:18 ` Chris Jones
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=20120627001925.56e350f8@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=chrisjones@spin.net.au \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®