From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: ivo.welch@gmail.com
Cc: ivo.welch@anderson.ucla.edu, linux-kernel@vger.kernel.org
Subject: Re: the easy way to sandbox?
Date: Mon, 21 May 2012 19:52:55 +0100 [thread overview]
Message-ID: <20120521195255.5b54f707@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <CAPr7RtUBDn01qDkxvcLO8ZckAtTmCCJk7hCjwH4_XziwXtAS6Q@mail.gmail.com>
On Mon, 21 May 2012 09:28:13 -0700
ivo welch <ivo.welch@anderson.ucla.edu> wrote:
> Suggestion: introduce a system call that eliminates access to all
> real file systems for the current process. the only permissible
> interaction would be stdin, stdout, and stderr.
>
> this would make it very simple to write a sandboxed safe fcgi script.
No it wouldn't - because of things like ptrace.
Sandboxing done right is *hard*. SELinux and the other security setups
can do it. Containers can do interesting stuff in this space. Probably
the distros sometimes need to package the tools for it better.
Take a look at some of the cloud service code people have published.
Alan
prev parent reply other threads:[~2012-05-21 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 16:28 the easy way to sandbox? ivo welch
2012-05-21 16:45 ` Mihai Donțu
2012-05-21 18:52 ` Alan Cox [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120521195255.5b54f707@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=ivo.welch@anderson.ucla.edu \
--cc=ivo.welch@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox