From: Petr Vorel <pvorel@suse.cz>
To: "Seth Forshee (DigitalOcean)" <sforshee@kernel.org>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] containers: override kernel.unprivileged_userns_clone sysctl where needed
Date: Thu, 23 Mar 2023 17:24:59 +0100 [thread overview]
Message-ID: <20230323162459.GA476022@pevik> (raw)
In-Reply-To: <20230323-override-unpriv-userns-sysctl-v1-1-0b62c71acd43@kernel.org>
Hi Seth,
> Some distros have a kernel.unprivileged_userns_clone which when disabled
> forbids users without CAP_SYS_ADMIN in the initial user namespace from
> creating new user namespaces. When disabled the containers user07 and
> user08 tests fail.
> Update these tests to ensure that when this sysctl is present it is set
> to allow unprivileged user namespace creation while the test is running.
Good catch, it's indeed a problem on Debian.
Reviewed-by: Petr Vorel Petr Vorel <pvorel@suse.cz>
Tested-by: Petr Vorel Petr Vorel <pvorel@suse.cz>
BTW it took me a while to find out /proc/sys/kernel/unprivileged_userns_clone is
Debian out of tree patch [1] (The funny note from 2013 "This is a short-term patch")
probably refused by upstream kernel (I've only found 3 years later one of Debian
kernel maintainers Ben Hutchings talking about it [2]).
Kind regards,
Petr
[1] https://salsa.debian.org/kernel-team/linux/-/blob/master/debian/patches/debian/add-sysctl-to-disallow-unprivileged-CLONE_NEWUSER-by-default.patch
[2] https://lore.kernel.org/lkml/1453510799.3734.153.camel@decadent.org.uk/
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-03-23 16:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 15:45 [LTP] [PATCH] containers: override kernel.unprivileged_userns_clone sysctl where needed Seth Forshee (DigitalOcean)
2023-03-23 16:24 ` Petr Vorel [this message]
2023-03-23 16:29 ` Petr Vorel
2023-03-24 12:09 ` Petr Vorel
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=20230323162459.GA476022@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=sforshee@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 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.