> because they are heavily promoted as a security/safety feature, You can build such features without baking the keys into the hardware. You can have an open

> because they are heavily promoted as a security/safety feature, You can build such features without baking the keys into the hardware. You can have an open security module where changing the key simply makes everything that has been previously secured by it unreadable. That way a user can load his custom keys and firmware if he wants to. You can cascade that dependency down the secure boot chain by mixing some secret from the module into the HDD decryption for example. Only vendor lock-in (e.g. windows RT) and DRM require hardcoded keys.