From: Mimi Zohar <zohar@linux.ibm.com>
To: linux-integrity@vger.kernel.org
Cc: Mimi Zohar <zohar@linux.ibm.com>,
roberto.sassu@huawei.com, Stefan Berger <stefanb@linux.ibm.com>,
Petr Vorel <pvorel@suse.cz>
Subject: [PATCH 0/2] ima: limit both open-writers and ToMToU violations
Date: Wed, 19 Feb 2025 11:21:29 -0500 [thread overview]
Message-ID: <20250219162131.416719-1-zohar@linux.ibm.com> (raw)
Each time a file in policy, that is already opened for write, is opened
for read an open-writers integrity violation audit message is emitted
and a violation record is added to the IMA measurement list, even if an
open-writers violation has already been recorded.
Similalry each time a file in policy, that is already opened for read,
is opened for write a Time-of-Measure-Time-of-Use (ToMToU) integrity
violation audit message is emitted and a violation record is added to
the IMA measurement list, even if a ToMToU violation has already been
recorded.
Minimize the violations in the audit log and the IMA measurement list.
Mimi Zohar (2):
ima: limit the number of open-writers integrity violations
ima: limit the number of ToMToU integrity violations
security/integrity/ima/ima.h | 1 +
security/integrity/ima/ima_main.c | 16 ++++++++++++----
2 files changed, 13 insertions(+), 4 deletions(-)
--
2.48.1
next reply other threads:[~2025-02-19 16:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 16:21 Mimi Zohar [this message]
2025-02-19 16:21 ` [PATCH 1/2] ima: limit the number of open-writers integrity violations Mimi Zohar
2025-02-20 15:24 ` Stefan Berger
2025-02-20 18:26 ` Petr Vorel
2025-02-21 8:18 ` Petr Vorel
2025-02-21 16:56 ` Roberto Sassu
2025-02-19 16:21 ` [PATCH 2/2] ima: limit the number of ToMToU " Mimi Zohar
2025-02-20 15:24 ` Stefan Berger
2025-02-20 18:27 ` Petr Vorel
2025-02-21 8:18 ` Petr Vorel
2025-02-21 17:36 ` Roberto Sassu
2025-02-26 19:19 ` Mimi Zohar
2025-02-27 8:34 ` Roberto Sassu
2025-02-21 16:49 ` [PATCH 0/2] ima: limit both open-writers and ToMToU violations Roberto Sassu
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=20250219162131.416719-1-zohar@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=linux-integrity@vger.kernel.org \
--cc=pvorel@suse.cz \
--cc=roberto.sassu@huawei.com \
--cc=stefanb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox