NTFS Module not signed

Bug #1596238 reported by Shawn Rose
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
grub2 (Ubuntu)
Fix Released
Undecided
Unassigned

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.

Revision history for this message
Colin Watson (cjwatson) wrote :

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.)

affects: grub2-signed (Ubuntu) → grub2 (Ubuntu)
Revision history for this message
Mate Kukri (mkukri) wrote :

NTFS is signed in the current grub2, although it is debatable whether or not it should be.

Changed in grub2 (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.