On Mon, 11 May 1998, Vidiot wrote:

> >> I thought the cure for this was to set the SUID bit on the X server.  I'm
> >> not at home to double-check, but I believe that is what you ultimately end
> >> up doing.
> >> 
> >
> >I think MB is right on this one.  However, I think the newest version of
> >XFree takes care of this (I believe setting the SUID bit on the Xservers
> >poses some security risks).
> >Brian.
> 
> Ya, I don't remember doing anything special with the latest XFree86 release
> and Brian is right about the security risk.
> 
> So, the end result is to:
> 
>       a) set the SUID bit on your current version
>       b) get the latest release and install it.
> 

It's quite true about security. But why not to use xserver-wrapper? This
solves the problem with the SUID bit on the X server. Another way is to
apply some patches to the kernel source and to switch on an option which
checks if somebody tries to overrun the X server buffer. This makes it
impossible to get root using this SUID bit. Still the first way is more
preferable to my mind.

I don't understand the problem with xdm. Xdm starts at the boot time when
all procs start as if run by root. So no SUID id need for xdm, if run at
booting. 

Alexei


-- 
  PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
         To unsubscribe: mail [EMAIL PROTECTED] with 
                       "unsubscribe" as the Subject.

Reply via email to