From: Mimi Zohar <zohar@linux.ibm.com>
To: Coiby Xu <coxu@redhat.com>
Cc: linux-integrity@vger.kernel.org,
Roberto Sassu <roberto.sassu@huawei.com>,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
Eric Snowberg <eric.snowberg@oracle.com>,
Paul Moore <paul@paul-moore.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
"open list:SECURITY SUBSYSTEM"
<linux-security-module@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ima: don't clear IMA_DIGSIG flag when setting non-IMA xattr
Date: Wed, 10 Sep 2025 08:21:33 -0400 [thread overview]
Message-ID: <6f2b7320b691669068dda110c29c25f8aae2f244.camel@linux.ibm.com> (raw)
In-Reply-To: <wwcnoevou44eoe3ner4oegtdsdg46tlvwidu3ynobs7huac7ae@ljivg5ksohxv>
On Wed, 2025-09-10 at 09:36 +0800, Coiby Xu wrote:
> On Mon, Sep 08, 2025 at 04:58:05PM -0400, Mimi Zohar wrote:
> > On Mon, 2025-09-08 at 10:53 -0400, Mimi Zohar wrote:
> > > Hi Coiby,
> > >
> > > On Mon, 2025-09-08 at 19:12 +0800, Coiby Xu wrote:
> > > > >
> > > > > Even without an IMA appraise policy, the security xattrs are written out to the
> > > > > filesystem, but the IMA_DIGSIG flag is not cached.
> > > >
> > > > It seems I miss some context for the above sentence. If no IMA policy is
> > > > configured, no ima_iint_cache will be created. If you mean non-appraisal
> > > > policy, will not caching IMA_DIGSIG flag cause any problem?
> > >
> > > Sorry. What I was trying to say is that your test program illustrates the
> > > problem both with or without any of the boot command line options as you
> > > suggested - "ima_appraise=fix evm=fix ima_policy=appraise_tcb". Writing some
> > > other security xattr is a generic problem, whether the file is in policy or not,
> > > whether IMA or EVM are in fix mode or not. The rpm-plugin-ima should install
> > > the IMA signature regardless.
> >
> > My mistake. An appraise policy indeed needs to be defined for the file
> > signature to be replaced with a file hash.
>
> Thanks for the clarification! rpm-plugin-ima does try to install IMA
> signature as shown from the following strace output,
Agreed. I was referring to the SELinux label, which would be installed for new
files, but not necessarily re-installed on existing files. The test program
simplified testing. Thank you.
Mimi
next prev parent reply other threads:[~2025-09-10 12:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 4:25 [PATCH] ima: don't clear IMA_DIGSIG flag when setting non-IMA xattr Coiby Xu
2025-09-05 2:41 ` Mimi Zohar
2025-09-08 11:12 ` Coiby Xu
2025-09-08 14:53 ` Mimi Zohar
2025-09-08 20:58 ` Mimi Zohar
2025-09-10 1:36 ` Coiby Xu
2025-09-10 12:21 ` Mimi Zohar [this message]
2025-09-15 4:06 ` Coiby Xu
2025-09-15 6:07 ` Coiby Xu
2025-09-08 10:58 ` [PATCH v2] " Coiby Xu
2025-09-10 12:21 ` Mimi Zohar
2025-09-15 6:03 ` Coiby Xu
2025-09-15 5:55 ` [PATCH v3] ima: don't clear IMA_DIGSIG flag when setting or removing " Coiby Xu
2025-09-22 17:11 ` 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=6f2b7320b691669068dda110c29c25f8aae2f244.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=coxu@redhat.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=eric.snowberg@oracle.com \
--cc=jmorris@namei.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@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