Date: Wed, 8 Nov 2006 15:23:06 +0100 From: Erik Trulsson <ertr1013@student.uu.se> To: Lowell Gilbert <freebsd-security-local@be-well.ilk.org> Cc: freebsd-security@freebsd.org, mal content <artifact.one@googlemail.com> Subject: Re: Sandboxing Message-ID: <20061108142306.GA64711@owl.midgard.homeip.net> In-Reply-To: <44irhq6ngd.fsf@be-well.ilk.org> References: <8e96a0b90611080439n558022edj79febf458494ef6e@mail.gmail.com> <8e96a0b90611080441t2b486637ya10acd5a1dd77690@mail.gmail.com> <44irhq6ngd.fsf@be-well.ilk.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Nov 08, 2006 at 09:08:02AM -0500, Lowell Gilbert wrote: > "mal content" <artifact.one@googlemail.com> writes: > > > On 08/11/06, mal content <artifact.one@googlemail.com> wrote: > >> Hi. > >> > >> This is mostly hypothetical, just because I want to see how knowledgeable > >> people would go about achieving it: > >> > >> I want to sandbox Mozilla Firefox. For the sake of example, I'm running it > >> under my own user account. The idea is that it should be allowed to > >> connect to the X server, it should be allowed to write to ~/.mozilla and > >> /tmp. > >> > >> I expect some configurations would want access to audio devices in > >> /dev, but for simplicity, that's ignored here. > >> > >> All other filesystem access is denied. > >> > >> Ready... > >> > >> Go! > >> > >> MC > >> > > > > I forgot to add: Use of TrustedBSD extensions is, of course, allowed. > > Putting an X Windows application in a sandbox is kind of silly. After > all, X has to have direct access to memory. The X *server* needs direct access to memory. X clients (like Firefox or just about any other application using X) does not need direct access to memory. They don't even need to run on the same machine as the X server. > A virtual machine > approach, with a whole virtual set of memory, might make more sense. > I use that (via qemu), although not for exactly the same reasons. -- <Insert your favourite quote here.> Erik Trulsson ertr1013@student.uu.se
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061108142306.GA64711>