<story><title>Grub2 security update renders system unbootable</title><url>https://bugzilla.redhat.com/show_bug.cgi?id=1861977</url></story><parent_chain></parent_chain><comment><author>peteri</author><text>I assume this is related to this from yesterday
&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=23990075&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=23990075&lt;/a&gt;
 Which is about revoking secure boot keys</text></comment>
<story><title>Grub2 security update renders system unbootable</title><url>https://bugzilla.redhat.com/show_bug.cgi?id=1861977</url></story><parent_chain></parent_chain><comment><author>Wowfunhappy</author><text>There was a story on HN last night from Debian where they  laid out this issue, and basically stated &amp;quot;Yes, this security update is going to render some systems unbootable, here is why we&amp;#x27;re doing it anyway.&amp;quot;&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.debian.org&amp;#x2F;security&amp;#x2F;2020-GRUB-UEFI-SecureBoot&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.debian.org&amp;#x2F;security&amp;#x2F;2020-GRUB-UEFI-SecureBoot&amp;#x2F;&lt;/a&gt;&lt;p&gt;Stability is important, especially when it comes to unbootable machines—but I don&amp;#x27;t quite know what anyone was supposed to do here. If a user has secure boot enabled, the OS has to assume that the user wants&amp;#x2F;needs security at that level of the chain—and it is therefor responsible for ensuring the chain&amp;#x27;s integrity. In this case, there was no way to do that without some machines (temporarily) failing to boot.&lt;p&gt;What would have been a better way to handle this?</text></comment>