<br><br><div class="gmail_quote">2012/10/28 Kevin Kofler <span dir="ltr"><<a href="mailto:kevin.kofler@chello.at" target="_blank">kevin.kofler@chello.at</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5">Joshua C. wrote:<br>
> Over the last months there have been many patches to the rawhide-kernel<br>
> and rawhide-grub2 packages that aim to make those compatible with the M$<br>
> requirements for secure boot. Those locked down many user space<br>
> capabilities. However I still haven't seen any single "magic" switch that<br>
> can disable all this crap at once during compilation. As a result I cannot<br>
> port grub2 and the rawhide kernel to the current f17. I can simply<br>
> recompile the packages against f17 but all those lockups will still stay<br>
> in place :-(<br>
><br>
> Can someone point me to this switch (option, parameter, etc) so that I can<br>
> recomile and strip down those packages of all this crap?<br>
<br>
</div></div>AIUI, those lockdowns are supposed to only apply if Restricted ("Secure")<br>
Boot is supported by and enabled in the BIOS (or rather, the UEFI firmware;<br>
traditional BIOSes don't have that misfeature).<br>
<span class="HOEnZb"><font color="#888888"><br>
Kevin Kofler<br>
</font></span><br></blockquote></div><br clear="all">I see but is there a general switch do disable those even if secure boot is set to enable in the uefi firmware?<br><br>Honestly looking into the latest patch applied to the rawhide-kernel, I cannot see any indication that those lockups occur only if secure boot is set in the uefi firmware. They just lock out the user space regardless of what the uefi says...<br>
<br>-- <br>--joshua<br>