nanogui: named socket issue...


Previous by date: 18 Jan 2001 13:36:02 -0000 nanogui, tangxj
Next by date: 18 Jan 2001 13:36:02 -0000 System hangs in SCR_FB.C in tty ioctl, Bipin T S
Previous in thread: 18 Jan 2001 13:36:02 -0000 Re: named socket issue..., Ken Kennedy
Next in thread: 18 Jan 2001 13:36:02 -0000 Re: named socket issue..., Ken Kennedy

Subject: Re: named socket issue...
From: Alex Holden ####@####.####
Date: 18 Jan 2001 13:36:02 -0000
Message-Id: <Pine.LNX.4.04.10101181310290.1744-100000@hyperspace.linuxhacker.org>

On Wed, 17 Jan 2001, Ken Kennedy wrote:
> Outstanding! That did it. Thanks heaps! Now, is the fact that I have to do
> that a "feature", or a bug...(ie, anyone interested in a patch to modify
> that behavior, to allow multiple users?)

Security feature.

Try this: create a new user and group (call it nano-X or something), place
all the users you want to be able to access the window server in the new
group, and run the nano-X server as the new user. If the new user can't
open the framebuffer devices because they're owned by root, create a new
group (fbusers?), set the group ID of the framebuffer devices to the
new framebuffer group, and add the nano-X user to the framebuffer group.

-- 
------- Alex Holden -------
http://www.linuxhacker.org/
 http://www.robogeeks.org/


Previous by date: 18 Jan 2001 13:36:02 -0000 nanogui, tangxj
Next by date: 18 Jan 2001 13:36:02 -0000 System hangs in SCR_FB.C in tty ioctl, Bipin T S
Previous in thread: 18 Jan 2001 13:36:02 -0000 Re: named socket issue..., Ken Kennedy
Next in thread: 18 Jan 2001 13:36:02 -0000 Re: named socket issue..., Ken Kennedy


Powered by ezmlm-browse 0.20.