From: Tal Tchwella <tal.tchwella@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: tchwella@mit.edu
Subject: [PATCH 0/3] Patches to enable chroot for all users
Date: Wed, 20 Mar 2013 05:53:42 -0700 [thread overview]
Message-ID: <1363784025-23870-1-git-send-email-tchwella@mit.edu> (raw)
I want to suggest adding chroot capability to all users.
The following patches enable that capability, while considering the security mechanism needed to disable escape routes for chroots by non-root users,
and keeping chroot backward-compatible for root users.
The first patch establishes the concept of multi-user chroot, while disabling checks for root user in the chroot process.
The second patch checks whether a fd that is sent to a chroot application by a non-root user refers to a directory.
If that is the case, that fd is skipped, to disable an escape route.
The third patch disables the option for applications that have open fds to directories to be chrooted by a non-root user.
Any comments, feedback and suggestions are appreciated!
Thanks,
Tal
Tal Tchwella (3):
enabled chroot for all users
socket checks for uds fds transfer
open fds check when starting chroot
fs/exec.c | 3 +++
fs/open.c | 32 ++++++++++++++++++++++++++++++--
include/linux/sched.h | 12 ++++++++++++
init/main.c | 1 +
kernel/fork.c | 2 ++
net/core/scm.c | 9 +++++++++
6 files changed, 57 insertions(+), 2 deletions(-)
--
1.7.9.5
next reply other threads:[~2013-03-20 12:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 12:53 Tal Tchwella [this message]
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 ` [PATCH 0/3] Patches to enable chroot for all users Rob Landley
2013-03-20 13:09 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=1363784025-23870-1-git-send-email-tchwella@mit.edu \
--to=tal.tchwella@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome