From: Stef Bon <stef@bononline.nl>
To: Chris Stromsoe <cbs@cts.ucla.edu>
Cc: autofs@linux.kernel.org
Subject: Re: bind mounting into a generated multi-level directory structure
Date: Sat, 16 Feb 2008 10:47:35 +0100 [thread overview]
Message-ID: <47B6B137.3000205@bononline.nl> (raw)
In-Reply-To: <Pine.LNX.4.64.0802151326180.27197@potato.cts.ucla.edu>
Chris Stromsoe wrote:
> My eventual solution was to use multi-mount to bind mount a shared
> directory with libraries and other common data to a "simple" generated
> path as a container, and then bind mount the hashed directory inside
> of that volume. I'm using the container volume as a chroot
> environment to run untrusted code (php) on a web server, and wanted to
> minimize exposure to the rest of the machine as much as possible.
Ok, it's more clear to me now. I'm wondering, isn't it possible to
create a custom "chroot" command, which will of course do the chroot,
but also do the necessary binds. I've been working on a login shell
(chroot_union) which is the standard shell of a user. When this user
logs in (starts a session) a copy of the system is created with unionfs.
Then a chroot is done, and a perfect environment where the user can do
anything is there. Isn't that possible?
Stef Bon
next prev parent reply other threads:[~2008-02-16 9:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 8:29 bind mounting into a generated multi-level directory structure Chris Stromsoe
2008-02-10 14:18 ` Stef Bon
2008-02-14 22:32 ` chris barry
2008-02-15 9:52 ` Stef Bon
2008-02-15 21:44 ` Chris Stromsoe
2008-02-16 9:47 ` Stef Bon [this message]
2008-02-17 7:51 ` Chris Stromsoe
2008-02-18 15:37 ` OT: was " chris barry
2008-02-11 8:13 ` Ian Kent
2008-02-11 9:53 ` Chris Stromsoe
2008-02-11 10:34 ` Ian Kent
2008-02-12 22:35 ` Chris Stromsoe
2008-02-11 13:50 ` Stef Bon
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=47B6B137.3000205@bononline.nl \
--to=stef@bononline.nl \
--cc=autofs@linux.kernel.org \
--cc=cbs@cts.ucla.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.