From: Alexander Larsson <alexl@redhat.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Andy Lutomirski <luto@amacapital.net>,
gnome-os-list@gnome.org,
Linux Containers <containers@lists.linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
mclasen@redhat.com, "Eric W. Biederman" <ebiederm@xmission.com>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] devpts: Add ptmx_uid and ptmx_gid options
Date: Tue, 31 Mar 2015 15:11:11 +0200 [thread overview]
Message-ID: <1427807471.4411.18.camel@redhat.com> (raw)
In-Reply-To: <1427807248.2117.117.camel@HansenPartnership.com>
On tis, 2015-03-31 at 16:07 +0300, James Bottomley wrote:
> On Tue, 2015-03-31 at 09:57 +0200, Alexander Larsson wrote:
> > On fre, 2015-03-27 at 10:03 +0100, James Bottomley
> > >
> > > > On Fri, Feb 20, 2015 at 5:04 PM, Andy Lutomirski <luto@amacapital.net> wrote:
> > > > > It's currently impossible to mount devpts in a user namespace that
> > > > > has no root user, since ptmx can't be created.
> > >
> > > This is where I stopped reading because it's not true ... because it is
> > > possible, you just do it from the host as real root.
> >
> > The point is being able to set up a container as a user, not requiring
> > the setup to be run as root at all. In my case container is a desktop
> > application which will be started by the user, and will run as the user.
> > There is no root involved in the call chain at all.
>
> I don't really like that use case: Most container setups are under the
> control of an orchestration system (like LXC, OpenVZ or even Docker).
Well, I'm doing something different from a server side orchestration
framework. I'm doing sandboxed desktop apps.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Alexander Larsson Red Hat, Inc
alexl@redhat.com alexander.larsson@gmail.com
He's an underprivileged sweet-toothed master criminal in a wheelchair.
She's a psychotic out-of-work opera singer with the power to see death.
They fight crime!
next prev parent reply other threads:[~2015-03-31 13:11 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-21 1:04 [PATCH] devpts: Add ptmx_uid and ptmx_gid options Andy Lutomirski
2015-03-26 19:29 ` Andy Lutomirski
2015-03-27 9:03 ` James Bottomley
2015-03-31 7:57 ` Alexander Larsson
2015-03-31 13:06 ` Andy Lutomirski
2015-03-31 13:07 ` James Bottomley
2015-03-31 13:11 ` Alexander Larsson [this message]
2015-03-31 13:12 ` Andy Lutomirski
2015-03-31 13:23 ` James Bottomley
2015-03-31 13:44 ` Andy Lutomirski
2015-03-31 13:55 ` James Bottomley
2015-03-31 13:59 ` Andy Lutomirski
2015-03-31 14:08 ` James Bottomley
2015-03-31 14:17 ` Alexander Larsson
2015-04-02 10:12 ` James Bottomley
2015-04-02 14:06 ` Andy Lutomirski
2015-04-02 14:29 ` Alexander Larsson
2015-04-02 14:33 ` Andy Lutomirski
2015-04-02 15:49 ` Serge Hallyn
2015-04-02 18:27 ` Eric W. Biederman
2015-05-27 21:32 ` Andy Lutomirski
2015-05-28 16:44 ` Eric W. Biederman
2015-05-28 17:01 ` Alexander Larsson
2015-05-28 17:14 ` Eric W. Biederman
2015-05-28 17:35 ` Alexander Larsson
2015-05-28 20:06 ` Alexander Larsson
2015-05-28 20:17 ` Kenton Varda
2015-05-28 21:50 ` Eric W. Biederman
2015-05-28 17:30 ` Andy Lutomirski
2015-05-28 19:42 ` Eric W. Biederman
2016-03-08 4:59 ` Andy Lutomirski
2016-03-08 9:16 ` Alexander Larsson
2016-03-08 18:17 ` Andy Lutomirski
2015-05-18 21:04 ` Alexander Larsson
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=1427807471.4411.18.camel@redhat.com \
--to=alexl@redhat.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=containers@lists.linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=gnome-os-list@gnome.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mclasen@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).