From: Dmitry Kasatkin <dmitry.kasatkin@intel.com>
To: linux-security-module@vger.kernel.org
Cc: jmorris@namei.org, linux-kernel@vger.kernel.org,
zohar@linux.vnet.ibm.com
Subject: [RFC][PATCH v1 0/2] integrity: module integrity verification
Date: Wed, 1 Feb 2012 22:25:02 +0200 [thread overview]
Message-ID: <cover.1328122362.git.dmitry.kasatkin@intel.com> (raw)
Hi,
Here is another module verification patchset, which is based on the recently
upstreamed digital signature support used by EVM and IMA-appraisal.
The initial module verification code was dependent on IMA-appraisal and
was using security.ima extended attribute to store the signature.
Based on some feeback, it was decided to add the ability to store the
signature in a corresponding module signature file <module>.sig and also
make module checking no longer dependent on IMA-appraisal.
Having signature in a separate <module>.sig file allows to use it on filesystem,
which do not support extended attributes, e.g. network file system,
and also copying modules to target system from build system.
The initial module verification code was dependent on IMA-appraisal and
was using security.ima extended attribute to store the signature.
Based on some feeback it was decided to remove IMA dependency and also
add possibility to store the signature in the corresponding signature
file <module>.sig. It allows to use it on filesystems, which do not support
extended attributes and also allows copying of modules from build system to
the target for testing without extended attribute aware tools.
modprobe and insmod have been modified to read signature either from
extended attribute or signature file and pass it as a kernel module
parameter to load_module system call.
Signature generation is done using the same tool as for EVM/IMA: evm-utils.
These 2 patches are available on the top at #next-ima-module branch at
git://git.kernel.org/pub/scm/linux/kernel/git/kasatkin/linux-digsig.git
evm-utils and module-init-tools are available in linux-ima project GIT:
git://linux-ima.git.sourceforge.net / linux-ima/evm-utils
git://linux-ima.git.sourceforge.net / linux-ima/module-init-tools
- Dmitry
Dmitry Kasatkin (2):
integrity: add ima_module_check hook
integrity: verify module integrity based on signature
Documentation/ABI/testing/securityfs-module-check | 17 ++
include/linux/integrity.h | 10 +
kernel/module.c | 20 ++-
security/integrity/Kconfig | 11 +
security/integrity/Makefile | 1 +
security/integrity/module.c | 251 +++++++++++++++++++++
6 files changed, 305 insertions(+), 5 deletions(-)
create mode 100644 Documentation/ABI/testing/securityfs-module-check
create mode 100644 security/integrity/module.c
--
1.7.5.4
next reply other threads:[~2012-02-01 20:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 20:25 Dmitry Kasatkin [this message]
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
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=cover.1328122362.git.dmitry.kasatkin@intel.com \
--to=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.