From: Tal Tchwella <tal.tchwella@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: tchwella@mit.edu
Subject: [PATCH 1/3] enabled chroot for all users
Date: Wed, 20 Mar 2013 05:53:43 -0700 [thread overview]
Message-ID: <1363784025-23870-2-git-send-email-tchwella@mit.edu> (raw)
In-Reply-To: <1363784025-23870-1-git-send-email-tchwella@mit.edu>
This patch enables chroot for all users, not just root users,
by disabling the appropriate checks in fs/open.c.
It also disables nested chroots by non-root users,
so they will not be able to break out of a chroot using classic techniques.
Signed-off-by: Tal Tchwella <tchwella@mit.edu>
---
fs/exec.c | 3 +++
fs/open.c | 8 ++++++--
include/linux/sched.h | 12 ++++++++++++
init/main.c | 1 +
kernel/fork.c | 2 ++
5 files changed, 24 insertions(+), 2 deletions(-)
diff --git a/fs/exec.c b/fs/exec.c
index 7d27def..e2303ef 100644
--- a/fs/exec.c
+++ b/fs/exec.c
@@ -1299,6 +1299,9 @@ int prepare_binprm(struct linux_binprm *bprm)
!current->no_new_privs) {
/* Set-uid? */
if (mode & S_ISUID) {
+ /* chroot by a regular, non root, user? */
+ if (current->user_chroot == CHROOT_USER_MODE)
+ return -EACCES;
bprm->per_clear |= PER_CLEAR_ON_SETID;
bprm->cred->euid = inode->i_uid;
}
diff --git a/fs/open.c b/fs/open.c
index a47a0a7..82832d8 100644
--- a/fs/open.c
+++ b/fs/open.c
@@ -435,9 +435,13 @@ SYSCALL_DEFINE1(chroot, const char __user *, filename)
if (error)
goto dput_and_out;
- error = -EPERM;
+ /* Are we in a nested chroot by a regular, non root, user? */
+ if (current->user_chroot != CHROOT_USER_MODE)
+ current->user_chroot = CHROOT_ROOT_MODE;
+
if (!capable(CAP_SYS_CHROOT))
- goto dput_and_out;
+ current->user_chroot = CHROOT_USER_MODE;
+
error = security_path_chroot(&path);
if (error)
goto dput_and_out;
diff --git a/include/linux/sched.h b/include/linux/sched.h
index 9e960d4..315e6fe 100644
--- a/include/linux/sched.h
+++ b/include/linux/sched.h
@@ -30,6 +30,16 @@
#define CLONE_NEWNET 0x40000000 /* New network namespace */
#define CLONE_IO 0x80000000 /* Clone io context */
+ /*
+ * chroot syscall Modes: INIT, USER, ROOT
+ * Init mode is to be used only by main.
+ * User mode is initialized when a non-root user tries to enter chroot mode.
+ * ROOT mode is the normal mode of operation for chroot.
+ */
+#define CHROOT_INIT 0
+#define CHROOT_USER_MODE 1
+#define CHROOT_ROOT_MODE 2
+
/*
* Scheduling policies
*/
@@ -1232,6 +1242,8 @@ struct task_struct {
unsigned int flags; /* per process flags, defined below */
unsigned int ptrace;
+ unsigned int user_chroot;
+
#ifdef CONFIG_SMP
struct llist_node wake_entry;
int on_cpu;
diff --git a/init/main.c b/init/main.c
index 0ec0731..044c655 100644
--- a/init/main.c
+++ b/init/main.c
@@ -781,6 +781,7 @@ static noinline int init_post(void)
current->signal->flags |= SIGNAL_UNKILLABLE;
+ current->user_chroot = CHROOT_INIT;
if (ramdisk_execute_command) {
run_init_process(ramdisk_execute_command);
diff --git a/kernel/fork.c b/kernel/fork.c
index 0269b2a..7f6d662 100644
--- a/kernel/fork.c
+++ b/kernel/fork.c
@@ -276,6 +276,8 @@ static struct task_struct *dup_task_struct(struct task_struct *orig)
if (err)
goto out;
+ tsk->user_chroot = orig->user_chroot;
+
tsk->stack = ti;
setup_thread_stack(tsk, orig);
--
1.7.9.5
next prev parent reply other threads:[~2013-03-20 12:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 12:53 [PATCH 0/3] Patches to enable " Tal Tchwella
2013-03-20 12:53 ` Tal Tchwella [this message]
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 13:09 ` [PATCH 1/3] enabled " tal.tchwella
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-2-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