From: Dave Hansen <dave-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: "Tanaka, Thomas" <thomas.tanaka-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org"
<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
Subject: Re: Building a SECURE cointainer using Cgroups ?
Date: Mon, 13 Oct 2008 10:54:56 -0700 [thread overview]
Message-ID: <1223920496.29877.22.camel@nimitz> (raw)
In-Reply-To: <0A97A441BFADC74EA1E299A79C69DF9212D3F6C9E2-osO9UTpF0UQ64kNsxIetb7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
On Mon, 2008-10-13 at 10:03 -0700, Tanaka, Thomas wrote:
> Is it possible to build a secure container by using cgroups? My goal
> is to achieve a file system namespace container that will limit the
> file system view given to a process similar to chroot does but of
> course has to be secure.
You'll have to be a bit more specific than that. Do you want to make
absolutely sure that certain containers have absolutely no access to
certain fs namespaces?
-- Dave
next prev parent reply other threads:[~2008-10-13 17:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-13 17:03 Building a SECURE cointainer using Cgroups ? Tanaka, Thomas
[not found] ` <0A97A441BFADC74EA1E299A79C69DF9212D3F6C9E2-osO9UTpF0UQ64kNsxIetb7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2008-10-13 17:54 ` Dave Hansen [this message]
2008-10-13 18:01 ` Tanaka, Thomas
[not found] ` <0A97A441BFADC74EA1E299A79C69DF9212D3F6CA1B-osO9UTpF0UQ64kNsxIetb7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2008-10-13 18:25 ` Dave Hansen
2008-10-13 19:29 ` Serge E. Hallyn
[not found] ` <20081013192921.GA10814-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-10-13 20:57 ` Tanaka, Thomas
[not found] ` <0A97A441BFADC74EA1E299A79C69DF9212D3F6CA82-osO9UTpF0UQ64kNsxIetb7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2008-10-13 21:04 ` Serge E. Hallyn
[not found] ` <20081013210420.GA26529-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-10-13 21:13 ` Tanaka, Thomas
2008-10-14 8:53 ` Daniel P. Berrange
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=1223920496.29877.22.camel@nimitz \
--to=dave-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=thomas.tanaka-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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