From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: herbert@gondor.hengli.com.au
Cc: linux-crypto <linux-crypto@vger.kernel.org>,
linux-security-module@vger.kernel.org,
Dmitry Kasatkin <dmitry.kasatkin@intel.com>,
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: Tue, 20 Sep 2011 09:24:28 -0400 [thread overview]
Message-ID: <1316525069.3189.4.camel@localhost.localdomain> (raw)
In-Reply-To: <cover.1315921427.git.dmitry.kasatkin@intel.com>
On Tue, 2011-09-13 at 17:20 +0300, Dmitry Kasatkin wrote:
> Hello,
>
> Changes to version 2.0:
> - MPI patch has been split to smaller in order to go to mailing lists.
> First 2 patches include only source and header files which are needed
> to build ksign verification. Headers and sources are split just to
> meet 100k kernel.org limit.
> Last patch adds all rest soures from original ported MPI library.
>
> Changes to version 1.1:
> - GnuPG MPI library has been refactored with lindent and checkpatch errors
> and warnings has been fixed.
> - creation of evm keyring has been remove. It is done now in user space.
> - related ksign and evm patches has been squashed.
> - patch descriptions has been updated.
>
> As EVM patches were recently merged to security-testing-2.6#next,
> it is a good time to resend evm signature verification patches for active
> discussion. Last time I forgot --cc linux-crypto. Here it is.
>
> This patchset introduces digital signature extensions for the IMA/EVM kernel
> integrity subsystem and is applied on the top of the EVM patches posted to
> LSM mailing list earlier.
Hi Herbert
Back in March 2011, in preparation for EVM, Dmitry posted the GnuPG MPI
library patch here on linux-crypto. The reason given for not upstreaming
the MPI library, at the time, was for lack of an in kernel user
(http://www.mail-archive.com/linux-crypto@vger.kernel.org/msg05613.html).
With the recent merging of the EVM patches in linux-next, via
security-testing-2.6/#next, that is changing. Any chance of re-opening
the discussion?
thanks,
Mimi
next prev parent reply other threads:[~2011-09-20 13:28 UTC|newest]
Thread overview: 15+ 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 ` Mimi Zohar [this message]
2011-09-26 7:33 ` [RFC v2.1 0/6] evm: digital signature verification extension Kasatkin, Dmitry
2011-09-26 23:15 ` James Morris
2011-09-28 15:37 ` Kasatkin, Dmitry
2011-09-29 0:14 ` Herbert Xu
2011-09-29 0:42 ` James Morris
2011-09-29 12:13 ` Kasatkin, Dmitry
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=1316525069.3189.4.camel@localhost.localdomain \
--to=zohar@linux.vnet.ibm.com \
--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 \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox