On Friday, April 7, 2017 at 11:15:46 AM UTC-4, cooloutac wrote: > On Tuesday, April 4, 2017 at 6:20:35 PM UTC-4, [email protected] wrote: > > On 04/04/2017 10:19 AM, cooloutac wrote: > > > > > > > > The hacking teams insyde bios exploit could only have been stopped with > > > secure boot. > > > > > Uhh no that isn't true, and again you're using microsoft's marketing > > name for something that is a generic technology (signing of kernel and > > important files) implemented in grub etc. > > > > On my libre coreboot system (not all coreboot is libre) I can use a > > signing key mechanism to sign kernels and load them with grub installed > > on my motherboards write-locked flash chip. > > > > > > Do you work for microsoft? > > Microsoft didn't create secure boot, intel did. They just tried to > monopolize it and failed. Tell all the major linux distros that they work > for Microsoft lol... > > I see you are Libre guy, that explains alot, but why ignore my comment > about what Richard Stallman says about "secure boot"? DOES Richard Stallman > work for windows!?!? haha...
What you are talking about is "restricted boot" as RMS calls it. not "secure boot". If you control the keys I don't see the problem. You are more worried about what could potentially happen. Even though prior predictions have been wrong. Its good to be aware of the potentials for abuse. But lets not claim abuse when it hasn't even happened yet. I mean I guess there are UEFI boards out there that don't let you disable secure boot or use custom keys? But I've never seen one. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d0f703fe-18df-4d64-95cf-0e7e8105bcc8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
