linux-kernel - Re: [RFC] enhancing the kernel's graphics subsystem

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: <21d7e9970705220127j6d92143ud0720e70e25c001a@mail.gmail.com>
Date:	Tue, 22 May 2007 18:27:43 +1000
From:	"Dave Airlie" <airlied@...il.com>
To:	"Jeff Garzik" <jeff@...zik.org>
Cc:	"Jon Smirl" <jonsmirl@...il.com>,
	"Jesse Barnes" <jbarnes@...tuousgeek.org>,
	"Jesse Barnes" <jesse.barnes@...el.com>,
	linux-kernel@...r.kernel.org,
	"Antonino A. Daplas" <adaplas@...il.com>
Subject: Re: [RFC] enhancing the kernel's graphics subsystem

> > Did I say the X server? There are policy decisions that are root only
> > also authorisation of processes to render etc..
>
> Root only today, maybe, but this thread is talking about future
> directions.  Don't lock your design into a coarse-grained security model.
>

We can add a new capability bit but there are certain operations that
need privs especially if multiple users are involved. binding outputs
to crtcs being one.

Again I can see little reason that this wouldn't be possible going
forward. But i'm seeing policy decisions we currently make in the X
server needing to be made somewhere.

Dave.

>
> > I'm not sure we can punt all that in-kernel.
>
> See my response to Alan.
>
> 	Jeff
>
>
>
>
-
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/