From: Petr Vorel <pvorel@suse.cz>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: ltp@lists.linux.it, linux-integrity@vger.kernel.org
Subject: Re: [PATCH v2 1/8] IMA: Add TCB policy as an example for ima_measurements.sh
Date: Fri, 3 Jan 2025 12:57:43 +0100 [thread overview]
Message-ID: <20250103115743.GA211314@pevik> (raw)
In-Reply-To: <fa7b251e0b7966e9d32117996f4ae8390bc4f6cc.camel@linux.ibm.com>
Hi Mimi,
> Hi Petr,
> On Fri, 2024-12-13 at 23:20 +0100, Petr Vorel wrote:
> > Taken from IMA docs [1], removed dont_measure fsmagic=0x1021994 (tmpfs)
> > as suggested by Mimi.
> > [1] https://ima-doc.readthedocs.io/en/latest/ima-policy.html#ima-tcb
> > Signed-off-by: Petr Vorel <pvorel@suse.cz>
> After thinking about it some more, anyone interested in constraining the
> "measure func=FILE_CHECK" rules based on LSM labels to avoid integrity
> violations would need to reboot the system anyway. [1]
> For this reason, please include the new dont_measure tmpfs rule as proposed in
> "[PATCH] ima: limit the builtin 'tcb' dont_measure tmpfs policy rule". [2]
Sure, I'll add in v3:
dont_measure fsmagic=0x1021994 func=FILE_CHECK
Kind regards,
Petr
> [1] Integrity violations -
> https://ima-doc.readthedocs.io/en/latest/event-log-format.html#template-data-hash
> [2]
> https://lore.kernel.org/linux-integrity/20241230142333.1309623-2-zohar@linux.ibm.com/
> thanks,
> Mimi
WARNING: multiple messages have this Message-ID (diff)
From: Petr Vorel <pvorel@suse.cz>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: linux-integrity@vger.kernel.org, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2 1/8] IMA: Add TCB policy as an example for ima_measurements.sh
Date: Fri, 3 Jan 2025 12:57:43 +0100 [thread overview]
Message-ID: <20250103115743.GA211314@pevik> (raw)
In-Reply-To: <fa7b251e0b7966e9d32117996f4ae8390bc4f6cc.camel@linux.ibm.com>
Hi Mimi,
> Hi Petr,
> On Fri, 2024-12-13 at 23:20 +0100, Petr Vorel wrote:
> > Taken from IMA docs [1], removed dont_measure fsmagic=0x1021994 (tmpfs)
> > as suggested by Mimi.
> > [1] https://ima-doc.readthedocs.io/en/latest/ima-policy.html#ima-tcb
> > Signed-off-by: Petr Vorel <pvorel@suse.cz>
> After thinking about it some more, anyone interested in constraining the
> "measure func=FILE_CHECK" rules based on LSM labels to avoid integrity
> violations would need to reboot the system anyway. [1]
> For this reason, please include the new dont_measure tmpfs rule as proposed in
> "[PATCH] ima: limit the builtin 'tcb' dont_measure tmpfs policy rule". [2]
Sure, I'll add in v3:
dont_measure fsmagic=0x1021994 func=FILE_CHECK
Kind regards,
Petr
> [1] Integrity violations -
> https://ima-doc.readthedocs.io/en/latest/event-log-format.html#template-data-hash
> [2]
> https://lore.kernel.org/linux-integrity/20241230142333.1309623-2-zohar@linux.ibm.com/
> thanks,
> Mimi
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-01-03 11:57 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 22:20 [PATCH v2 0/8] LTP tests: load predefined policy, enhancements Petr Vorel
2024-12-13 22:20 ` [LTP] " Petr Vorel
2024-12-13 22:20 ` [PATCH v2 1/8] IMA: Add TCB policy as an example for ima_measurements.sh Petr Vorel
2024-12-13 22:20 ` [LTP] " Petr Vorel
2024-12-31 16:01 ` Mimi Zohar
2024-12-31 16:01 ` [LTP] " Mimi Zohar
2025-01-03 11:57 ` Petr Vorel [this message]
2025-01-03 11:57 ` Petr Vorel
2024-12-13 22:20 ` [PATCH v2 2/8] ima_setup.sh: Allow to load predefined policy Petr Vorel
2024-12-13 22:20 ` [LTP] " Petr Vorel
2024-12-30 20:43 ` Mimi Zohar
2024-12-30 20:43 ` [LTP] " Mimi Zohar
2024-12-31 10:00 ` Petr Vorel
2024-12-31 10:00 ` [LTP] " Petr Vorel
2024-12-31 14:54 ` Mimi Zohar
2024-12-31 14:54 ` [LTP] " Mimi Zohar
2025-01-03 12:09 ` Petr Vorel
2025-01-03 12:09 ` [LTP] " Petr Vorel
2025-01-03 12:18 ` Petr Vorel
2025-01-03 12:18 ` [LTP] " Petr Vorel
2025-01-03 15:31 ` Mimi Zohar
2025-01-03 15:31 ` [LTP] " Mimi Zohar
2024-12-13 22:20 ` [PATCH v2 3/8] tst_test.sh: IMA: Allow to disable LSM warnings and use it for IMA Petr Vorel
2024-12-13 22:20 ` [LTP] " Petr Vorel
2024-12-13 22:20 ` [PATCH v2 4/8] ima_setup: Print warning when policy not readable Petr Vorel
2024-12-13 22:20 ` [LTP] " Petr Vorel
2024-12-13 22:20 ` [PATCH v2 5/8] ima_kexec.sh: Move checking policy if readable to ima_setup.sh Petr Vorel
2024-12-13 22:20 ` [LTP] " Petr Vorel
2024-12-13 22:20 ` [PATCH v2 6/8] IMA: Add example policy for ima_violations.sh Petr Vorel
2024-12-13 22:20 ` [LTP] " Petr Vorel
2024-12-31 3:43 ` Mimi Zohar
2024-12-31 3:43 ` [LTP] " Mimi Zohar
2024-12-31 10:40 ` Petr Vorel
2024-12-31 10:40 ` [LTP] " Petr Vorel
2024-12-31 12:23 ` Petr Vorel
2024-12-31 12:23 ` [LTP] " Petr Vorel
2024-12-31 15:34 ` Mimi Zohar
2024-12-31 15:34 ` [LTP] " Mimi Zohar
2025-01-03 19:02 ` Petr Vorel
2025-01-03 19:02 ` [LTP] " Petr Vorel
2025-01-07 18:29 ` Mimi Zohar
2025-01-07 18:29 ` [LTP] " Mimi Zohar
2024-12-13 22:20 ` [PATCH v2 7/8] ima_violations.sh: Check for a required policy Petr Vorel
2024-12-13 22:20 ` [LTP] " Petr Vorel
2024-12-31 3:42 ` Mimi Zohar
2024-12-31 3:42 ` [LTP] " Mimi Zohar
2024-12-13 22:20 ` [PATCH v2 8/8] [RFC] ima_kexec.sh: Relax result on unreadable policy to TCONF Petr Vorel
2024-12-13 22:20 ` [LTP] " 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=20250103115743.GA211314@pevik \
--to=pvorel@suse.cz \
--cc=linux-integrity@vger.kernel.org \
--cc=ltp@lists.linux.it \
--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.