forked from pool/shim-leap
Chun-Yi Lee
bc6b6ed6d2
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)
Since shim needs a "stable" environment to reproduce the binary to match the signature from UEFI CA, it's difficult to maintain shim in Tumbleweed due to the nature of a rolling release distro. Instead of compiling shim for Tumbleweed, we directly import the binary the latest stable Leap release to maintain a stable and reproducible shim binary.