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]

Date:	Mon, 21 May 2007 20:33:05 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
CC:	Dave Airlie <airlied@...il.com>, 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

Alan Cox wrote:
>>> the kernel, it can be a lot smaller than X and auditable.. sticking
>>> the DRI protocol in the kernel is just pointless..
>> It is a quite sensible idea.
>>
>> The userspace X server SHOULD be running under a non-root user, with 
>> appropriate fine-grained privs granted to it.
>>
>> "I need root to do graphics" is a myopic, antiquated view of the world.
> 
> X server: priviledges below everything, pageable
> kernel: priviledges as high as conceivable, non-pageable
> 
> So why do you want it in kernel.... security is not the sensible answer
> here.

Replying/quoting mixup.  I was responding to the root-privs userspace 
aspect, not the "put it in the kernel" aspect.

I do not want it in the kernel (should have snipped that last quoted line).

	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/