From: Mike Frysinger <vapier@gentoo.org>
To: "U.Mutlu" <for-gmane@mutluit.com>
Cc: util-linux@vger.kernel.org
Subject: Re: user namespaces: user mapping
Date: Tue, 17 Nov 2015 15:58:51 -0500 [thread overview]
Message-ID: <20151117205851.GL31395@vapier.lan> (raw)
In-Reply-To: <n2edon$mfu$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 783 bytes --]
this really isn't the place for logical fallacies. it is impossible to prove
any code is entirely bug free (let's ignore the theoretical proof based systems
as they're entirely irrelevant to this discussion). if you have any actual bugs
to report, then do so. otherwise, you're wasting everyone's time.
i think we've all been pretty clear that making unshare, as-is, setuid is
completely wrong and, frankly, stupid. it's trivial to leverage privilege
escalation after that point.
as for enhancing unshare to be aware that it's setuid and thus drop root back
once it's done making the unshare calls, i don't see the point. user namespaces
work already and don't require setuid and are widely available. if you don't
like userns, that's your choice, but not our problem.
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-11-17 20:58 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
2015-11-17 4:32 ` Mike Frysinger
2015-11-17 5:25 ` U.Mutlu
2015-11-17 20:58 ` Mike Frysinger [this message]
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=20151117205851.GL31395@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