From: "Serge E. Hallyn" <serge@hallyn.com>
To: "Serge E. Hallyn" <serge@hallyn.com>
Cc: David Drysdale <drysdale@google.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Andy Lutomirski <luto@amacapital.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: RFC: fsyscall
Date: Thu, 10 Sep 2015 09:03:08 -0500 [thread overview]
Message-ID: <20150910140308.GA28113@mail.hallyn.com> (raw)
In-Reply-To: <20150910140120.GA28071@mail.hallyn.com>
On Thu, Sep 10, 2015 at 09:01:20AM -0500, Serge E. Hallyn wrote:
> On Thu, Sep 10, 2015 at 02:51:28PM +0100, David Drysdale wrote:
> > On Thu, Sep 10, 2015 at 2:43 PM, Serge E. Hallyn <serge@hallyn.com> wrote:
> > > 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
> >
> > execveat(fd, "", argv, envp, AT_EMPTY_PATH) ?
>
> ??? I looked for it but I don't have a manpage for it. I see it at
> man7.org though. Thanks :)
But this isn't quite what I was suggesting. I was suggesting a call which
would exec the fd, not exec a file inside the dirfd.
next prev parent reply other threads:[~2015-09-10 14:03 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
2015-09-10 13:51 ` David Drysdale
2015-09-10 14:01 ` Serge E. Hallyn
2015-09-10 14:03 ` Serge E. Hallyn [this message]
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=20150910140308.GA28113@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox