[Bug 1596238] Re: NTFS Module not signed
Colin Watson
cjwatson at canonical.com
Sun Jun 26 11:39:02 UTC 2016
Reassigning since the decision of which modules are built into the image
to be signed is in fact in the grub2 source package. (grub2-signed is
just a delivery vehicle.)
** Package changed: grub2-signed (Ubuntu) => grub2 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/1596238
Title:
NTFS Module not signed
Status in grub2 package in Ubuntu:
New
Bug description:
Hi, as per the response on question #295452
(https://answers.launchpad.net/ubuntu/+source/grub2-signed/+question/295452),
I would like to have the NTFS module added to the signed binary.
In addition, it may be worth looking into testing to see if the Grub2
module signing subsystem can be used to sign the modules themselves,
instead of having one monolithic signed module that only supports a
subset of modules for Secure Boot.
The bug reporting guidelines 1 and 2 don't really apply in this
specific case, as it doesn't matter which version is used.
3) On a secure-boot enabled machine, while in the grub2 console, I run
'insmod ntfs' expecting it to load the ntfs module.
4) Secure boot refuses to load the module as it is not signed.
Referencing previous bug #1104627
(https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1104627) as
well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1596238/+subscriptions
More information about the foundations-bugs
mailing list