mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: akpm@linux-foundation.org, linux-fsdevel@vger.kernel.org,
	containers@lists.osdl.org, util-linux-ng@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [patch 0/8] unprivileged mount syscall
Date: Mon, 9 Apr 2007 09:38:02 -0500	[thread overview]
Message-ID: <20070409143802.GB4891@sergelap.austin.ibm.com> (raw)
In-Reply-To: <E1Ha4cN-0004rc-00@dorka.pomaz.szeredi.hu>

Quoting Miklos Szeredi (miklos@szeredi.hu):
> > > This patchset adds support for keeping mount ownership information in
> > > the kernel, and allow unprivileged mount(2) and umount(2) in certain
> > > cases.
> > 
> > No replies, huh?
> 
> All we need is a comment from Andrew, and the replies come flooding in ;)
> 
> > My knowledge of the code which you're touching is not strong, and my spare
> > reviewing capacity is not high.  And this work does need close review by
> > people who are familar with the code which you're changing.
> > 
> > So could I suggest that you go for a dig through the git history, identify
> > some individuals who look like they know this code, then do a resend,
> > cc'ing those people?  Please also cc linux-kernel on that resend.
> 
> OK.
> 
> > > One thing that is missing from this series is the ability to restrict
> > > user mounts to private namespaces.  The reason is that private
> > > namespaces have still not gained the momentum and support needed for
> > > painless user experience.  So such a feature would not yet get enough
> > > attention and testing.  However adding such an optional restriction
> > > can be done with minimal changes in the future, once private
> > > namespaces have matured.
> > 
> > I suspect the people who developed and maintain nsproxy would disagree ;)
> 
> Well, they better show me some working and simple-to-use userspace
> code, because I've not seen anything like that related to mount
> namespaces.

If you mean to test/exploit them, see
http://lxc.sourceforge.net/patches/2.6.20/2.6.20-lxc8/broken-out/tests/

Compile the ns_exec.c program and do

	ns_exec -m /bin/sh

to get a shell in a new mounts namespace.

> pam_namespace.so is one example of a non-working, but probably-not-too-
> hard-to-fix one.

Non-working?  I sure hope the one used for LSPP certification is
working...  As is the ugly version I wrote 18 mounts ago and use on my
laptop.

> I'm just saying this is not yet something that Joe Blow would just
> enable by ticking a box in their desktop setup wizard, and it would
> all work flawlessly thereafter.  There's still a _long_ way towards
> that, and mostly in userspace.

I'm not sure there's a that long a way to go, but clearly we need to be
showing users what they can do, or they'll never work their way towards
there.

For instance, as you say, a user admin gui with a checkmark and text
boxes saying 'enter new namespace on login', 'create private /tmp',
and 'create private dmcrypted /home' would be trivial right now.

-serge

  reply	other threads:[~2007-04-09 14:38 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070404183012.429274832@szeredi.hu>
2007-04-06 23:02 ` Andrew Morton
2007-04-06 23:16   ` H. Peter Anvin
2007-04-06 23:55     ` Jan Engelhardt
2007-04-07  0:22       ` H. Peter Anvin
2007-04-07  3:40         ` Eric Van Hensbergen
2007-04-07  6:48           ` Miklos Szeredi
2007-04-10  8:52     ` Ian Kent
2007-04-11 10:48       ` Miklos Szeredi
2007-04-11 13:48         ` Ian Kent
2007-04-11 14:26           ` Serge E. Hallyn
2007-04-11 14:27             ` Ian Kent
2007-04-11 14:45               ` Serge E. Hallyn
2007-04-07  6:41   ` Miklos Szeredi
2007-04-09 14:38     ` Serge E. Hallyn [this message]
2007-04-09 16:24       ` Miklos Szeredi
2007-04-09 17:07         ` Serge E. Hallyn
2007-04-09 17:46           ` Ram Pai
2007-04-09 18:25             ` H. Peter Anvin
2007-04-10 10:33             ` Karel Zak
2007-04-09 20:10           ` Miklos Szeredi
2007-04-10  8:38             ` Ram Pai
2007-04-11 10:44               ` Miklos Szeredi
2007-04-11 18:28                 ` Ram Pai
2007-04-13 11:58                   ` Miklos Szeredi
2007-04-13 13:28                     ` Serge E. Hallyn
2007-04-13 14:05                       ` Miklos Szeredi
2007-04-13 21:44                         ` Serge E. Hallyn
2007-04-15 20:39                           ` Miklos Szeredi
2007-04-16  1:11                             ` Serge E. Hallyn
2007-04-16  8:18                         ` Ram Pai
2007-04-16  9:27                           ` Miklos Szeredi
2007-04-16 15:40                             ` Eric W. Biederman
2007-04-16 15:55                               ` Miklos Szeredi
2007-04-13 20:07                     ` Karel Zak
2007-04-15 20:21                       ` Miklos Szeredi
2007-04-16  7:59                     ` Ram Pai

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=20070409143802.GB4891@sergelap.austin.ibm.com \
    --to=serue@us.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=containers@lists.osdl.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=util-linux-ng@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

all inboxes | Powered by JetHome®