It doesn't affect me but there's more to security these days then giving up root access. There are systems with guarantees even if you have physical access and root access and this breaks those guarantees.

Sending out patches not fully tested is never good though.

Only Secure Boot, which is an optional feature of the UEFI specification was initially proposed by Microsoft. The PE/COFF format of EFI images is described in a Microsoft document, but this document is public and the format is unambiguously specified, which is a very good thing. It is also good that the file system of the ESP be FAT (also, initially from Microsoft) as it is not only well specified and stable but also very simple. The advantages and disadvantages of EFI over BIOS are stated in https://en.wikipedia.org/wiki/Unifie...ware_Interface, the details are in https://uefi.org/sites/default/files..._8_A_Feb14.pdf.

FYI the new Slint installer will have an "auto" aka "guided" mode helping to share a drive with another (already installed) system, but only if the installer booted in EFI mode and the drive has a GPT, as this is way safer than BIOS and a DOS partition table in this use case, and allows to make both systems truly independent of each other.

Anyway in a few years you won't find motherboards with an hybrid firmware, so better be prepared

3 members found this post helpful.

Let me get this right, you have issues with some unspecified threads where quality of discussion does not meet your expectations?
Meanwhile, creating a new thread warning Slackers that your Debian system may have crashed is totally fine in your book.
Not only that, but in the title you make it look like Slackware had shipped a bad patch, and in the post it's just a warning that Slackware may or may not ship a bad patch in the future.

What if windows users came here to post clickbait titles, do you think that would help regenerate the forum?
It'd help with keeping the forum on-topic, right?

I'm not going to derail any further, just wanted to say you did actually quote my post there so I assumed you're trying to make it my problem.

1 members found this post helpful.

Slackware uses signed binaries[1] for booting?

Last I checked, it doesn't, then this shocking security flaw on Grub is not our problem. It does not make our UEFI boot more insecure as already it is.




[1] like in: kernels signed with developer certificates issued by Microsoft, Inc. which should be the only things accepted for execution by bootloader.

1 members found this post helpful.

Ah, no. Really, my off-hand statement was generic, directed to nobody in particular but everybody generically. I only wanted to warn Slackers and Pat of the potential breakage. A simple public service announcement (PSA). I wrote my off-hand generic statement because I did not want the thread to devolve, but you seem well on the way of doing just that.

Are you a native English speaker? Or simply someone with poor reading skills?

Rule of thumb: when exchanging pleasantries begins, it's time to let the thread rest in peace.

2 members found this post helpful.

No, how is that even relevant to the title of the thread?
Title is clickbait, it does not say whether or not Slackware has actually shipped the "bad-grub-security-patch"
Just saying threads about Debian breakage should go into Debian sub, if quality of the forum in general is a main concern here.
If not, then why do we have different subforums anyway? We could all just post bugs in general forum.

Mods, please lock this thread. Thank you.

Thread closed at OPs request.