mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.ibm.com>
To: Paul Moore <paul@paul-moore.com>, linux-integrity@vger.kernel.org
Cc: "Mickaël Salaün" <mic@digikod.net>,
	roberto.sassu@huawei.com, linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org, "Jeff Xu" <jeffxu@chromium.org>,
	"Kees Cook" <kees@kernel.org>,
	audit@vger.kernel.org
Subject: Re: [PATCH v2] ima: instantiate the bprm_creds_for_exec() hook
Date: Thu, 05 Dec 2024 22:10:36 -0500	[thread overview]
Message-ID: <b6dc4d8b23b822638ab676055809503060c0bca2.camel@linux.ibm.com> (raw)
In-Reply-To: <282573d0ea82ac71c8305d0c8cc89083@paul-moore.com>

On Thu, 2024-12-05 at 19:30 -0500, Paul Moore wrote:
> On Dec  4, 2024 Mimi Zohar <zohar@linux.ibm.com> wrote:
> > 
> > Like direct file execution (e.g. ./script.sh), indirect file execution
> > (e.g. sh script.sh) needs to be measured and appraised.  Instantiate
> > the new security_bprm_creds_for_exec() hook to measure and verify the
> > indirect file's integrity.  Unlike direct file execution, indirect file
> > execution is optionally enforced by the interpreter.
> > 
> > Differentiate kernel and userspace enforced integrity audit messages.
> > 
> > Co-developed-by: Roberto Sassu <roberto.sassu@huawei.com>
> > Signed-off-by: Roberto Sassu <roberto.sassu@huawei.com>
> > Signed-off-by: Mimi Zohar <zohar@linux.ibm.com>
> > ---
> > Changelog v3:
> > - Mickael: add comment ima_bprm_creds_for_exec(), minor code cleanup,
> >   add Co-developed-by tag.
> > 
> > Changelog v2:
> > - Mickael: Use same audit messages with new audit message number
> > - Stefan Berger: Return boolean from is_bprm_creds_for_exec()
> > 
> >  include/uapi/linux/audit.h            |  1 +
> >  security/integrity/ima/ima_appraise.c | 27 +++++++++++++++++++++++--
> >  security/integrity/ima/ima_main.c     | 29 +++++++++++++++++++++++++++
> >  3 files changed, 55 insertions(+), 2 deletions(-)
> > 
> > diff --git a/include/uapi/linux/audit.h b/include/uapi/linux/audit.h
> > index 75e21a135483..826337905466 100644
> > --- a/include/uapi/linux/audit.h
> > +++ b/include/uapi/linux/audit.h
> > @@ -161,6 +161,7 @@
> >  #define AUDIT_INTEGRITY_RULE	    1805 /* policy rule */
> >  #define AUDIT_INTEGRITY_EVM_XATTR   1806 /* New EVM-covered xattr */
> >  #define AUDIT_INTEGRITY_POLICY_RULE 1807 /* IMA policy rules */
> > +#define AUDIT_INTEGRITY_DATA_CHECK  1808 /* Userspace enforced data integrity */
> 
> I worry that "DATA_CHECK" is a bit vague, should we change the name so
> that there is some hint of either userspace enforcement or
> AT_EXECVE_CHECK?
> 
> What about AUDIT_INTEGRITY_DATA_USER?

The emphasis should be on userspace - AUDIT_INTEGRITY_USERSPACE.

Mimi

  reply	other threads:[~2024-12-06  3:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-04 19:25 Mimi Zohar
2024-12-04 19:27 ` Mimi Zohar
2024-12-06  0:30 ` Paul Moore
2024-12-06  3:10   ` Mimi Zohar [this message]
2024-12-10 16:34     ` Mickaël Salaün
2024-12-10 16:47       ` Mimi Zohar
  -- strict thread matches above, loose matches on Subject: below --
2024-12-03 23:34 Mimi Zohar
2024-12-04 10:15 ` Mickaël Salaün
2024-12-04 14:57   ` Mimi Zohar
2024-12-04 17:47     ` Mickaël Salaün
2024-12-04 19:01 ` Stefan Berger
2024-12-05 10:53   ` Mickaël Salaün
2024-12-05 15:44 ` Stefan Berger

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=b6dc4d8b23b822638ab676055809503060c0bca2.camel@linux.ibm.com \
    --to=zohar@linux.ibm.com \
    --cc=audit@vger.kernel.org \
    --cc=jeffxu@chromium.org \
    --cc=kees@kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=mic@digikod.net \
    --cc=paul@paul-moore.com \
    --cc=roberto.sassu@huawei.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

all inboxes | Powered by JetHome®