Does this mean this is now a non-issue?
Thanks in advance.
Does this mean this is now a non-issue?
Thanks in advance.
If your OS doesn't allow arbitrary code to be run on the raw machine (so a chain of trust on executables), microsoft provides a signing service. This is a problem for linux, due to the way it allows any code to run privileged. This is a problem because if a generic linux kernel was signed, it could be used to bypass secureboot (since it allows you to run any code, and it would be trusted).
Some distros are looking at disabling all these features, so that their distro image can be signed. This would disable all third-party modules, and disallow other features (that most people probably don't use anyway).
This specific post is about an a key management program, that allows a user to install their own keys, so they can sign their own linux image. A simpler option allows you to put your machine in another mode that disables secureboot. Like the UEFI configuration option, this is a roadblock to new users, who want something to "just work". So unfortunately yes, it's still an issue.