Re: [RFC][PATCH v1 0/2] integrity: module integrity verification

[Rusty Russell <rusty@ozlabs.org>]

On Tue, 7 Feb 2012 23:18:38 +0200, "Kasatkin, Dmitry" <dmitry.kasatkin@intel.com> wrote:
> On Tue, Feb 7, 2012 at 7:13 PM, Rusty Russell <rusty@ozlabs.org> wrote:
> > On Mon, 6 Feb 2012 08:59:00 +0200, "Kasatkin, Dmitry" <dmitry.kasatkin@intel.com> wrote:
> >> On Mon, Feb 6, 2012 at 3:51 AM, James Morris <jmorris@namei.org> wrote:
> >> > On Wed, 1 Feb 2012, Dmitry Kasatkin wrote:
> >> >
> >> >> Hi,
> >> >>
> >> >> Here is another module verification patchset, which is based on the recently
> >> >> upstreamed digital signature support used by EVM and IMA-appraisal.
> >> >
> >> > You should cc: Rusty on any changes to the module code.
> >> >
> >>
> >> Hello,
> >>
> >> Mimi already has pointed that out.
> >> I have sent him an email with the link..
> >
> > Thanks.
> >
> > Using an external signature (via cmdline arguments) is simple, at
> > least.  Not sure what the userspace side of this looks like?
> >
> 
> Hello,
> 
> There are couple of patches for modprobe and insmod...
> 
> You could see them on the top at:
> http://linux-ima.git.sourceforge.net/git/gitweb.cgi?p=linux-ima/module-init-tools.git;a=summary
> 
> It first tries to read signature from xattr, then from file...
> "modprobe -v" will show 'ima='  parameter with signature.
> 
> - Dmitry

The problem is that distributions tend to have two variants of modules:
stripped and unstripped.  Thus you may want to support multiple
signatures, any *one* of which may match.

I've cc'd the module-init-tools and libkmod maintainers for their
comments, too.

Cheers,
Rusty.