[ Reply to This | Parent | # ]

• UEFI and Secure Boot - less Freedom is No Freedom - Authored by: Anonymous on Monday, June 25 2012 @ 06:36 PM EDT

I'm a little confused over driver signing. Once the system is booted do the drivers need to be signed for a device to work?

One bit that I have grasped from this massive spec is that the UEFI scheme is entirely modular, and includes the ability to load "pre-boot-environment" driver files for particular devices, sort of like the "initrd" concept when booting Linux. If, for example, a hardware vendor comes out with a new device (call it a disk) that is not supported by the resident UEFI code, they can also provide a driver file to work with UEFI that will allow the device to be accessed and used during boot (which would let the machine boot from that "disk"). I believe that's the "driver signing" that they're talking about.

Still reading...

---
"When I say something, I put my name next to it." -- Isaac Jaffe, "Sports Night"

[ Reply to This | Parent | # ]

• I think the controller/formatter must also be signed. - Authored by: jesse on Tuesday, June 26 2012 @ 09:01 AM EDT

[ Reply to This | Parent | # ]

• Canonical anounced they'll do exactly that [n/t] - Authored by: Anonymous on Tuesday, June 26 2012 @ 07:01 PM EDT