From: Stefan Berger <stefanb@linux.ibm.com>
To: Mimi Zohar <zohar@linux.ibm.com>, linux-integrity@vger.kernel.org
Cc: "Mickaël Salaün" <mic@digikod.net>,
roberto.sassu@huawei.com, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, "Jeff Xu" <jeffxu@chromium.org>,
"Kees Cook" <kees@kernel.org>, "Paul Moore" <paul@paul-moore.com>,
audit@vger.kernel.org
Subject: Re: [PATCH v2] ima: instantiate the bprm_creds_for_exec() hook
Date: Thu, 5 Dec 2024 10:44:23 -0500 [thread overview]
Message-ID: <2a449edc-a642-4e6b-a55f-2eb03e5b15ce@linux.ibm.com> (raw)
In-Reply-To: <20241203233424.287880-1-zohar@linux.ibm.com>
On 12/3/24 6:34 PM, Mimi Zohar wrote:
> Like direct file execution (e.g. ./script.sh), indirect file exection
> (e.g. sh script.sh) needs to be measured and appraised. Instantiate
> the new security_bprm_creds_for_exec() hook to measure and verify the
> indirect file's integrity. Unlike direct file execution, indirect file
> execution is optionally enforced by the interpreter.
>
> Differentiate kernel and userspace enforced integrity audit messages.
>
> Signed-off-by: Roberto Sassu <roberto.sassu@huawei.com>
> Signed-off-by: Mimi Zohar <zohar@linux.ibm.com>
Tested-by: Stefan Berger <stefanb@linux.ibm.com>
next prev parent reply other threads:[~2024-12-05 15:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 23:34 [PATCH v2] ima: instantiate the bprm_creds_for_exec() hook Mimi Zohar
2024-12-04 10:15 ` Mickaël Salaün
2024-12-04 14:57 ` Mimi Zohar
2024-12-04 17:47 ` Mickaël Salaün
2024-12-04 19:01 ` Stefan Berger
2024-12-05 10:53 ` Mickaël Salaün
2024-12-05 15:44 ` Stefan Berger [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-04 19:25 Mimi Zohar
2024-12-04 19:27 ` Mimi Zohar
2024-12-06 0:30 ` Paul Moore
2024-12-06 3:10 ` Mimi Zohar
2024-12-10 16:34 ` Mickaël Salaün
2024-12-10 16:47 ` 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=2a449edc-a642-4e6b-a55f-2eb03e5b15ce@linux.ibm.com \
--to=stefanb@linux.ibm.com \
--cc=audit@vger.kernel.org \
--cc=jeffxu@chromium.org \
--cc=kees@kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
--cc=paul@paul-moore.com \
--cc=roberto.sassu@huawei.com \
--cc=zohar@linux.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.