public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: Dongsu Park <dongsu@kinvolk.io>, LKML <linux-kernel@vger.kernel.org>
Cc: Alban Crequy <alban@kinvolk.io>,
	Miklos Szeredi <miklos@szeredi.hu>,
	Seth Forshee <seth.forshee@canonical.com>
Subject: Re: [PATCH 0/2] turn on force option for FUSE in builtin policies
Date: Tue, 16 Jan 2018 06:23:51 -0500	[thread overview]
Message-ID: <1516101831.6607.98.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <CANxcAMv-p_1Wu=83zhy5-fkmDqxF3jzwfhsD+3Q6iCZ+FiJSSg@mail.gmail.com>

On Tue, 2018-01-16 at 12:09 +0100, Dongsu Park wrote:
> Hi,
> 
> On Thu, Jan 11, 2018 at 8:51 PM, Dongsu Park <dongsu@kinvolk.io> wrote:
> > In case of FUSE filesystem, cached integrity results in IMA could be
> > reused, when the userspace FUSE process has changed the
> > underlying files. To be able to avoid such cases, we need to turn on
> > the force option in builtin policies, for actions of measure and
> > appraise. Then integrity values become re-measured and re-appraised.
> > In that way, cached integrity results won't be used.
> 
> Since yesterday Alban and I have been working on a different approach
> that does not depend on IMA rules, nor fsmagic. Please see:
> https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1587390.html
> 
> If that's ok, I'm ready to discard this patchset.

You dropped a number of people involved in this discussion and mailing
lists.  Please post the proposed patch inline as an RFC, cc'ing the
same people, those involved in the discussion, and previous mailing
lists, including LSM, integrity, and fsdevel.

thanks,

Mimi

  reply	other threads:[~2018-01-16 11:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-11 19:51 [PATCH 0/2] turn on force option for FUSE in builtin policies Dongsu Park
2018-01-11 19:51 ` [PATCH 1/2] fs/fuse: move SUPER_MAGIC definitions to linux/magic.h Dongsu Park
2018-01-11 19:51 ` [PATCH 2/2] ima: turn on force option for FUSE in builtin policies Dongsu Park
2018-01-12 15:33   ` Mimi Zohar
2018-01-14 19:09   ` kbuild test robot
2018-01-16 10:47     ` Dongsu Park
2018-01-15 14:48 ` [PATCH 0/2] " Christoph Hellwig
2018-01-15 16:32   ` Mimi Zohar
2018-01-15 17:18     ` Christoph Hellwig
2018-01-15 21:00       ` Mimi Zohar
2018-01-16 10:41   ` [PATCH] ima,fuse: introduce new fs flag FS_NO_IMA_CACHE Alban Crequy
2018-01-16 11:26     ` Alban Crequy
2018-01-16 11:35       ` Mimi Zohar
2018-01-16 11:09 ` [PATCH 0/2] turn on force option for FUSE in builtin policies Dongsu Park
2018-01-16 11:23   ` Mimi Zohar [this message]
2018-01-16 14:05     ` Dongsu Park

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=1516101831.6607.98.camel@linux.vnet.ibm.com \
    --to=zohar@linux.vnet.ibm.com \
    --cc=alban@kinvolk.io \
    --cc=dongsu@kinvolk.io \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=seth.forshee@canonical.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