From: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Alexey Dobriyan <adobriyan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Linux Containers <containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: Re: [PATCH 1/1] cr: use a new capability to authorize c/r
Date: Tue, 12 May 2009 16:17:03 -0500 [thread overview]
Message-ID: <20090512211703.GA6510@us.ibm.com> (raw)
In-Reply-To: <20090512205932.GA4346-2ev+ksY9ol182hYKe6nXyg@public.gmane.org>
Quoting Alexey Dobriyan (adobriyan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org):
> On Tue, May 12, 2009 at 10:07:13AM -0500, Serge E. Hallyn wrote:
> > do you object to this patch? The idea is to not give away any
> > privilege not otherwise needed.
>
> > --- a/checkpoint/sys.c
> > +++ b/checkpoint/sys.c
> > @@ -281,7 +281,7 @@ asmlinkage long sys_checkpoint(pid_t pid, int fd, unsigned long flags)
> > if (flags & ~CKPT_USER_FLAGS)
> > return -EINVAL;
> >
> > - if (!ckpt_unpriv_allowed && !capable(CAP_SYS_ADMIN))
> > + if (!ckpt_unpriv_allowed && !capable(CAP_CHECKPOINT_RESTART))
> > return -EPERM;
> >
> > if (pid == 0)
> > @@ -318,7 +318,7 @@ asmlinkage long sys_restart(int crid, int fd, unsigned long flags)
> > if (flags)
> > return -EINVAL;
> >
> > - if (!ckpt_unpriv_allowed && !capable(CAP_SYS_ADMIN))
> > + if (!ckpt_unpriv_allowed && !capable(CAP_CHECKPOINT_RESTART))
> > return -EPERM;
> >
> > /* FIXME: for now, we use 'crid' as a pid */
> > diff --git a/include/linux/capability.h b/include/linux/capability.h
> > index 572b5a0..a593391 100644
> > --- a/include/linux/capability.h
> > +++ b/include/linux/capability.h
> > @@ -357,7 +357,9 @@ struct cpu_vfs_cap_data {
> >
> > #define CAP_MAC_ADMIN 33
> >
> > -#define CAP_LAST_CAP CAP_MAC_ADMIN
> > +#define CAP_CHECKPOINT_RESTART 34
>
> I don't know if this is really needed.
>
> If you allow restart(2) for everyone, you can during struct cred
> restoration check if, say, capabilities coming from image are more
> strict than capabilities of restorer, that aux groups are a subset of
> aux groups of restorer and so on.
Yes, I do all of that in the task credentials restore patchset I sent
yesterday.
> You still need these checks, otherwise CAP_CHECKPOINT_RESTART is much
> more powerful than it suggests.
Absolutely. This patch I sent here is for Oren's checkpoint/restart
tree, which already makes sure (well aims to make sure) that at every
step of the way the task doing sys_restart() has the appopriate
privilege.
> I'm going to try and see how hard will it be.
-serge
prev parent reply other threads:[~2009-05-12 21:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 15:07 [PATCH 1/1] cr: use a new capability to authorize c/r Serge E. Hallyn
[not found] ` <20090512150713.GA32064-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-05-12 20:59 ` Alexey Dobriyan
[not found] ` <20090512205932.GA4346-2ev+ksY9ol182hYKe6nXyg@public.gmane.org>
2009-05-12 21:17 ` Serge E. Hallyn [this message]
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=20090512211703.GA6510@us.ibm.com \
--to=serue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=adobriyan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@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.