On 11/22/06, Alan Coopersmith <[EMAIL PROTECTED]> wrote:
Peter Tribble wrote:
> Is there any particular reason why Xnest can't be setgid root?
None that we know of, we've just never done a security audit on the
code that's specific to Xnest to verify that it's safe to run setgid.
Many sites
Peter Tribble wrote:
Is there any particular reason why Xnest can't be setgid root?
None that we know of, we've just never done a security audit on the
code that's specific to Xnest to verify that it's safe to run setgid.
--
-Alan Coopersmith- [EMAIL PROTECTED]
Sun M
On 11/22/06, Alan Coopersmith <[EMAIL PROTECTED]> wrote:
Thomas Maier-Komor wrote:
> Hi,
>
> default permissions for .X11-pipe and .X11-unix seems to be 0775 with
ownership root:root.
>
> This prevents Xnest from running. I saw that in Solaris 2.5.1 the
permissions originally have been 0777 and
Thomas Maier-Komor wrote:
Hi,
default permissions for .X11-pipe and .X11-unix seems to be 0775 with ownership
root:root.
This prevents Xnest from running. I saw that in Solaris 2.5.1 the permissions
originally have been 0777 and a patch changed it to 0775. I suspect that there
was no support
>2.5.1 certainly had the sticky bit, but there was still at least one
>scenario that was claimed to be vunerable. Although I can't remember
>which right now. But perhaps along the lines of:
The sticky bit semantics in 2.5.1 were "pure SV" but possibly with
a lax interpretation (if users have
Thomas Maier-Komor wrote:
Hi,
default permissions for .X11-pipe and .X11-unix seems to be 0775 with ownership
root:root.
This prevents Xnest from running. I saw that in Solaris 2.5.1 the permissions
originally have been 0777 and a patch changed it to 0775. I suspect that there
was no support
Hi,
default permissions for .X11-pipe and .X11-unix seems to be 0775 with ownership
root:root.
This prevents Xnest from running. I saw that in Solaris 2.5.1 the permissions
originally have been 0777 and a patch changed it to 0775. I suspect that there
was no support for the sticky bit in Solar
