linux-ext4 - [RFC] open_by_handle() vs. EA inodes

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-next>] [day] [month] [year] [list]

Message-ID: <20180629181900.GP30522@ZenIV.linux.org.uk>
Date:   Fri, 29 Jun 2018 19:19:00 +0100
From:   Al Viro <viro@...IV.linux.org.uk>
To:     linux-ext4@...r.kernel.org
Cc:     linux-fsdevel@...r.kernel.org
Subject: [RFC] open_by_handle() vs. EA inodes

	On ea_inode-enabled ext4 open_by_handle() (as well as knfsd, etc.)
can get to EA inodes as long as it knows their inumbers - just pass it
an fhandle with zeroed version bytes and the right inumber in it.

	AFAICS, it's Not Nice(tm), especially since you can write to those,
whether they are shared or not.

	Should we make ext4_nfs_get_inode() check for EXT4_EA_INODE_FL
and fail if it's set?