From: "U.Mutlu" <for-gmane@mutluit.com>
To: util-linux@vger.kernel.org
Subject: Re: user namespaces: user mapping
Date: Tue, 17 Nov 2015 00:41:56 +0100 [thread overview]
Message-ID: <n2dpk4$p47$1@ger.gmane.org> (raw)
In-Reply-To: <n2ctjg$1d0$1@ger.gmane.org>
U.Mutlu wrote on 11/16/2015 04:43 PM:
> Mike Frysinger wrote on 11/16/2015 05:19 AM:
>> On 16 Nov 2015 03:26, U.Mutlu wrote:
>>
>>> The other solution via user namespace is IMHO overkill and in my case
>>> impractical and irritating because user gets a root-prompt (#)
>>> eventhough it is only inside the user namespace.
>>
>> so remap it to your own user instead of to root
>
> Sorry, I forgot the dangers of mounting into existing mount namespace.
> Yes, user namespace seems to be the way to go, so I tried the sample from
> man user_namespaces:
>
> $ ./userns_child_exec -v -p -m -U -z bash
> ./userns_child_exec: PID of child created by clone() is 2950
> ERROR: write /proc/2950/gid_map: Operation not permitted
> About to exec bash
>
> Am I on the right track with the above method for user remapping?
>
> It's maybe that under Debian another sysctl-setting is needed
> for this to work, I'll need to do some research on the net.
> If someone here knows the solution let me know pls.
I did some research on the net, and the findings are:
- user namespaces have their own security holes
- a workaround exists, but then a new problem happens: loop devices cannot
be accessed
Here's the output of a modified (fixed) version of the above pgm,
but mount still not working, even with root-prompt inside the namespace:
$ ./userns_child_exec -v -m -U -z bash
uid=1003 gid=1006 pid=7728
./userns_child_exec: PID of child created by clone() is 7729
uid=1003 gid=1006 pid=7729
map_file=/proc/7729/setgroups map_val=deny
map_file=/proc/7729/uid_map map_val=0 1003 1
map_file=/proc/7729/gid_map map_val=0 1006 1
About to exec bash
# mount -o loop ../mount-test/theFile.img mnt
mount: /home/user/tmp/test/mount-test/theFile.img: failed to setup loop
device: Permission denied
# ls -l /dev/loop*
brw-rw---- 1 nobody nogroup 7, 0 Nov 16 20:01 /dev/loop0
brw-rw---- 1 nobody nogroup 7, 1 Nov 16 20:14 /dev/loop1
brw-rw---- 1 nobody nogroup 7, 2 Nov 16 15:29 /dev/loop2
brw-rw---- 1 nobody nogroup 7, 3 Nov 16 15:29 /dev/loop3
brw-rw---- 1 nobody nogroup 7, 4 Nov 16 15:29 /dev/loop4
brw-rw---- 1 nobody nogroup 7, 5 Nov 16 15:29 /dev/loop5
brw-rw---- 1 nobody nogroup 7, 6 Nov 16 15:29 /dev/loop6
brw-rw---- 1 nobody nogroup 7, 7 Nov 16 15:29 /dev/loop7
crw-rw---- 1 nobody nogroup 10, 237 Nov 16 15:29 /dev/loop-control
Does the user need to create his own loop device(s)?
Hmm. it looks like there is (currently?) a big mess with user namespaces:
https://code.google.com/p/chromium/issues/detail?id=457362
next prev parent reply other threads:[~2015-11-16 23:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 2:26 unshare -m should not be a privileged option U.Mutlu
2015-11-16 4:19 ` Mike Frysinger
2015-11-16 15:43 ` user namespaces: user mapping U.Mutlu
2015-11-16 23:41 ` U.Mutlu [this message]
2015-11-17 4:32 ` Mike Frysinger
2015-11-17 5:25 ` U.Mutlu
2015-11-17 20:58 ` Mike Frysinger
2015-11-17 6:54 ` unshare -m should not be a privileged option U.Mutlu
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='n2dpk4$p47$1@ger.gmane.org' \
--to=for-gmane@mutluit.com \
--cc=util-linux@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