From: ebiederm@xmission.com (Eric W. Biederman)
To: Mimi Zohar <zohar@linux.vnet.ibm.com>
Cc: Stef Bon <stefbon@gmail.com>,
linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-fsdevel@vger.kernel.org, Miklos Szeredi <miklos@szeredi.hu>,
Seth Forshee <seth.forshee@canonical.com>,
Dongsu Park <dongsu@kinvolk.io>, Alban Crequy <alban@kinvolk.io>,
"Serge E. Hallyn" <serge@hallyn.com>
Subject: Re: [PATCH v3 4/4] fuse: define the filesystem as untrusted
Date: Wed, 14 Mar 2018 11:17:33 -0500 [thread overview]
Message-ID: <877eqer5r6.fsf@xmission.com> (raw)
In-Reply-To: <1521032461.3547.404.camel@linux.vnet.ibm.com> (Mimi Zohar's message of "Wed, 14 Mar 2018 09:01:01 -0400")
Mimi Zohar <zohar@linux.vnet.ibm.com> writes:
> On Wed, 2018-03-14 at 08:52 +0100, Stef Bon wrote:
>> I do not have any comments about the patches but a question.
>> I completely agree that the files can change without the VFS knowing
>> about it, but isn't that in general the case with filesystems with a
>> backend shared with others (network fs's?).
>
> Right, the problem is not limited to fuse, but needs to be addressed
> before unprivileged fuse mounts are upstreamed.
>
> Alban's response to this question:
> https://marc.info/?l=linux-kernel&m=151784020321045&w=2
Which goes to why it is a flag that get's set.
All of this just needs a follow-up patch to update every filesystem
that does not meet ima's requirements.
Mimi I believe you said that the requirement is that all file changes
can be detected through the final __fput of a file that calls
ima_file_free.
Eric
WARNING: multiple messages have this Message-ID (diff)
From: ebiederm@xmission.com (Eric W. Biederman)
To: linux-security-module@vger.kernel.org
Subject: [PATCH v3 4/4] fuse: define the filesystem as untrusted
Date: Wed, 14 Mar 2018 11:17:33 -0500 [thread overview]
Message-ID: <877eqer5r6.fsf@xmission.com> (raw)
In-Reply-To: <1521032461.3547.404.camel@linux.vnet.ibm.com> (Mimi Zohar's message of "Wed, 14 Mar 2018 09:01:01 -0400")
Mimi Zohar <zohar@linux.vnet.ibm.com> writes:
> On Wed, 2018-03-14 at 08:52 +0100, Stef Bon wrote:
>> I do not have any comments about the patches but a question.
>> I completely agree that the files can change without the VFS knowing
>> about it, but isn't that in general the case with filesystems with a
>> backend shared with others (network fs's?).
>
> Right, the problem is not limited to fuse, but needs to be addressed
> before unprivileged fuse mounts are upstreamed.
>
> Alban's response to this question:
> https://marc.info/?l=linux-kernel&m=151784020321045&w=2
Which goes to why it is a flag that get's set.
All of this just needs a follow-up patch to update every filesystem
that does not meet ima's requirements.
Mimi I believe you said that the requirement is that all file changes
can be detected through the final __fput of a file that calls
ima_file_free.
Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-03-14 16:18 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 20:24 [PATCH v3 0/4] unverifiable file signatures Mimi Zohar
2018-03-08 20:24 ` Mimi Zohar
2018-03-08 20:24 ` [PATCH v3 1/4] ima: fail file signature verification on non-init mounted filesystems Mimi Zohar
2018-03-08 20:24 ` Mimi Zohar
2018-03-12 19:17 ` Serge E. Hallyn
2018-03-12 19:17 ` Serge E. Hallyn
2018-03-12 19:26 ` Serge E. Hallyn
2018-03-12 19:26 ` Serge E. Hallyn
2018-03-13 18:45 ` Eric W. Biederman
2018-03-13 18:45 ` Eric W. Biederman
2018-03-08 20:24 ` [PATCH v3 2/4] ima: re-evaluate files on privileged " Mimi Zohar
2018-03-08 20:24 ` Mimi Zohar
2018-03-12 19:18 ` Serge E. Hallyn
2018-03-12 19:18 ` Serge E. Hallyn
2018-03-13 19:24 ` Eric W. Biederman
2018-03-13 19:24 ` Eric W. Biederman
2018-03-08 20:24 ` [PATCH v3 3/4] ima: fail signature verification based on policy Mimi Zohar
2018-03-08 20:24 ` Mimi Zohar
2018-03-12 19:28 ` Serge E. Hallyn
2018-03-12 19:28 ` Serge E. Hallyn
2018-03-12 19:32 ` Mimi Zohar
2018-03-12 19:32 ` Mimi Zohar
2018-03-13 19:31 ` Eric W. Biederman
2018-03-13 19:31 ` Eric W. Biederman
2018-03-08 20:24 ` [PATCH v3 4/4] fuse: define the filesystem as untrusted Mimi Zohar
2018-03-08 20:24 ` Mimi Zohar
2018-03-12 19:29 ` Serge E. Hallyn
2018-03-12 19:29 ` Serge E. Hallyn
2018-03-13 14:46 ` Stefan Berger
2018-03-13 14:46 ` Stefan Berger
2018-03-14 14:27 ` Serge E. Hallyn
2018-03-14 14:27 ` Serge E. Hallyn
2018-03-14 14:37 ` Stefan Berger
2018-03-14 14:37 ` Stefan Berger
2018-03-13 19:32 ` Eric W. Biederman
2018-03-13 19:32 ` Eric W. Biederman
2018-03-19 11:57 ` Mimi Zohar
2018-03-19 11:57 ` Mimi Zohar
2018-03-19 11:57 ` Mimi Zohar
2018-03-14 7:52 ` Stef Bon
2018-03-14 7:52 ` Stef Bon
2018-03-14 13:01 ` Mimi Zohar
2018-03-14 13:01 ` Mimi Zohar
2018-03-14 16:17 ` Eric W. Biederman [this message]
2018-03-14 16:17 ` Eric W. Biederman
2018-03-14 17:50 ` Mimi Zohar
2018-03-14 17:50 ` Mimi Zohar
2018-03-14 17:50 ` Mimi Zohar
2018-03-14 18:08 ` Chuck Lever
2018-03-14 18:08 ` Chuck Lever
2018-03-14 19:46 ` Eric W. Biederman
2018-03-14 19:46 ` Eric W. Biederman
2018-03-14 20:34 ` Chuck Lever
2018-03-14 20:34 ` Chuck Lever
2018-03-14 21:42 ` Eric W. Biederman
2018-03-14 21:42 ` Eric W. Biederman
2018-03-14 22:53 ` Michael Halcrow
2018-03-14 22:53 ` Michael Halcrow
2018-03-15 21:24 ` Mimi Zohar
2018-03-15 21:24 ` Mimi Zohar
2018-03-15 21:24 ` Mimi Zohar
2018-03-15 10:07 ` Stef Bon
2018-03-15 10:07 ` Stef Bon
2018-03-15 13:53 ` Chuck Lever
2018-03-15 13:53 ` Chuck Lever
2018-03-15 22:05 ` Mimi Zohar
2018-03-15 22:05 ` Mimi Zohar
2018-03-13 19:40 ` [PATCH v3 0/4] unverifiable file signatures Eric W. Biederman
2018-03-13 19:40 ` Eric W. Biederman
2018-03-13 20:40 ` Mimi Zohar
2018-03-13 20:40 ` 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=877eqer5r6.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=alban@kinvolk.io \
--cc=dongsu@kinvolk.io \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=serge@hallyn.com \
--cc=seth.forshee@canonical.com \
--cc=stefbon@gmail.com \
--cc=zohar@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.