Security and Javascript

simo s at
Tue Jul 2 13:07:55 UTC 2013

On Tue, 2013-07-02 at 11:24 +0300, Timo Juhani Lindfors wrote:
> Simo Sorce <s at> writes:
> > sandbox -i $HOME/.mozilla/extensions -i $HOME/.mozilla/plugins -i 
> > $HOME/.mozilla/firefox/abcdefgh.sandbox -i 
> > $HOME/.mozilla/firefox/profiles.ini -w 1024x900 -t sandbox_web_t -M -X 
> > /usr/bin/firefox -P sandbox $*
> >
> > It requires at least a basic SeLinux Policy installed and the sandbox
> > program, but it is really neat in that it completely isolates the
> > browser and crates a completely new environment for it to run.
> Can't the browser still talk anything it wants with the X server? Or
> does your X server somehow understand selinux labels?

sandbox -X runs everything into a nested X server (Xephyr here) run
explicitly for the application, so that the app does not have direct
access to the outer X server.

Although there was a feature (XACE) to make the X server more secure I
do no think it ever worked well enough. I think the only good solution
will be to use wayland once it is good enough. Its model isolates each
process and is much better from a security pov from what I've been told
so far.


More information about the Discussion mailing list