mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Jones <chrisjones@spin.net.au>
To: linux-kernel@vger.kernel.org
Subject: Re: UEFI and custom kernel
Date: Wed, 27 Jun 2012 09:18:27 +1000	[thread overview]
Message-ID: <4FEA4343.7080008@spin.net.au> (raw)
In-Reply-To: <20120627001925.56e350f8@pyramind.ukuu.org.uk>

Alan Cox wrote:
> 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 

Thanks Alan. I never realized that for x86 based hardware, nothing would 
change once disabled. In fact, I was not even aware that it could be 
disabled to begin with. Thank you.


Regards

-- 
		Chris Jones @ kernel.devproject@gmail.com
                           and oracle.kerneldev@gmail.com

OpenSUSE Linux x86_64 (PC)|Android (Smartphone)|Windows 7 (Laptop)|Windows XP (Gaming)
Linux kernel developer|Solaris kernel developer|Lead Developer of SDL|Lead Developer of Nest Linux
Gamer and Emulator nut|Web Services|Digital Imaging Services
Controllers: Rapier V2 Gaming mouse|Logitech Precision|PS3 controller|XB360 controller|Logitech Attack 3 j/stick
Emulators: Fusion|Gens|ZSNES|Project64|PCSX-R|Stella|WinVICE|WinUAE|DOSBox


      reply	other threads:[~2012-06-26 23:20 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
2012-06-26 23:18   ` Chris Jones [this message]

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=4FEA4343.7080008@spin.net.au \
    --to=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®