forked from pool/shim
caused by buggy firmware when Secure Boot is disabled It is impossible for the db to be empty while Secure Boot is enabled. If the db is empty, the installation behavior will be treated the same as when Secure Boot is disabled. We allow the shim installation process to continue and display a message reminding the user to add the appropriate certificate. (bsc#1259096)
Description
No description provided
Languages
Shell
83.2%
Perl
16.8%