nanogui: named socket issue...


Previous by date: 18 Jan 2001 14:59:22 -0000 Re: System hangs in SCR_FB.C in tty ioctl, Martin_Doering.mn.man.de
Next by date: 18 Jan 2001 14:59:22 -0000 Re: named socket issue..., Alex Holden
Previous in thread: 18 Jan 2001 14:59:22 -0000 Re: named socket issue..., Alex Holden
Next in thread: 18 Jan 2001 14:59:22 -0000 Re: named socket issue..., Alex Holden

Subject: Re: named socket issue...
From: Ken Kennedy ####@####.####
Date: 18 Jan 2001 14:59:22 -0000
Message-Id: <Pine.LNX.4.21.0101181000350.29388-100000@abelard.kenzoid.com>

On Thu, 18 Jan 2001, Alex Holden wrote:

> 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.

Gotcha. That makes sense, when compiling for the fb...but I'm compiling
for X. I can certainly do the same basic thing, but it kinda breaks the
concept of installing a X prg and allowing many users to run it
separately, doesn't it? Please note, I'm not complaining...it works, and
I'm happy. Just asking the question!

Thanks for all you help!

Ken



Previous by date: 18 Jan 2001 14:59:22 -0000 Re: System hangs in SCR_FB.C in tty ioctl, Martin_Doering.mn.man.de
Next by date: 18 Jan 2001 14:59:22 -0000 Re: named socket issue..., Alex Holden
Previous in thread: 18 Jan 2001 14:59:22 -0000 Re: named socket issue..., Alex Holden
Next in thread: 18 Jan 2001 14:59:22 -0000 Re: named socket issue..., Alex Holden


Powered by ezmlm-browse 0.20.