From: "U.Mutlu" <for-gmane@mutluit.com>
To: util-linux@vger.kernel.org
Subject: unshare -m should not be a privileged option
Date: Mon, 16 Nov 2015 03:26:33 +0100 [thread overview]
Message-ID: <n2besp$j56$1@ger.gmane.org> (raw)
I'm proposing that "unshare -m" should not be a privileged option,
because in practice it is IMO used like this:
unshare -m /bin/bash
now user can do his mounts (mostly via sudo)
The user should need the root permission (or CAP_ADMIN or whatever
caps it needs) only for the mount and unmount cmds, but not for "unshare -m".
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.
Maybe even better would be to define the users in a new conf file
/etc/unshare.conf or so.
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.
I like "unshare -m", but it should work also for unprivileged users without
needing sudo.
As said in previous postings of mine: "chmod u+s unshare" does what I need,
but I don't know if that solution will continue working in newer versions.
...just my .02 cents from the field as admin and user
next reply other threads:[~2015-11-16 2:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 2:26 U.Mutlu [this message]
2015-11-16 4:19 ` unshare -m should not be a privileged option Mike Frysinger
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='n2besp$j56$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