From: Mimi Zohar <zohar@linux.ibm.com>
To: "Guozihua (Scott)" <guozihua@huawei.com>,
dmitry.kasatkin@gmail.com, paul@paul-moore.com,
jmorris@namei.org, serge@hallyn.com
Cc: linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org,
Janne Karhunen <janne.karhunen@gmail.com>,
Roberto Sassu <roberto.sassu@huawei.com>
Subject: Re: [PATCH v5 2/2] ima: Handle -ESTALE returned by ima_filter_rule_match()
Date: Thu, 03 Nov 2022 09:15:45 -0400 [thread overview]
Message-ID: <30ac558a35a0551f50dc49a834755beb1ab2d593.camel@linux.ibm.com> (raw)
In-Reply-To: <b2949b3d-c370-8a41-fe7c-9f175abd4f71@huawei.com>
On Wed, 2022-11-02 at 09:42 +0800, Guozihua (Scott) wrote:
> > As I only see an IMA measurement policy rule being loaded for
> > "unlabeled_t" and not "user_home_t", should I assume that an IMA
> > measurement rule already exists for "user_home_t"?
>
> There wasn't a rule for user_home_t. These scripts demonstrate that
> during a selinux policy reload, IMA would measure files that is not in
> the range of it's LSM based rules. Which is the issue I am trying to fix.
>
> In this test, we only have one rule for measuring files of type
> unlabeled_t. However, during selinux policy reload, file of user_home_t
> is also measured.
Thanks, Scott. After tweaking the scripts for my system, I was able to
reproduce the bug. This patch set is now queued in next-integrity.
--
thanks,
Mimi
next prev parent reply other threads:[~2022-11-03 13:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 12:58 [PATCH v5 0/2] ima: Handle -ESTALE returned by ima_filter_rule_match() GUO Zihua
2022-09-21 12:58 ` [PATCH v5 1/2] ima: Simplify ima_lsm_copy_rule GUO Zihua
2022-09-21 12:58 ` [PATCH v5 2/2] ima: Handle -ESTALE returned by ima_filter_rule_match() GUO Zihua
2022-09-22 11:09 ` Mimi Zohar
2022-09-23 4:01 ` Guozihua (Scott)
2022-09-23 11:19 ` Mimi Zohar
2022-09-24 6:05 ` Guozihua (Scott)
2022-09-28 14:11 ` Mimi Zohar
2022-10-04 14:19 ` Roberto Sassu
2022-10-18 8:43 ` Guozihua (Scott)
2022-10-19 1:07 ` Mimi Zohar
2022-10-19 7:17 ` Guozihua (Scott)
2022-10-28 8:36 ` Guozihua (Scott)
2022-11-01 22:15 ` Mimi Zohar
2022-11-02 1:42 ` Guozihua (Scott)
2022-11-03 13:15 ` Mimi Zohar [this message]
2022-11-14 3:31 ` Guozihua (Scott)
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=30ac558a35a0551f50dc49a834755beb1ab2d593.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=guozihua@huawei.com \
--cc=janne.karhunen@gmail.com \
--cc=jmorris@namei.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=roberto.sassu@huawei.com \
--cc=serge@hallyn.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).