From: "Askar Safin" <safinaskar@mail.ru>
To: "Mickaël Salaün" <mic@digikod.net>,
kernel-hardening@lists.openwall.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH v5 1/1] fs: Allow no_new_privs tasks to call chroot(2)
Date: Sat, 27 Mar 2021 02:12:42 +0300 [thread overview]
Message-ID: <1616800362.522029786@f737.i.mail.ru> (raw)
Hi. Unprivileged users already can do chroot. He should simply create userns and then call "chroot" inside. As an LWN commenter noted, you can simply run
"unshare -r /usr/sbin/chroot some-dir". (I recommend reading all comments: https://lwn.net/Articles/849125/ .)
Also: if you need chroot for path resolving only, consider openat2 with RESOLVE_IN_ROOT ( https://lwn.net/Articles/796868/ ).
==
Askar Safin
https://github.com/safinaskar
next reply other threads:[~2021-03-27 10:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 23:12 Askar Safin [this message]
2021-03-27 18:56 ` [PATCH v5 1/1] fs: Allow no_new_privs tasks to call chroot(2) Mickaël Salaün
-- strict thread matches above, loose matches on Subject: below --
2021-03-16 20:36 [PATCH v5 0/1] Unprivileged chroot Mickaël Salaün
2021-03-16 20:36 ` [PATCH v5 1/1] fs: Allow no_new_privs tasks to call chroot(2) Mickaël Salaün
2021-03-30 17:01 ` Mickaël Salaün
2021-03-30 17:19 ` Casey Schaufler
2021-03-30 18:11 ` Mickaël Salaün
2021-03-30 18:22 ` Casey Schaufler
2021-03-30 18:40 ` Casey Schaufler
2021-03-30 19:28 ` Mickaël Salaün
2021-03-30 22:53 ` Casey Schaufler
2021-03-31 6:03 ` Kees Cook
2021-03-31 6:33 ` Al Viro
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=1616800362.522029786@f737.i.mail.ru \
--to=safinaskar@mail.ru \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
/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.