[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFLxGvwzRBGJf0-jCAwGts1HwV_nT072+yhHLP079sxQezoTFQ@mail.gmail.com>
Date: Fri, 22 Dec 2017 22:06:13 +0100
From: Richard Weinberger <richard.weinberger@...il.com>
To: Dongsu Park <dongsu@...volk.io>
Cc: LKML <linux-kernel@...r.kernel.org>,
Miklos Szeredi <mszeredi@...hat.com>,
Linux Containers <containers@...ts.linux-foundation.org>,
Seth Forshee <seth.forshee@...onical.com>,
Alban Crequy <alban@...volk.io>,
"Eric W . Biederman" <ebiederm@...ssion.com>,
Sargun Dhillon <sargun@...gun.me>,
"linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>
Subject: Re: [PATCH 02/11] mtd: Check permissions towards mtd block device
inode when mounting
Dongsu,
On Fri, Dec 22, 2017 at 3:32 PM, Dongsu Park <dongsu@...volk.io> wrote:
> From: Seth Forshee <seth.forshee@...onical.com>
>
> Unprivileged users should not be able to mount mtd block devices
> when they lack sufficient privileges towards the block device
> inode. Update mount_mtd() to validate that the user has the
> required access to the inode at the specified path. The check
> will be skipped for CAP_SYS_ADMIN, so privileged mounts will
> continue working as before.
What is the big picture of this?
Can in future an unprivileged user just mount UBIFS?
Please note that UBIFS sits on top of a character device and not a block device.
--
Thanks,
//richard
Powered by blists - more mailing lists