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):
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.
There's a fix upstream, it's in the latest Fedora packages.