From: Mike Frysinger <vapier@gentoo.org>
To: "U.Mutlu" <for-gmane@mutluit.com>
Cc: util-linux@vger.kernel.org
Subject: Re: unshare -m for non-root user
Date: Sun, 15 Nov 2015 07:42:11 -0500 [thread overview]
Message-ID: <20151115124211.GA5949@vapier.lan> (raw)
In-Reply-To: <n29sg5$15j$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1341 bytes --]
On 15 Nov 2015 13:06, U.Mutlu wrote:
> Mike Frysinger wrote on 11/15/2015 07:28 AM:
> > On 15 Nov 2015 03:10, U.Mutlu wrote:
> >> Mike Frysinger wrote on 11/15/2015 02:24 AM:
> >>> On 15 Nov 2015 01:49, U.Mutlu wrote:
> >>>> So, then the question remains: how to give non-root user a secure mount
> >>>
> >>> no, it doesn't. at least two people have already told you how to do it:
> >>> use the usernamespace (-U) option that unshare already supports.
> >>
> >> It's not yet clear for me how to use that. Can you give an example?
> >> unshare -U /bin/bash
> >
> > the unshare(1) man page already includes an example:
> > $ unshare --map-root-user --user sh -c whoami
> > root
>
> No, firstly there is no such example in man unshare, secondly it doesn't do here:
> $ unshare --map-root-user --user sh -c whoami
> unshare: unshare failed: Operation not permitted
>
> Is there maybe a bug in the Debian version?
complain to Debian. iirc, they break their kernels on purpose by adding
non-standard caps which disallow userns usage.
> And thirdly: is that not even more dangerous to give a user root permission
> then? I don't understand this philosophy. Or, where is the trick in this?
you aren't actually root. you'll probably want to read:
https://lwn.net/Articles/532593/
man user_namespaces
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-11-15 12:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 2:09 unshare -m for non-root user U.Mutlu
2015-10-30 10:22 ` Karel Zak
2015-11-14 2:43 ` U.Mutlu
2015-11-14 3:53 ` Eric W. Biederman
2015-11-14 7:25 ` U.Mutlu
2015-11-14 18:17 ` Isaac Dunham
2015-11-14 21:07 ` U.Mutlu
2015-11-15 0:49 ` U.Mutlu
2015-11-15 1:24 ` Mike Frysinger
2015-11-15 2:10 ` U.Mutlu
2015-11-15 6:28 ` Mike Frysinger
2015-11-15 12:06 ` U.Mutlu
2015-11-15 12:42 ` Mike Frysinger [this message]
2015-11-15 15:56 ` U.Mutlu
2015-11-15 18:49 ` Mike Frysinger
2015-11-15 20:25 ` Ángel González
2015-11-16 2:01 ` U.Mutlu
2015-10-30 16:49 ` Mike Frysinger
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=20151115124211.GA5949@vapier.lan \
--to=vapier@gentoo.org \
--cc=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