From: Mimi Zohar <zohar@linux.ibm.com>
To: Petr Vorel <pvorel@suse.cz>,
linux-integrity@vger.kernel.org, ltp@lists.linux.it,
Stefan Berger <stefanb@linux.ibm.com>
Cc: Roberto Sassu <roberto.sassu@huaweicloud.com>
Subject: Re: [LTP] [RFC PATCH 3/3] ima: additional ToMToU violation tests
Date: Thu, 20 Feb 2025 16:15:51 -0500 [thread overview]
Message-ID: <63e4b47ebb2729f36111badcaae589a36eb24422.camel@linux.ibm.com> (raw)
In-Reply-To: <20250220184631.GA2713854@pevik>
Hi Petr,
On Thu, 2025-02-20 at 19:46 +0100, Petr Vorel wrote:
> Is it this considered as a security feature? If yes, than failures on vanilla
> kernel are ok, we just need to later add kernel hashes to let testers know about
> missing backports. If it's a feature (not to be backported) we should test new
> feature only on newer kernels.
I posted these LTP patches as RFC since the kernel patches themselves haven't been
upstreamed. I'm still waiting for some kernel patch reviews. Posting these LTP patches
might help with that.
Having multiple open-writers or ToMToU violations doesn't provide any benefit in terms of
attestation. It just clutters the audit log and the IMA measurement list. Not extending
the TPM would be a performance improvement. I'm not sure it would be classified as a
security feature or bug fix.
Mimi
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-02-20 21:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 16:00 [LTP] [RFC PATCH 1/3] Update validate() to support multiple violations Mimi Zohar
2025-02-20 16:00 ` [LTP] [RFC PATCH 2/3] ima: additional open-writer violation tests Mimi Zohar
2025-02-20 19:02 ` Petr Vorel
2025-02-20 16:00 ` [LTP] [RFC PATCH 3/3] ima: additional ToMToU " Mimi Zohar
2025-02-20 18:16 ` Petr Vorel
2025-02-20 18:46 ` Petr Vorel
2025-02-20 21:15 ` Mimi Zohar [this message]
2025-02-20 18:59 ` Mimi Zohar
2025-02-20 19:13 ` Petr Vorel
2025-02-20 20:22 ` Mimi Zohar
2025-02-20 21:18 ` Mimi Zohar
2025-02-20 21:43 ` Petr Vorel
2025-02-21 2:07 ` Mimi Zohar
2025-02-21 8:16 ` Petr Vorel
2025-02-24 18:48 ` Mimi Zohar
2025-02-25 7:45 ` Petr Vorel
2025-02-20 18:50 ` [LTP] [RFC PATCH 1/3] Update validate() to support multiple violations Petr Vorel
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=63e4b47ebb2729f36111badcaae589a36eb24422.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=linux-integrity@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
--cc=roberto.sassu@huaweicloud.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