linux-kernel - Re: [PATCH 0/2] turn on force option for FUSE in builtin policies

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20180115171825.GA28088@infradead.org>
Date:   Mon, 15 Jan 2018 09:18:25 -0800
From:   Christoph Hellwig <hch@...radead.org>
To:     Mimi Zohar <zohar@...ux.vnet.ibm.com>
Cc:     Christoph Hellwig <hch@...radead.org>,
        Dongsu Park <dongsu@...volk.io>, linux-kernel@...r.kernel.org,
        Alban Crequy <alban@...volk.io>,
        Miklos Szeredi <miklos@...redi.hu>,
        Seth Forshee <seth.forshee@...onical.com>,
        linux-integrity <linux-integrity@...r.kernel.org>
Subject: Re: [PATCH 0/2] turn on force option for FUSE in builtin policies

On Mon, Jan 15, 2018 at 11:32:41AM -0500, Mimi Zohar wrote:
> For XFS, which considers fsmagic numbers private to the filesystem,
> *always* using the fsmagic number is wrong.  As to whether this is
> true for other filesystems is unclear.  IMA policies have been defined
> in terms of fsmagic numbers for a long time.  fsmagic numbers were
> moved from the filesystems to magic.h for this purpose.  Someone would
> have complained earlier if it is always wrong.
>  
> I just posted a patch titled "ima: define new policy condition based
> on the filesystem name" to allow policies to be defined in terms of
> the i_sb->s_type->name.

ima has no business looking at either the name _or_ the magic number.