From: James Morris <jmorris@namei.org>
To: Herbert Xu <herbert@gondor.hengli.com.au>
Cc: "Kasatkin, Dmitry" <dmitry.kasatkin@intel.com>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
linux-crypto <linux-crypto@vger.kernel.org>,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, dhowells@redhat.com,
Greg KH <greg@kroah.com>,
"Serge E. Hallyn" <serge.hallyn@canonical.com>
Subject: Re: [RFC v2.1 0/6] evm: digital signature verification extension
Date: Thu, 29 Sep 2011 10:42:46 +1000 (EST) [thread overview]
Message-ID: <alpine.LRH.2.00.1109291042290.21622@tundra.namei.org> (raw)
In-Reply-To: <20110929001424.GA17356@gondor.apana.org.au>
On Thu, 29 Sep 2011, Herbert Xu wrote:
> Well if James is OK with adding the user for this then I'm fine
> with adding the necessary infrastructure.
Are you happy with the API?
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2011-09-29 0:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 14:20 [RFC v2.1 0/6] evm: digital signature verification extension Dmitry Kasatkin
2011-09-13 14:20 ` [RFC v2.1 1/6] crypto: GnuPG based MPI lib - source files needed for ksign Dmitry Kasatkin
2011-09-13 14:20 ` [RFC v2.1 2/6] crypto: GnuPG based MPI lib - header " Dmitry Kasatkin
2011-09-13 14:20 ` [RFC v2.1 3/6] crypto: GnuPG based MPI lib - make " Dmitry Kasatkin
2011-09-13 14:20 ` [RFC v2.1 4/6] crypto: GnuPG based MPI lib - extra MPI sources Dmitry Kasatkin
2011-09-13 14:20 ` [RFC v2.1 5/6] crypto: ksign - digital signature verification support Dmitry Kasatkin
2011-09-13 14:20 ` [RFC v2.1 6/6] evm: " Dmitry Kasatkin
2011-09-20 13:24 ` [RFC v2.1 0/6] evm: digital signature verification extension Mimi Zohar
2011-09-26 7:33 ` Kasatkin, Dmitry
2011-09-26 23:15 ` James Morris
2011-09-28 15:37 ` Kasatkin, Dmitry
2011-09-28 15:37 ` Kasatkin, Dmitry
2011-09-29 0:14 ` Herbert Xu
2011-09-29 0:14 ` Herbert Xu
2011-09-29 0:42 ` James Morris [this message]
2011-09-29 12:13 ` Kasatkin, Dmitry
2011-10-04 19:04 ` Herbert Xu
2011-10-04 19:04 ` Herbert Xu
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=alpine.LRH.2.00.1109291042290.21622@tundra.namei.org \
--to=jmorris@namei.org \
--cc=dhowells@redhat.com \
--cc=dmitry.kasatkin@intel.com \
--cc=greg@kroah.com \
--cc=herbert@gondor.hengli.com.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge.hallyn@canonical.com \
--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.