From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 216215] clone and unshare say CAP_SYS_ADMIN is required to create new namespaces
Date: Mon, 11 Jul 2022 08:01:24 +0000 [thread overview]
Message-ID: <bug-216215-11311-uSrlZVvYdZ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216215-11311@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216215
--- Comment #2 from pxeger (linuxkernelbugzilla@pxeger.com) ---
Ah, I understand the confusion I was having now: all namespaces, *except user
namespaces*, require CAP_SYS_ADMIN. But creating a new user namespace
automatically confers a full set of capabilities. So, when using clone(2) with
CLONE_NEWUSER and some other CLONE_NEW* flags for other namespaces, at the same
time, you don't need CAP_SYS_ADMIN in the parent, because it's given to the
child during the clone call.
Is this worth mentioning somewhere?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2022-07-11 8:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 18:50 [Bug 216215] New: clone and unshare say CAP_SYS_ADMIN is required to create new namespaces bugzilla-daemon
2022-07-10 22:19 ` [Bug 216215] " bugzilla-daemon
2022-07-11 8:01 ` bugzilla-daemon [this message]
2022-07-19 15:04 ` bugzilla-daemon
2022-09-06 12:31 ` bugzilla-daemon
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=bug-216215-11311-uSrlZVvYdZ@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-man@vger.kernel.org \
/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