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, 05 Feb 2018 12:31:41 -0500 [thread overview]
Message-ID: <1517851901.3736.120.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180115171914.GB28088@infradead.org>
On Mon, 2018-01-15 at 09:19 -0800, Christoph Hellwig wrote:
> On Mon, Jan 15, 2018 at 11:40:07AM -0500, Mimi Zohar wrote:
> > 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.
>
> Tons of filesystems only have xattrs optionally. Check for goddamn
> xattrs if that is the requirement and not a name that has absolutely
> zero meaning for functionality. That is the whole point!
I should have said the main reason for defining a rootfs policy rule
is not to differentiate it from ramfs, but the ability to require file
signatures.
Up to now, CPIO did not support xattrs. ?With Taras' proposed CPIO
xattr patch set, the initramfs can now be properly labeled with file
signatures. ?Since only some systems will include file signatures in
the initramfs, we need to be able to differentiate between those that
require file signatures from those that don't.
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
prev parent reply other threads:[~2018-02-05 17:31 UTC|newest]
Thread overview: 5+ 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:27 ` Christoph Hellwig
2018-01-15 16:40 ` Mimi Zohar
2018-01-15 17:19 ` Christoph Hellwig
2018-02-05 17:31 ` Mimi Zohar [this message]
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=1517851901.3736.120.camel@linux.vnet.ibm.com \
--to=zohar@linux.vnet.ibm.com \
--cc=linux-security-module@vger.kernel.org \
/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).