3 ms·
One possible solution to this problem is for the FSF itself -- or perhaps another non-profit organization with similar goals but a more flexible stance -- to ge
by cs702 14y ago
One possible solution to this problem is for the FSF itself -- or perhaps another non-profit organization with similar goals but a more flexible stance -- to get in the business of issuing Secure-Boot keys, backed by a public written policy of non-discriminatory key issuance. Such an organization could work with non-mainstream operating systems to get hardware vendors to adopt its keys. For example, Ubuntu and Red Hat could use keys issued by it.
All non-mainstream operating system projects would be able to request keys from this organization and boot without having to resort to tinkering in UEFI hardware from multiple vendors.
One can dream.
- sounds 14y agoJust assuming that the current UEFI working group agreed to this, the first problem arises when one of the key holders is compromised. As a possible scenario: what if the Windows 8 private signing key leaked because it was used in Terminal Server somehow - do you want the FSF revoking the Microsoft signing key, thus invalidating UEFI signed drivers (necessary for boot) from hundreds of OEM's? We can shortcut all this by supporting www.coreboot.org
- cs702 14y agosounds: coreboot.org is a worthwhile cause but unfortunately, for better or worse, whether we like it or not, most hardware vendors have decided to adopt UEFI.