From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: Christoph Hellwig <hch@lst.de>, Al Viro <viro@zeniv.linux.org.uk>
Cc: Jan Kara <jack@suse.cz>, Jeff Layton <jlayton@redhat.com>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
linux-fsdevel@vger.kernel.org,
linux-ima-devel@lists.sourceforge.net,
linux-security-module@vger.kernel.org
Subject: [RFC PATCH 0/4] ima: filesystems not mounted with i_version
Date: Wed, 16 Aug 2017 13:30:16 -0400 [thread overview]
Message-ID: <1502904620-20075-1-git-send-email-zohar@linux.vnet.ibm.com> (raw)
IMA measures a file, verifies a file's integrity, and caches the
results. On filesystems with MS_I_VERSION enabled, IMA can detect
file changes and cause them to be re-measured and verified. On
filesystems without MS_I_VERSION enabled, files are measured and
verified just once.
Currently users either have to look at the source code or test
to determine if the file system supports i_version. Even if the
file system supports i_version, there is no guarantee that the
filesystem was actually mounted with the i_version flag.
This patch set emits warning messages when filesystems are not
mounted with i_version support. This patch set defines two new post
LSM hooks named security_sb_post_new_mount and
security_sb_post_remount, with their corresponding IMA functions.
Questions:
- IMA can call out directly to the IMA functions, without having to
define these LSM hooks. Is there a need for these LSM hooks?
- do_new_mount() creates a new vfsmount. If there is a way of accessing
this new vfsmount from the caller do_mount(), we would only need one
new LSM hook and corresponding IMA hook.
Mimi
Mimi Zohar (4):
security: define new LSM sb_post_new_mount hook
ima: define new ima_sb_post_new_mount hook
security: define a new LSM sb_post_remount hook
ima: define a new ima_sb_post_remount hook
fs/namespace.c | 5 ++++
include/linux/ima.h | 14 +++++++++
include/linux/lsm_hooks.h | 16 ++++++++++
include/linux/security.h | 10 +++++++
security/integrity/ima/ima_main.c | 62 +++++++++++++++++++++++++++++++++++++++
security/security.c | 15 ++++++++++
6 files changed, 122 insertions(+)
--
2.7.4
next reply other threads:[~2017-08-16 17:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 17:30 Mimi Zohar [this message]
2017-08-16 17:30 ` [RFC PATCH 1/4] security: define new LSM sb_post_new_mount hook Mimi Zohar
2017-08-16 17:30 ` [RFC PATCH 2/4] ima: define new ima_sb_post_new_mount hook Mimi Zohar
2017-08-16 19:24 ` Casey Schaufler
2017-08-16 20:59 ` Mimi Zohar
2017-08-17 2:39 ` [Linux-ima-devel] " James Morris
2017-12-07 12:26 ` Jeff Layton
2017-12-07 14:35 ` Mimi Zohar
2017-12-07 14:50 ` Jeff Layton
2017-12-07 15:08 ` Mimi Zohar
2017-12-07 15:09 ` Jeff Layton
2017-12-15 21:13 ` Jeff Layton
2017-08-16 17:30 ` [RFC PATCH 3/4] security: define a new LSM sb_post_remount hook Mimi Zohar
2017-08-16 17:30 ` [RFC PATCH 4/4] ima: define a new ima_sb_post_remount hook Mimi Zohar
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=1502904620-20075-1-git-send-email-zohar@linux.vnet.ibm.com \
--to=zohar@linux.vnet.ibm.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=jlayton@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-ima-devel@lists.sourceforge.net \
--cc=linux-security-module@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).