Linked by Elv13 on Sun 17th Jun 2012 10:35 UTC
Thread beginning with comment 522509
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.





Member since:
2010-02-18
For the time being, you will be able to disable secureboot in the UEFI menu somewhere. Fedora's issue with that solution is that UEFI isn't standardized, so they can't tell their customers 3 simple steps to unlock the device.
There's a NIST paper on securing systems which also includes firmware level attacks. I'd expect that secureboot has something to do with that rather than licensing concerns - they might need to lock that area down to be able to pass the next level Common Criteria certification.
The issue is also more pressing with UEFI than with BIOS since UEFI is so much more powerful than BIOS - you can load rather arbitrarily sized 32bit modules (built by a modern C compiler), which have access to everything a modern OS provides (threads, networking, plenty of memory). With "UEFI Shell" they basically admitted that UEFI _is_ an Operating System (whose main purpose - for now - is to load another OS).
This cozy environment simplifies attacks somewhat compared with the old BIOS situation.