From: "Daniel P. Berrange" <berrange-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Requirements for CAP_SYS_ADMIN on setns() ?
Date: Thu, 6 Jun 2013 11:01:49 +0100 [thread overview]
Message-ID: <20130606100149.GG30217@redhat.com> (raw)
IIUC, currently, in order to be able to invoke setns() the calling
process is required to have CAP_SYS_ADMIN capability. Alternatively
with user namespaces, access is allowed if the process' effective
uid matches the uid of the owner of the namespace.
I have a scenario though that isn't dealt with by those rules. I have
a container that was spawned by uid == 0, and I have an unprivileged
process uid != 0 in the initial namespace that I wish to allow to enter
the namespaces associated with the container.
With the CAP_SYS_ADMIN rule on setns(), it seems that the unprivileged
process will need to execute some setuid binary in order to gain the
CAP_SYS_ADMIN capability required to call setns().
Of course you can't call setns() without first obtaining a file
descriptor corresponding to the /proc/$CONTAINERPID/ns/XXXX namespace
you wish to join. This appears to require elevated privileges too.
Is it not sufficient to rely on the permissions on the /proc/$PID/ns/XXX
file to control access to a namespace, and thus allow setns() without
a CAP_SYS_ADMIN check ? ie setns() is basically useless unless you
already have sufficient privileges to get a file descriptor for the
namespace, so why does setns need an additional privilege check beyond
that done at time of open() on the proc file.
In my scenario this would allow for a privileged daemon to open the
/proc/$PID/ns/XXX file, and then pass the file descriptor back to the
unprivileged process using SCM_RIGHTS, which could then invoke setns().
This kind of privilege separation is perferrable to requiring the
unprivileged process to run some kind of setuid program to gain the
CAP_SYS_ADMIN capability.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next reply other threads:[~2013-06-06 10:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 10:01 Daniel P. Berrange [this message]
[not found] ` <20130606100149.GG30217-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-06-06 13:48 ` Requirements for CAP_SYS_ADMIN on setns() ? Serge Hallyn
2013-06-06 16:26 ` Eric W. Biederman
[not found] ` <87txlb8atb.fsf-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
2013-06-06 16:44 ` Serge E. Hallyn
[not found] ` <20130606164428.GA4687-anj0Drq5vpzx6HRWoRZK3AC/G2K4zDHf@public.gmane.org>
2013-06-06 18:15 ` Eric W. Biederman
[not found] ` <87bo7j6r80.fsf-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
2013-06-07 9:34 ` Daniel P. Berrange
[not found] ` <20130607093459.GB10742-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-06-07 19:18 ` Eric W. Biederman
2013-06-08 19:54 ` Rob Landley
2013-06-09 5:33 ` 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=20130606100149.GG30217@redhat.com \
--to=berrange-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.