Thanks for reporting this.
We aren't currently using SecureBoot for security reasons. Our
SecureBoot support is only to allow installation on computers that have
it enabled by default.
If we ever in the future rely on SecureBoot as a security measure, I
agree a warning would be appropriate.
** Information type changed from Private Security to Public Security
** Changed in: grub2-signed (Ubuntu)
Status: New => Triaged
** Changed in: grub2-signed (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401532
Title:
GRUB's Secure Boot implementation loads unsigned kernel without
warning
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1401532/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
