All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serge@hallyn.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Andy Lutomirski <luto@amacapital.net>,
	David Drysdale <drysdale@google.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Serge E. Hallyn" <serge@hallyn.com>
Subject: Re: RFC: fsyscall
Date: Thu, 10 Sep 2015 08:43:50 -0500	[thread overview]
Message-ID: <20150910134350.GC27602@mail.hallyn.com> (raw)
In-Reply-To: <87mvwwfngy.fsf@x220.int.ebiederm.org>

On Tue, Sep 08, 2015 at 07:25:17PM -0500, Eric W. Biederman wrote:
> Andy Lutomirski <luto@amacapital.net> writes:
> 
> > On Tue, Sep 8, 2015 at 4:07 PM, Eric W. Biederman <ebiederm@xmission.com> wrote:
> 
> >> Perhaps I had missed it but I don't recall capsicum being able to wrap
> >> things like reboot(2).
> >>
> >
> > Ah, so you want to be able to grant BPF-defined capabilities :)
> 
> Pretty much.
> 
> Where I am focusing is turning Posix capabilities into real
> capabilities.  I would not mind if the functionality was a bit more
> general.  Say to be able to handle things like security labels, or
> anywhere else you might reasonably be asked can you do X?
> 
> But I would be happy if we just managed to wrap the Posix capabilities
> and turned them into real capablilities.

If there were a clever way to exec an open fd, then you could do this
by passing an fd to a copy of /bin/reboot which has fP=CAP_SYS_BOOT,
or prefereably fI=CAP_SYS_BOOT,fE=1 and leave pI=CAP_SYS_BOOT in the
task.

A cleaner way to do this is to have a service which can reboot, which
looks at unix socket peercreds to determine whether the granter may
reboot, then passes it an fd which the granter may pass to a grantee.
Then the grantee passes the fd to the service, which recognizes it and
reboots.

-serge

  parent reply	other threads:[~2015-09-10 13:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-08 22:35 RFC: fsyscall Eric W. Biederman
2015-09-08 22:55 ` Andy Lutomirski
2015-09-08 23:07   ` Eric W. Biederman
2015-09-08 23:18     ` Andy Lutomirski
2015-09-09  0:25       ` Eric W. Biederman
2015-09-09 17:27         ` David Drysdale
2015-09-09 19:33           ` Eric W. Biederman
2015-09-10 13:35             ` Serge E. Hallyn
2015-09-10 13:28           ` Serge E. Hallyn
2015-09-10 13:43         ` Serge E. Hallyn [this message]
2015-09-10 13:51           ` David Drysdale
2015-09-10 14:01             ` Serge E. Hallyn
2015-09-10 14:03               ` Serge E. Hallyn
2015-09-10 14:04                 ` Serge E. Hallyn

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=20150910134350.GC27602@mail.hallyn.com \
    --to=serge@hallyn.com \
    --cc=drysdale@google.com \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    /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.