Chroot and X-Window applications

From: Erwan Becquet (becquet_at_cnam.fr)
Date: 05/15/03 

Date: 14 May 2003 21:39:11 -0700

Hi everybody,

I have a strange problem, I want to start programs
from a chrooted tree. It works perfectly with non-x
apps. But with X apps (emacs for example), I have an
error "Cant Connect to X Server on :0". Same work
perfecly without chroot.

I think X-Window use some special place of the filesystem
but I cant find what.

I tried with a chroot on / and it works. But when I tried
to copy whole tree on a subtree (like /tmp/jail), so I have
under /tmp/jail : usr, var,etc, tmp, bin, sbin, home etc ...
and try that, it fails.

Has someone already encounter a similar problem ? Or maybe
someone has a deep knowledge of X-Window mechanisms and could
help me ?

Thanks in advance.

Relevant Pages

  • Re: Chroot and X-Window applications
    ... > I have a strange problem, ... But with X apps, ... > I tried with a chroot on / and it works. ... Nigel Wade, System Administrator, Space Plasma Physics Group, University of Leicester, Leicester, LE1 7RH, UK ...
    (comp.security.unix)
  • Re: Chroot and X-Window applications
    ... >> I have a strange problem, ... >> apps. ... >server outside the chroot). ... If it got far enough to give him a "Can't connect" message, the libraries ...
    (comp.security.unix)
  • Re: bug in libc6
    ... > | install it into it's own little chroot containing whatever old libraries ... > Before I go off and do this, it occurs to me that running an X server ... > in chroot might be problematic. ... one machine and your apps on another. ...
    (Debian-User)
  • Re: [RFC][PATCH 0/11] security: AppArmor - Overview
    ... You may filter out worms and script kiddies this way but in the end you are using obscurity (of filesystem layout, what the policy allows, how the apps are configured, etc) for security, which again, leads to a false sense of security. ... I was paying attention, thank you. ... So it may not be able to chroot during runtime but if you can't be sure that it starts in the chroot the argument still applies. ...
    (Linux-Kernel)
  • Re: BUG? atleast >=2.6.19-rc5, x86 chroot on x86_64
    ... for 10 days, and then chroot in, run ... the 32bit apps, and within hours of using, hardlock. ... Early AMD K8 platforms had a hardware bug that could have caused ...
    (Linux-Kernel)