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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sat, 23 Dec 2017 13:18:30 +0100
From:   Dongsu Park <>
To:     Richard Weinberger <>
Cc:     LKML <>,
        Miklos Szeredi <>,
        Linux Containers <>,
        Seth Forshee <>,
        Alban Crequy <>,
        "Eric W . Biederman" <>,
        Sargun Dhillon <>,
        "" <>
Subject: Re: [PATCH 02/11] mtd: Check permissions towards mtd block device
 inode when mounting


On Fri, Dec 22, 2017 at 10:06 PM, Richard Weinberger
<> wrote:
> Dongsu,
> On Fri, Dec 22, 2017 at 3:32 PM, Dongsu Park <> wrote:
>> From: Seth Forshee <>
>> 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?

I'm not sure I'm aware of all use cases w.r.t mtd & ubifs.
To my understanding, in these days many container runtimes allow
unprivileged users to run containers. (docker, lxc, runc, bubblewrap, etc)
That's why the kernel should deal with additional permission checks
that might have not been necessary in the past.
This MTD patch is one of those special cases.

> Please note that UBIFS sits on top of a character device and not a block device.

Aha, good to know.


> --
> Thanks,
> //richard

Powered by blists - more mailing lists