From: Shaya Potter <spotter@cs.columbia.edu>
To: Majkls <majkls@tiscali.cz>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: hardened chroot()
Date: Wed, 30 Aug 2006 13:51:51 -0400 [thread overview]
Message-ID: <44F5D037.2000606@cs.columbia.edu> (raw)
In-Reply-To: <44F5CF1F.1080304@tiscali.cz>
Majkls wrote:
> Hello,
> is there possibility to add hardened chroot() to linux kernel? I have
> some patch and I would like submit it into linux-kernel. Now can be
> chroot workarounded. What do you think about it?
I wrote one a few years ago, but there seemed to be no interest in it.
My conception was based on that observation that a chroot "point" really
only deals with path walking and basically says that at this point ".."
is the same as ".". Therefore, all we need are a linked list of "chroot
points" and just like the current follow_dotdot() function tests if the
current directory is the "root", one can just have it loop through the
entire list of chroot points.
The idea was to enable root processes to run within a chroot
environment, and even call chroot().
In Linux today, it might be better solved via setting up an alternative
namespace.
next prev parent reply other threads:[~2006-08-30 17:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 17:47 hardened chroot() Majkls
2006-08-30 17:51 ` Shaya Potter [this message]
2006-08-30 18:11 ` Majkls
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=44F5D037.2000606@cs.columbia.edu \
--to=spotter@cs.columbia.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=majkls@tiscali.cz \
/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.