From: Andi Kleen <ak@muc.de>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] disallow modular capabilities
Date: Sun, 02 Jan 2005 21:47:41 +0100 [thread overview]
Message-ID: <m1is6fy2vm.fsf@muc.de> (raw)
In-Reply-To: <20050102203005.GA9491@lst.de> (Christoph Hellwig's message of "Sun, 2 Jan 2005 21:30:05 +0100")
Christoph Hellwig <hch@lst.de> writes:
> On Sun, Jan 02, 2005 at 09:28:00PM +0100, Andi Kleen wrote:
>> Christoph Hellwig <hch@lst.de> writes:
>>
>> > There's been a bugtraq report about a root exploit with modular
>> > capabilities LSM support out for more than a week.
>>
>> It was a root exploit only triggerable by root. Not exactly
>> what I would call a real problem.
>
> At least Debian currently inserts the capabilities module on boot.
That is fine as long as they control all code executed before
that module loading. And if they do not it is their own fault
and they have to fix that in user space or compile the capability in.
Unix policy is to not stop root from doing stupid things because
that would also stop him from doing clever things.
-Anddi
next prev parent reply other threads:[~2005-01-02 20:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-02 20:00 [PATCH] disallow modular capabilities Christoph Hellwig
2005-01-02 20:01 ` Christoph Hellwig
2005-01-02 20:28 ` Andi Kleen
2005-01-02 20:30 ` Christoph Hellwig
2005-01-02 20:47 ` Andi Kleen [this message]
2005-01-02 22:36 ` David Meybohm
2005-01-02 23:30 ` Andi Kleen
2005-01-03 0:21 ` David Meybohm
2005-01-03 0:32 ` Andi Kleen
2005-01-03 14:38 ` Florian Weimer
2005-01-03 15:52 ` Alan Cox
2005-01-04 20:24 ` Lee Revell
2005-01-04 21:05 ` Linus Torvalds
2005-01-04 21:08 ` Christoph Hellwig
2005-01-04 21:31 ` Chris Wright
2005-01-04 21:09 ` Lee Revell
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=m1is6fy2vm.fsf@muc.de \
--to=ak@muc.de \
--cc=hch@lst.de \
--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