From: Mike Frysinger <vapier@gentoo.org>
To: "U.Mutlu" <for-gmane@mutluit.com>
Cc: util-linux@vger.kernel.org
Subject: Re: unshare -m should not be a privileged option
Date: Sun, 15 Nov 2015 23:19:31 -0500 [thread overview]
Message-ID: <20151116041931.GC5949@vapier.lan> (raw)
In-Reply-To: <n2besp$j56$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1212 bytes --]
On 16 Nov 2015 03:26, U.Mutlu wrote:
> I'm proposing that "unshare -m" should not be a privileged option,
what you're asking for is not coming from util-linux. unshare is merely an
interface to the unshare() syscall. if you dislike the security semantics
there, you can post to the namespace mailing list:
https://lists.linuxfoundation.org/mailman/listinfo/containers
> Therefore the -m option (and maybe even most of the other options) of unshare
> should be made to work for users, without needing root permission.
they do already -- with user namespaces. if you give people the ability to
mount anything in the existing mount namespace, you open up attacks:
- create an ext2 fs as the user with some setuid programs
- create a new mount namespace
- mount that image
- instant root
> 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
> As said in previous postings of mine: "chmod u+s unshare" does what I need,
i would like shell access to your systems please. free root is fun.
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-11-16 4:19 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 [this message]
2015-11-16 15:43 ` user namespaces: user mapping U.Mutlu
2015-11-16 23:41 ` U.Mutlu
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=20151116041931.GC5949@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