public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: David Wagner <daw-usenet@taverner.cs.berkeley.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] capabilities not inherited
Date: Thu, 09 Jun 2005 11:31:23 -0400	[thread overview]
Message-ID: <1118331084.15527.26.camel@mindpipe> (raw)
In-Reply-To: <d89l9a$d3i$1@abraham.cs.berkeley.edu>

On Thu, 2005-06-09 at 14:55 +0000, David Wagner wrote:
> Alexander Nyberg  wrote:
> >tor 2005-06-09 klockan 02:59 +0000 skrev David Wagner:
> >> [...] the sendmail attack [...]
> >
> >I'll look this up but it sounds very weird and I don't see how this
> >would happen with this change.
> 
> Yup, it was a weird one indeed -- which is part of why I'm concerned.
> Take a look at the attack again, then re-read my message.  Maybe my
> concerns will make more sense once you refresh your memory about the
> setuid capabilities attack?  If not, feel free to ask again, and I'll
> try to elaborate.  Here is a pointer to one description of that attack:
>     http://www.cs.berkeley.edu/~daw/papers/setuid-usenix02.pdf
>     (jump straight to Section 7.1) 

Thanks for the link, I wish I had that during the realtime LSM debate,
when people were actually recommending that jackd use setuid to grant RT
scheduling ability to clients.

Lee


      reply	other threads:[~2005-06-09 15:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-08 20:27 [PATCH] capabilities not inherited Manfred Georg
2005-06-08 20:41 ` Alexander Nyberg
2005-06-08 21:26   ` Manfred Georg
2005-06-08 20:44 ` Chris Wright
2005-06-08 21:20   ` Alexander Nyberg
2005-06-08 21:33     ` Manfred Georg
2005-06-08 21:46       ` Alexander Nyberg
2005-06-08 21:54       ` Chris Wright
2005-06-08 21:59     ` Chris Wright
2005-06-08 23:49       ` Lee Revell
2005-06-09  2:59     ` David Wagner
2005-06-09 10:32       ` Alexander Nyberg
2005-06-09 14:55         ` David Wagner
2005-06-09 15:31           ` Lee Revell [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=1118331084.15527.26.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=daw-usenet@taverner.cs.berkeley.edu \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox