linux-kernel - Re: [PATCH] driver core: add uid and gid to devtmpfs

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: <20130406172612.GA27809@kroah.com>
Date:	Sat, 6 Apr 2013 10:26:12 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Al Viro <viro@...IV.linux.org.uk>
Cc:	linux-kernel@...r.kernel.org, Kay Sievers <kay@...y.org>
Subject: Re: [PATCH] driver core: add uid and gid to devtmpfs

On Sat, Apr 06, 2013 at 06:09:52PM +0100, Al Viro wrote:
> On Sat, Apr 06, 2013 at 09:56:00AM -0700, Greg KH wrote:
> > From: Kay Sievers <kay@...y.org>
> > 
> > Some drivers want to tell userspace what uid and gid should be used for
> > their device nodes, so allow that information to percolate through the
> > driver core to userspace in order to make this happen.  This means that
> > some systems (i.e.  Android and friends) will not need to even run a
> > udev-like daemon for their device node manager and can just rely in
> > devtmpfs fully, reducing their footprint even more.
> 
> Excuse me, but "some drivers" have no fucking business to mess with
> uid and gid assignments in the first place...

Why not?  "closed" systems, like Android and other embedded systems,
have "assigned" uid and gid values that never change.  Right now they
have to have a horrible shell-script to set these values in devtmpfs
when the device shows up to the needed numbers.  This tiny patch gets
rid of that shell script entirely, allowing them to specify it from the
kernel as needed.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/