public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: util-linux@vger.kernel.org, Neil Horman <nhorman@tuxdriver.com>,
	"Serge E. Hallyn" <serge@hallyn.com>,
	"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Subject: Re: [PATCH] enter: new command (light wrapper around setns)
Date: Fri, 11 Jan 2013 17:13:20 +0100	[thread overview]
Message-ID: <20130111161320.GA16206@x2.net.home> (raw)
In-Reply-To: <876234812z.fsf@xmission.com>

On Fri, Jan 11, 2013 at 02:29:24AM -0800, Eric W. Biederman wrote:
> 
> Inspired by unshare, enter is a simple wrapper around setns that
> allows running a new process in the context of an existing process.

 It would be really nice to have "ns" in the name -- for example
 "enterns" sounds good.

> While doing a final check on this patch I just realized I am a week or
> two late to the discussion.

 Yep :-)

> Little things like retaining the the ability for unshare to be suid root
> safely and sanely become intractable if you call setns() and join a
> user namespace.  

 Do you have any example (use case) with suid unshare(1)? 

> Supporting the ability for the command to be setuid root does not
> work in combination with the user namespace.  As after entering
> the user namespace you can not reliably change your uid back to
> your uid without setuid as your uid may not be mapped.
> 
> When joining an existing mount namespace you most likely want to change
> your root directory and your working directory to the directory of the
> process whoose mount namespace you are entering.  Something you don't
> even think about when just unsharing a mount namespace.
> 
> Then there is the practical wish to call fork after entering a pid
> namespace and before launching a command.  You don't always want that
> but almost always so that the command will actually be run in the new
> pid namespace with a new pid, instead of having it's children in the new
> pid namespace.
> 
> I really can't see support for using setns being in the same binary as
> unshare that just mixes two different but closely related things that
> will want to evolve in different directions.
> 
> My inclination is to send a follow up patch to remove setns and migrate
> from unshare. 

 unnecessary, "git revert" works fine :-)

> And a second patch to add pid and user namespace support
> to unshare.  But since I am going against the way that seems to have
> already been decided I will hold off on those patches until after we
> there is agreement on this one.

 well, the decision has been based on little different context. 
 
 I have no problem to revert the change if there is a real use case 
 with suid and if the setns() goals will be incompatible with the 
 way how people use unshare(1) command.

    Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

  parent reply	other threads:[~2013-01-11 16:13 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-11 10:29 [PATCH] enter: new command (light wrapper around setns) Eric W. Biederman
2013-01-11 10:54 ` Michael Kerrisk (man-pages)
2013-01-11 11:10   ` Eric W. Biederman
2013-01-11 13:13     ` Ángel González
2013-01-12  8:59     ` Michael Kerrisk (man-pages)
2013-01-11 16:13 ` Karel Zak [this message]
2013-01-11 22:11   ` Eric W. Biederman
2013-01-12  9:01     ` Michael Kerrisk (man-pages)
2013-01-11 22:46   ` [PATCH] nsenter: " Eric W. Biederman
2013-01-11 23:45     ` Mike Frysinger
2013-01-14  8:28       ` Karel Zak
2013-01-17  0:33         ` [PATCH 0/5] nsenter review comment fixes Eric W. Biederman
2013-01-17  0:34           ` [PATCH 1/5] nsenter: Enhance waiting for a child process Eric W. Biederman
2013-01-17  0:34           ` [PATCH 2/5] nsenter: Properly spell significant in a comment Eric W. Biederman
2013-01-17  0:35           ` [PATCH 3/5] nsenter: Add const to declarations where possible Eric W. Biederman
2013-01-17  0:35           ` [PATCH 4/5] nsenter: Replace a bare strtoul with strtoul_or_err Eric W. Biederman
2013-01-17  0:36           ` [PATCH 5/5] unshare,nsenter: Move the old libc handling into a common header namespace.h Eric W. Biederman
2013-01-17  3:11           ` [PATCH 0/5] nsenter review comment fixes Mike Frysinger
2013-01-17 12:35           ` Karel Zak
2013-01-15 18:51     ` [PATCH] nsenter: new command (light wrapper around setns) Serge E. Hallyn
2013-01-17 12:34     ` Karel Zak
2013-01-11 22:53   ` [PATCH] unshare: Add support for the pid and user namespaces Eric W. Biederman
2013-01-17 12:35     ` Karel Zak
2013-01-17 12:56       ` Eric W. Biederman

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=20130111161320.GA16206@x2.net.home \
    --to=kzak@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=mtk.manpages@gmail.com \
    --cc=nhorman@tuxdriver.com \
    --cc=serge@hallyn.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