From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-integrity <linux-integrity@vger.kernel.org>,
linux-security-module <linux-security-module@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Dongsu Park <dongsu@kinvolk.io>, Alban Crequy <alban@kinvolk.io>,
Seth Forshee <seth.forshee@canonical.com>
Subject: Re: [PATCH] ima: define new policy condition based on the filesystem name
Date: Mon, 15 Jan 2018 11:40:07 -0500 [thread overview]
Message-ID: <1516034407.6607.26.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180115162726.GB15686@infradead.org>
On Mon, 2018-01-15 at 08:27 -0800, Christoph Hellwig wrote:
> On Mon, Jan 15, 2018 at 11:20:36AM -0500, Mimi Zohar wrote:
> > Some filesystems do not export the filesystem's magic number, as it is
> > considered internal, private data. In other cases, the policy rule
> > needs to identify a specifically mounted filesystem (eg. rootfs).
>
> No, it doesn't. Policies based on a file system type are complete and
> utterly bogus. rootfs should not be treated any different from other
> file systems.
rootfs IS different than other filesystems, as other filesystems
uniquely identify the underlying filesystem type. rootfs can be a
ramfs or tmpfs filesystem. Only tmpfs supports xattrs.
Mimi
WARNING: multiple messages have this Message-ID (diff)
From: zohar@linux.vnet.ibm.com (Mimi Zohar)
To: linux-security-module@vger.kernel.org
Subject: [PATCH] ima: define new policy condition based on the filesystem name
Date: Mon, 15 Jan 2018 11:40:07 -0500 [thread overview]
Message-ID: <1516034407.6607.26.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180115162726.GB15686@infradead.org>
On Mon, 2018-01-15 at 08:27 -0800, Christoph Hellwig wrote:
> On Mon, Jan 15, 2018 at 11:20:36AM -0500, Mimi Zohar wrote:
> > Some filesystems do not export the filesystem's magic number, as it is
> > considered internal, private data. In other cases, the policy rule
> > needs to identify a specifically mounted filesystem (eg. rootfs).
>
> No, it doesn't. Policies based on a file system type are complete and
> utterly bogus. rootfs should not be treated any different from other
> file systems.
rootfs IS different than other filesystems, as other filesystems
uniquely identify the underlying filesystem type. ?rootfs can be a
ramfs or tmpfs filesystem. ?Only tmpfs supports xattrs.
Mimi
--
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
WARNING: multiple messages have this Message-ID (diff)
From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-integrity <linux-integrity@vger.kernel.org>,
linux-security-module <linux-security-module@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Dongsu Park <dongsu@kinvolk.io>, Alban Crequy <alban@kinvolk.io>,
Seth Forshee <seth.forshee@canonical.com>
Subject: Re: [PATCH] ima: define new policy condition based on the filesystem name
Date: Mon, 15 Jan 2018 11:40:07 -0500 [thread overview]
Message-ID: <1516034407.6607.26.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180115162726.GB15686@infradead.org>
On Mon, 2018-01-15 at 08:27 -0800, Christoph Hellwig wrote:
> On Mon, Jan 15, 2018 at 11:20:36AM -0500, Mimi Zohar wrote:
> > Some filesystems do not export the filesystem's magic number, as it is
> > considered internal, private data. In other cases, the policy rule
> > needs to identify a specifically mounted filesystem (eg. rootfs).
>
> No, it doesn't. Policies based on a file system type are complete and
> utterly bogus. rootfs should not be treated any different from other
> file systems.
rootfs IS different than other filesystems, as other filesystems
uniquely identify the underlying filesystem type. rootfs can be a
ramfs or tmpfs filesystem. Only tmpfs supports xattrs.
Mimi
next prev parent reply other threads:[~2018-01-15 16:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 16:20 [PATCH] ima: define new policy condition based on the filesystem name Mimi Zohar
2018-01-15 16:20 ` Mimi Zohar
2018-01-15 16:27 ` Christoph Hellwig
2018-01-15 16:27 ` Christoph Hellwig
2018-01-15 16:40 ` Mimi Zohar [this message]
2018-01-15 16:40 ` Mimi Zohar
2018-01-15 16:40 ` Mimi Zohar
2018-01-15 17:19 ` Christoph Hellwig
2018-01-15 17:19 ` Christoph Hellwig
2018-01-15 17:19 ` Christoph Hellwig
2018-01-15 17:19 ` Christoph Hellwig
2018-02-05 17:31 ` Mimi Zohar
2018-02-05 17:31 ` 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=1516034407.6607.26.camel@linux.vnet.ibm.com \
--to=zohar@linux.vnet.ibm.com \
--cc=alban@kinvolk.io \
--cc=dongsu@kinvolk.io \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--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 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.