linux-kernel - Re: [PATCH] driver-core: devtmpfs - driver core maintained /dev tmpfs

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: <ac3eb2510905011928o26ae45efr2b23deafda76e1fc@mail.gmail.com>
Date:	Sat, 2 May 2009 04:28:33 +0200
From:	Kay Sievers <kay.sievers@...y.org>
To:	Brian Swetland <swetland@...gle.com>
Cc:	Greg KH <greg@...ah.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Jan Blunck <jblunck@...e.de>
Subject: Re: [PATCH] driver-core: devtmpfs - driver core maintained /dev tmpfs

On Sat, May 2, 2009 at 04:02, Brian Swetland <swetland@...gle.com> wrote:
> On Fri, May 1, 2009 at 6:48 PM, Kay Sievers <kay.sievers@...y.org> wrote:

>>> I would love to have a way for the kernel to do something like devfs
>>> (it'd let me kill some ugly userspace code on my side)....
>>
>> How are permissions defined in your environment? What's the set of
>> permissions you need to apply?
>
> In our world we use groups to provide access to specific classes of
> hardware resources (audio, video, display, dsp, etc) and processes
> that have the appropriate permissions are arranged to run with
> necessary additional groups for the hardware they need to access.

These group numbers are always static on your system, and don't get
changed while the system is running? Like you always assign gid X to
all sound devices? Or do you need to manage them dynamically?

Do your device nodes permissions/ownership ever change on the running
system after the device is alive?

Thanks,
Kay
--
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/