From: Richard Weinberger <richard@nod.at>
To: Alejandro Colomar <alx@kernel.org>
Cc: "Serge E. Hallyn" <serge@hallyn.com>,
christian <christian@brauner.io>, ipedrosa <ipedrosa@redhat.com>,
gscrivan <gscrivan@redhat.com>,
"Andreas Grünbacher" <andreas.gruenbacher@gmail.com>,
acl-devel <acl-devel@nongnu.org>,
linux-man <linux-man@vger.kernel.org>,
linux-api <linux-api@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
ebiederm <ebiederm@xmission.com>
Subject: Re: [PATCH 2/3] user_namespaces.7: Document pitfall with negative permissions and user namespaces
Date: Tue, 29 Aug 2023 23:39:10 +0200 (CEST) [thread overview]
Message-ID: <300010998.1870230.1693345150665.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <51d4691d-dbc8-2e70-edc8-3b5814213c3f@kernel.org>
----- Ursprüngliche Mail -----
> Von: "Alejandro Colomar" <alx@kernel.org>
> $ unshare ‐S 0 ‐G 0 ‐‐map‐users=100000,0,65536 ‐‐map‐groups=100000,0,65536 id
> unshare: failed to execute ‐S: No such file or directory
Well, maybe your unshare tool is too old.
AFAIK it uses newuidmap only in recent versions.
You can achieve the very same als using podman in rootless mode.
e.g.
podman run -it -v /scratch:/scratch/ bash -c "cat /scratch/games/game.txt"
Thanks,
//richard
next prev parent reply other threads:[~2023-08-29 21:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 20:58 [PATCH 0/3] Document impact of user namespaces and negative permissions Richard Weinberger
2023-08-29 20:58 ` [PATCH 1/3] man: Document pitfall with negative permissions and user namespaces Richard Weinberger
2023-08-30 8:19 ` Christian Brauner
2023-08-29 20:58 ` [PATCH 2/3] user_namespaces.7: " Richard Weinberger
2023-08-29 21:32 ` Alejandro Colomar
2023-08-29 21:38 ` Alejandro Colomar
2023-08-29 21:40 ` Richard Weinberger
2023-08-29 21:39 ` Richard Weinberger [this message]
2023-08-29 21:40 ` Alejandro Colomar
2023-08-30 9:26 ` Alejandro Colomar
2023-08-30 8:18 ` Christian Brauner
2023-08-29 20:58 ` [PATCH 3/3] man: " Richard Weinberger
2023-08-30 8:19 ` Christian Brauner
2023-08-29 21:26 ` [PATCH 0/3] Document impact of user namespaces and negative permissions Alejandro Colomar
2023-08-29 21:32 ` Richard Weinberger
2023-09-13 14:35 ` Alejandro Colomar
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=300010998.1870230.1693345150665.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=acl-devel@nongnu.org \
--cc=alx@kernel.org \
--cc=andreas.gruenbacher@gmail.com \
--cc=christian@brauner.io \
--cc=ebiederm@xmission.com \
--cc=gscrivan@redhat.com \
--cc=ipedrosa@redhat.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=serge@hallyn.com \
/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;
as well as URLs for NNTP newsgroup(s).