On Sat, Oct 27, 2012 at 10:04 PM, Joshua C. joshua...@gmail.com wrote:
AIUI, those lockdowns are supposed to only apply if Restricted (Secure)
Boot is supported by and enabled in the BIOS (or rather, the UEFI
firmware;
traditional BIOSes don't have that misfeature).
Correct.
I see but is
On Sun, Oct 28, 2012 at 03:04:15AM +0100, Joshua C. wrote:
I see but is there a general switch do disable those even if secure boot is
set to enable in the uefi firmware?
No. That's kind of the point.
Honestly looking into the latest patch applied to the rawhide-kernel, I
cannot see any
2012/10/28 Matthew Garrett mj...@srcf.ucam.org
On Sun, Oct 28, 2012 at 03:04:15AM +0100, Joshua C. wrote:
I see but is there a general switch do disable those even if secure boot
is
set to enable in the uefi firmware?
No. That's kind of the point.
Honestly looking into the latest
Over the last months there have been many patches to the rawhide-kernel and
rawhide-grub2 packages that aim to make those compatible with the M$
requirements for secure boot. Those locked down many user space
capabilities. However I still haven't seen any single magic switch that
can disable all
Joshua C. wrote:
Over the last months there have been many patches to the rawhide-kernel
and rawhide-grub2 packages that aim to make those compatible with the M$
requirements for secure boot. Those locked down many user space
capabilities. However I still haven't seen any single magic switch
2012/10/28 Kevin Kofler kevin.kof...@chello.at
Joshua C. wrote:
Over the last months there have been many patches to the rawhide-kernel
and rawhide-grub2 packages that aim to make those compatible with the M$
requirements for secure boot. Those locked down many user space
capabilities.
On Oct 27, 2012, at 8:04 PM, Joshua C. joshua...@gmail.com wrote:
I see but is there a general switch do disable those even if secure boot is
set to enable in the uefi firmware?
If you're going to disable it for linux, you might as well disable it in the
firmware. There's little point in
