slac-in-the-box |
09-23-2020 12:47 PM |
Quote:
Originally Posted by enorbet
(Post 6167234)
Again, what does Secure Boot actually bring to the table as a Benefit and at what Cost? That is by definition, The Bottom Line - Profit or Loss?.
|
I own and provision x86_64 and arm64 devices, both which have secure-boot (mainline u-boot can store secure-boot-keys); linux kernel can uefi boot with efi_boot_stub configured... so one way to configure booting that works everywhere is handy, though not profitable, per se.
I fixed an apple guy's imac's time machine's mess: I put my portable ssd with slackware64 on it, (which has /boot/efi/EFI/BOOT/BOOTX64.efi), and held the option key during startup, and behold, the portable ssd was available, and I was able to run his imac on my ssd, then mount his imac's internal drive, and use rsync to merge all the copies of copies inside itself that his time machine setup had created... he was really grateful and gave me some bucks (profit). If he had had a secure-boot computer, it would have been more challenging, as this thread discloses, and I would have missed out.
Having a portable slackware installation that can boot a customer's secure-boot device leads to profit! Even though, from a security point of view, secure-boot might not have helped slackware or linux--in fact it created a hindrance by needing more work to make it work--nevertheless, having a secure-boot equipped slackware allows access to those devices that would otherwise be hindered, and that access can be profitable!
|