linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.ibm.com>
To: Michael Peters <michael00peters@gmail.com>
Cc: amir73il@gmail.com, linux-fsdevel@vger.kernel.org,
	linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-unionfs@vger.kernel.org, miklos@szeredi.hu
Subject: Re: [RFC PATCH] ima: differentiate overlay, pivot_root, and other pathnames
Date: Wed, 10 Nov 2021 12:39:28 -0500	[thread overview]
Message-ID: <6213c2f886637f824b14c67de7f9534349417b49.camel@linux.ibm.com> (raw)
In-Reply-To: <CAJQqANe-SFvPEEQcQrGUsn9n1aFybCOQaofvnmS+qZGvnNh7nQ@mail.gmail.com>

On Wed, 2021-11-10 at 10:28 -0500, Michael Peters wrote:

> This looks good, but would be even better if the flag that controlled
> this was settable in the ima_policy. That's much easier to work with
> in a lot of DevOps toolchains and pipelines and is similar to how the
> other ima configuration is done.

Thanks, Michael.  Agreed, which is one of the reasons for posting this
patch as an RFC.  The other reason is that it is an incomplete
solution, since it doesn't address mount namespaces.  Any suggestions
for addressing mount namespaces would be appreciated. Assuming there is
a benefit for a partial solution, I'll add the per policy rule support.

thanks,

Mimi


       reply	other threads:[~2021-11-10 17:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJQqANe-SFvPEEQcQrGUsn9n1aFybCOQaofvnmS+qZGvnNh7nQ@mail.gmail.com>
2021-11-10 17:39 ` Mimi Zohar [this message]
2021-11-08 17:01 [RFC PATCH] ima: differentiate overlay, pivot_root, and other pathnames 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=6213c2f886637f824b14c67de7f9534349417b49.camel@linux.ibm.com \
    --to=zohar@linux.ibm.com \
    --cc=amir73il@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=michael00peters@gmail.com \
    --cc=miklos@szeredi.hu \
    /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).