public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Cc: Alex Dubov <alex.dubov@gmail.com>,
	linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk,
	corbet@lwn.net, richardcochran@gmail.com
Subject: Re: syscall: introduce sendfd() syscall (v.2)
Date: Sun, 7 Dec 2014 10:55:29 +0100	[thread overview]
Message-ID: <20141207095529.GA18733@amd> (raw)
In-Reply-To: <20141205132250.6f2f9ec1@lxorguk.ukuu.org.uk>

On Fri 2014-12-05 13:22:50, One Thousand Gnomes wrote:
> 
> > 2.a. If task A has sufficient capabilities to send signals to task B, then
> > task A is already in position to do anything it wants with task B, including
> > killing it outright.
> 
> Not entirely true.
> 
> - We have securirty models like SELinux
> - We have namespaces and being able to send an fd between namespaces is
>   not quite as flexible as you would make it
> 
> I suspect therefore it needs security hooks but otherwise looks more sane
> than the current AF_UNIX approach.

The right test for "can do anything" is "can_ptrace()"...
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

      parent reply	other threads:[~2014-12-07  9:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-03  9:00 syscall: introduce sendfd() syscall (v.2) Alex Dubov
2014-12-03  9:00 ` [PATCH] " Alex Dubov
     [not found]   ` <CAE2SPAa3FZz6MH41UB-CmruFw0kCTq=KS5MkNXMaiEidpSGkSg@mail.gmail.com>
2014-12-06  3:55     ` Alex Dubov
2014-12-05 13:22 ` One Thousand Gnomes
2014-12-06  4:13   ` Alex Dubov
2014-12-07  9:55   ` Pavel Machek [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=20141207095529.GA18733@amd \
    --to=pavel@ucw.cz \
    --cc=alex.dubov@gmail.com \
    --cc=corbet@lwn.net \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richardcochran@gmail.com \
    --cc=viro@zeniv.linux.org.uk \
    /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