Hacker Newsnew | past | comments | ask | show | jobs | submit | zaolin's commentslogin

The whole step moving forward into the UEFI direction on Client Computing Systems (laptops, desktop) is the right way.

Even if I dislike the UEFI specification and existing implementations, the spec is more than 24 years old. It might fulfill its purpose as a bootloader/OS interface.

The UEFI BDS interface, the one the most people see and the operating system interfaces, is now standardized for many operating systems and OEMs, making it easier to integrate and maintain. It is finally possible to use standard security mechanisms (verified, measured boot) to secure your device. So we can use such technologies to ensure device security reasonably as we do in my corp www.immu.ne

The custom certificate provisioning is a mess and hard to use, but that can be possibly made easy by projects like: https://github.com/Foxboron/sbctl

I don't believe the UEFI interface is beneficial for data-center or embedded devices. The UEFI BDS interface was developed for client platforms and required physical presence. It leads to complexity in the DC and embedded world. I feel a more suitable approach would be www.linuxboot.org which is already used by many Hyperscalers and Embedded companies.

That's my 50 cents about the story. My background, I am coreboot developer and security architect.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: