[PATCH] devpts: Add ptmx_uid and ptmx_gid options
James.Bottomley at HansenPartnership.com
Thu Apr 2 10:12:05 UTC 2015
On Tue, 2015-03-31 at 16:17 +0200, Alexander Larsson wrote:
> On tis, 2015-03-31 at 17:08 +0300, James Bottomley wrote:
> > On Tue, 2015-03-31 at 06:59 -0700, Andy Lutomirski wrote:
> > >
> > > I don't think that this is correct. That user can already create a
> > > nested userns and map themselves as 0 inside it. Then they can mount
> > > devpts.
> > I don't mind if they create a container and control the isolated ttys in
> > that sub container in the VPS; that's fine. I do mind if they get
> > access to the ttys in the VPS.
> > If you can convince me (and the rest of Linux) that the tty subsystem
> > should be mountable by an unprivileged user generally, then what you
> > propose is OK.
> That is controlled by the general rights to mount stuff. I.e. unless you
> have CAP_SYS_ADMIN in the VPS container you will not be able to mount
> devpts there. You can only do it in a subcontainer where you got
> permissions to mount via using user namespaces.
OK let me try again. Fine, if you want to speak capabilities, you've
given a non-root user an unexpected capability (the capability of
creating a ptmx device). But you haven't used a capability separation
to do this, you've just hard coded it via a mount parameter mechanism.
If you want to do this thing, do it properly, so it's acceptable to the
whole of Linux, not a special corner case for one particular type of
Security breaches are created when people code in special, little used,
corner cases because they don't get as thoroughly tested and inspected
as generally applicable mechanisms.
What you want is to be able to use the tty subsystem as a non root user:
fine, but set that up globally, don't hide it in containers so a lot
fewer people care.
More information about the Containers