From: Rusty Russell <rusty@ozlabs.org>
To: "Kasatkin\, Dmitry" <dmitry.kasatkin@intel.com>,
James Morris <jmorris@namei.org>
Cc: linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, zohar@linux.vnet.ibm.com,
David Howells <dhowells@redhat.com>
Subject: Re: [RFC][PATCH v1 0/2] integrity: module integrity verification
Date: Wed, 08 Feb 2012 03:43:01 +1030 [thread overview]
Message-ID: <87zkcuh8iq.fsf@rustcorp.com.au> (raw)
In-Reply-To: <CALLzPKZSWSp6r-5e1c1Z6qOH6C0DcOz=LHJ20Y468SQE6UU1ww@mail.gmail.com>
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?
Cheers,
Rusty.
next prev parent reply other threads:[~2012-02-07 20:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 20:25 [RFC][PATCH v1 0/2] integrity: module integrity verification Dmitry Kasatkin
2012-02-01 20:25 ` [RFC][PATCH v1 1/2] integrity: add ima_module_check hook Dmitry Kasatkin
2012-02-01 20:25 ` [RFC][PATCH v1 2/2] integrity: verify module integrity based on signature Dmitry Kasatkin
2012-02-06 1:51 ` [RFC][PATCH v1 0/2] integrity: module integrity verification James Morris
2012-02-06 6:59 ` Kasatkin, Dmitry
2012-02-07 17:13 ` Rusty Russell [this message]
2012-02-07 21:18 ` Kasatkin, Dmitry
2012-02-07 23:39 ` Rusty Russell
2012-02-08 13:45 ` Mimi Zohar
2012-02-08 14:02 ` Kasatkin, Dmitry
2012-02-08 18:02 ` Rusty Russell
2012-02-13 16:20 ` David Howells
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zkcuh8iq.fsf@rustcorp.com.au \
--to=rusty@ozlabs.org \
--cc=dhowells@redhat.com \
--cc=dmitry.kasatkin@intel.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=zohar@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.