From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: Dmitry Kasatkin <dmitry.kasatkin@gmail.com>
Cc: linux-ima-devel@lists.sourceforge.net,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org,
Dmitry Kasatkin <dmitry.kasatkin@huawei.com>
Subject: Re: [PATCHv3 0/6] integrity: few EVM patches
Date: Thu, 05 Nov 2015 13:35:09 -0500 [thread overview]
Message-ID: <1446748509.2570.143.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <cover.1445539084.git.dmitry.kasatkin@huawei.com>
On Thu, 2015-10-22 at 21:49 +0300, Dmitry Kasatkin wrote:
> Hi,
>
> IMA module provides functionality to load x509 certificates into the
> trusted '.ima' keyring. This is patchset adds the same functionality
> to the EVM as well. Also it provides functionality to set EVM key from
> the kernel crypto HW driver. This is an update for the patchset which was
> previously sent for review few months ago. Please refer to the patch
> descriptions for details.
Other than patch "evm: define EVM key max and min sizes", which prevents
existing EVM keys from being loaded, the patches are queued
http://git.kernel.org/cgit/linux/kernel/git/zohar/linux-integrity.git/next-for-4.5.
Thanks!
Mimi
> BR,
>
> Dmitry
>
> Dmitry Kasatkin (6):
> integrity: define '.evm' as a builtin 'trusted' keyring
> evm: load x509 certificate from the kernel
> evm: enable EVM when X509 certificate is loaded
> evm: provide a function to set EVM key from the kernel
> evm: define EVM key max and min sizes
> evm: reset EVM status when file attributes changes
>
> include/linux/evm.h | 10 +++++++
> security/integrity/Kconfig | 11 ++++++++
> security/integrity/digsig.c | 14 ++++++++--
> security/integrity/evm/Kconfig | 17 ++++++++++++
> security/integrity/evm/evm.h | 3 +++
> security/integrity/evm/evm_crypto.c | 54 ++++++++++++++++++++++++++++++-------
> security/integrity/evm/evm_main.c | 32 +++++++++++++++++++---
> security/integrity/evm/evm_secfs.c | 12 +++------
> security/integrity/iint.c | 1 +
> security/integrity/ima/Kconfig | 5 +++-
> security/integrity/ima/ima.h | 12 ---------
> security/integrity/ima/ima_init.c | 2 +-
> security/integrity/integrity.h | 13 ++++++---
> 13 files changed, 146 insertions(+), 40 deletions(-)
>
prev parent reply other threads:[~2015-11-05 18:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 18:49 [PATCHv3 0/6] integrity: few EVM patches Dmitry Kasatkin
2015-10-22 18:49 ` [PATCHv3 1/6] integrity: define '.evm' as a builtin 'trusted' keyring Dmitry Kasatkin
2015-10-23 13:05 ` Petko Manolov
2015-10-23 13:40 ` Dmitry Kasatkin
2015-10-23 18:43 ` Mimi Zohar
2015-10-24 9:35 ` Petko Manolov
2015-10-22 18:49 ` [PATCHv3 2/6] evm: load x509 certificate from the kernel Dmitry Kasatkin
2015-10-22 18:49 ` [PATCHv3 3/6] evm: enable EVM when X509 certificate is loaded Dmitry Kasatkin
2015-10-23 18:31 ` Mimi Zohar
2015-10-26 19:18 ` Dmitry Kasatkin
2015-10-22 18:49 ` [PATCHv3 4/6] evm: provide a function to set EVM key from the kernel Dmitry Kasatkin
2015-10-23 18:30 ` Mimi Zohar
2015-10-26 19:18 ` Dmitry Kasatkin
2015-10-22 18:49 ` [PATCHv3 5/6] evm: define EVM key max and min sizes Dmitry Kasatkin
2015-10-22 18:49 ` [PATCHv3 6/6] evm: reset EVM status when file attributes changes Dmitry Kasatkin
2015-11-05 18:35 ` Mimi Zohar [this message]
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=1446748509.2570.143.camel@linux.vnet.ibm.com \
--to=zohar@linux.vnet.ibm.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=dmitry.kasatkin@huawei.com \
--cc=linux-ima-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
/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.