From: Rob Landley <rob@landley.net>
To: Tal Tchwella <tal.tchwella@gmail.com>
Cc: linux-kernel@vger.kernel.org, tchwella@mit.edu
Subject: Re: [PATCH 0/3] Patches to enable chroot for all users
Date: Wed, 20 Mar 2013 10:16:03 -0500 [thread overview]
Message-ID: <1363792563.15703.50@driftwood> (raw)
In-Reply-To: <1363784025-23870-1-git-send-email-tchwella@mit.edu> (from tal.tchwella@gmail.com on Wed Mar 20 07:53:42 2013)
On 03/20/2013 07:53:42 AM, Tal Tchwella wrote:
> I want to suggest adding chroot capability to all users.
I note that chroot doesn't quite do what most people think it does:
http://landley.net/notes-2011.html#02-06-2011
I've had a todo item forever to modify chroot to actually change the
process-local mount tree, creating a bind mount if necessary for the
new directory, reparenting the mount tree to that bind mount, and
making sure that reference counting can free unused mounts that this
would discard. (Except rootfs always needs a nonzero reference count.)
The problem isn't adding security checks, the problem is that having a
"/" symlink point somewhere _other_ than the actual top of the
process-local mount tree is obsolete now that there isn't a single
global mount tree for all processes. (Yes, this would mean it might
need to create a new namespace.)
Rob
next prev parent reply other threads:[~2013-03-20 15:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 12:53 [PATCH 0/3] Patches to enable chroot for all users Tal Tchwella
2013-03-20 12:53 ` [PATCH 1/3] enabled " Tal Tchwella
2013-03-20 12:53 ` [PATCH 2/3] socket checks for uds fds transfer Tal Tchwella
2013-03-20 12:53 ` [PATCH 3/3] open fds check when starting chroot Tal Tchwella
2013-03-20 15:16 ` Rob Landley [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-03-20 13:09 [PATCH 0/3] Patches to enable chroot for all users tal.tchwella
2013-03-20 15:35 ` Casey Schaufler
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=1363792563.15703.50@driftwood \
--to=rob@landley.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tal.tchwella@gmail.com \
--cc=tchwella@mit.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.