From: Mimi Zohar <zohar@linux.ibm.com>
To: linux-integrity@vger.kernel.org
Cc: Mimi Zohar <zohar@linux.ibm.com>,
Mickael Salaun <mic@digikod.net>, Steve Grubb <sgrubb@redhat.com>,
Jann Horn <jannh@google.com>,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] ima: extending IMA policy to support interpreters
Date: Wed, 29 Apr 2020 09:38:41 -0400 [thread overview]
Message-ID: <1588167523-7866-1-git-send-email-zohar@linux.ibm.com> (raw)
On file open, the kernel has no way of differentiating between files
containing data and those with code that will be executed. Only the
interpreter knows how the file will be used. To bridge this gap, this
patch set extends the IMA policy language:
- to identify files with the executable mode bit set
- to support the new file open flag MAY_OPENEXEC introduced by Mickael
Salaun's "[PATCH v3 0/5] Add support for RESOLVE_MAYEXEC" patch set.
Mimi
Mimi Zohar (2):
ima: add policy support for identifying file execute mode bit
ima: add policy support for the new file open MAY_OPENEXEC flag
Documentation/ABI/testing/ima_policy | 7 ++++---
security/integrity/ima/ima_main.c | 3 ++-
security/integrity/ima/ima_policy.c | 33 +++++++++++++++++++++++++++------
3 files changed, 33 insertions(+), 10 deletions(-)
--
2.7.5
next reply other threads:[~2020-04-29 13:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 13:38 Mimi Zohar [this message]
2020-04-29 13:38 ` [PATCH 1/2] ima: add policy support for identifying file execute mode bit Mimi Zohar
2020-04-29 17:22 ` Lakshmi Ramasubramanian
2020-04-29 13:38 ` [PATCH 2/2] ima: add policy support for the new file open MAY_OPENEXEC flag Mimi Zohar
2020-04-29 17:22 ` Lakshmi Ramasubramanian
2020-04-29 21:24 ` kbuild test robot
2020-04-30 13:42 ` Mimi Zohar
2020-04-30 14:26 ` Mickaël Salaün
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=1588167523-7866-1-git-send-email-zohar@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=jannh@google.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
--cc=sgrubb@redhat.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;
as well as URLs for NNTP newsgroup(s).