Bug 223820 - modinfo does not show whether a module is signed or not (and by whom)
modinfo does not show whether a module is signed or not (and by whom)
Product: Fedora
Classification: Fedora
Component: module-init-tools (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Jon Masters
Depends On:
Blocks: 224596
  Show dependency treegraph
Reported: 2007-01-22 12:04 EST by Jan Iven
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-30 02:13:58 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jan Iven 2007-01-22 12:04:28 EST
Description of problem:

/sbin/modinfo gives no indication of whether a module has been signed or not.
This would be a nice addition (perhaps even with information on the signing key
actually used). Given that RedHat/Fedora modules that come inside the kernel RPM
get automagically signed with a temporary key, one could even imagine keeping
that key and using it to verify module integrity (RPM checksums do something
similar, but the in-kernel algorithm is different).

Version-Release number of selected component (if applicable):
Comment 1 Jon Masters 2007-08-20 02:23:37 EDT
This has been fixed upstream and is included in the latest RHEL5. I will also
ensure the updated module-init-tools is available - though it was in rawhide
when I last checked.

Comment 2 Jon Masters 2007-10-30 02:13:58 EDT
There's a fix upstream, it's in the latest Fedora packages.

Note You need to log in before you can comment on or make changes to this bug.