I would disagree. The idea is great; eliminate preboot malware by trusting the whole boot stack. It has a place in computing and I would like to see it be something easier to work with.
Pretty much everything about how it’s currently implemented is a mistake, I’ll agree with.
It is open, oddly enough. It’s just that nobody ships anything other than Microsoft’s keys. You can add your own. It’s just that it is a tedious, manual process.
UEFI doesn’t forbid you from implementing additional file systems, it just requires everyone to support UEFI-FAT.
iBoot for example supports booting from HFS volumes.
Everything about secure boot is a mistake.
I would disagree. The idea is great; eliminate preboot malware by trusting the whole boot stack. It has a place in computing and I would like to see it be something easier to work with.
Pretty much everything about how it’s currently implemented is a mistake, I’ll agree with.
More like who is implementing it. Take MS out of the picture and set it as an open standard.
It is open, oddly enough. It’s just that nobody ships anything other than Microsoft’s keys. You can add your own. It’s just that it is a tedious, manual process.
Microsoft has unofficial support for ext4 for their EFI partitions on their azure cloud, which in itself is a violation of their standard.
UEFI doesn’t forbid you from implementing additional file systems, it just requires everyone to support UEFI-FAT. iBoot for example supports booting from HFS volumes.