From: Chris Wright <chrisw@osdl.org>
To: Andy Lutomirski <luto@myrealbox.com>
Cc: Chris Wright <chrisw@osdl.org>, Andrew Morton <akpm@osdl.org>,
Christoph Hellwig <hch@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.6-mm2
Date: Thu, 13 May 2004 18:01:24 -0700 [thread overview]
Message-ID: <20040513180124.C22989@build.pdx.osdl.net> (raw)
In-Reply-To: <40A417EC.7010604@myrealbox.com>; from luto@myrealbox.com on Thu, May 13, 2004 at 05:50:52PM -0700
* Andy Lutomirski (luto@myrealbox.com) wrote:
> Chris Wright wrote:
> > What about something that's just simple and generic? This is similar to
> > Andrea's disable_cap_mlock patch and the disabling capabilities patch
> > that wli produced back in that thread. It would remove the hack, and
> > buy us some time to find better solutions. Downside of course (as all
> > of these have) is reduced security value.
>
> I actually like the magic group better. This one means that _anyone_
> can DoS the system. Why not just give Oracle its own LSM if this is
> what you want to do (that way the nastiness is completely isolated)?
Magic group has better safety property, but it evolved from
disable_cap_mlock which for CAP_IPC_LOCK has the identical property to
this patch. Agreed it's safer w/out, but the magic group is so special
purpose that it feels like a hack. This patch is more contained and
IMO is just a hold over until we have something that really works.
> <shameless_plug> My patch (posted a couple hours ago) solves this one
> cleanly </shameless_plug>
I'll comment on that separately ;-)
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2004-05-14 1:01 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.h4eq5gb.nj6q31@ifi.uio.no>
[not found] ` <fa.gi5j8pu.92umbq@ifi.uio.no>
2004-05-14 0:50 ` 2.6.6-mm2 Andy Lutomirski
2004-05-14 1:01 ` Chris Wright [this message]
2004-05-14 18:51 2.6.6-mm2 Jan Killius
-- strict thread matches above, loose matches on Subject: below --
2004-05-13 19:14 2.6.6-mm2 Martin J. Bligh
2004-05-13 19:21 ` 2.6.6-mm2 Andrew Morton
2004-05-13 20:47 ` 2.6.6-mm2 Adrian Bunk
2004-05-13 15:44 2.6.6-mm2 David Brownell
2004-05-13 12:39 2.6.6-mm2 Oleg Nesterov
2004-05-13 18:28 ` 2.6.6-mm2 Andrew Morton
2004-05-13 23:51 ` 2.6.6-mm2 Nick Piggin
2004-05-13 10:27 2.6.6-mm2 Andrew Morton
2004-05-13 10:45 ` 2.6.6-mm2 Christoph Hellwig
2004-05-13 10:51 ` 2.6.6-mm2 Andrew Morton
2004-05-13 11:12 ` 2.6.6-mm2 Christoph Hellwig
2004-05-13 11:25 ` 2.6.6-mm2 Andrew Morton
2004-05-13 13:18 ` 2.6.6-mm2 Adrian Bunk
2004-05-13 13:39 ` 2.6.6-mm2 Chris Mason
2004-05-13 14:09 ` 2.6.6-mm2 Adrian Bunk
2004-05-17 20:52 ` 2.6.6-mm2 Bill Davidsen
2004-05-14 7:30 ` 2.6.6-mm2 Ian Kent
2004-05-13 14:15 ` 2.6.6-mm2 Adrian Bunk
2004-05-13 19:18 ` 2.6.6-mm2 Chris Wright
2004-05-13 19:29 ` 2.6.6-mm2 Andrew Morton
2004-05-13 19:35 ` 2.6.6-mm2 Chris Wright
2004-05-13 19:38 ` 2.6.6-mm2 Andrew Morton
2004-05-13 19:42 ` 2.6.6-mm2 Chris Wright
2004-05-14 19:14 ` 2.6.6-mm2 Andrea Arcangeli
2004-05-14 20:58 ` 2.6.6-mm2 Chris Wright
2004-05-15 2:43 ` 2.6.6-mm2 Andrea Arcangeli
2004-05-15 7:43 ` 2.6.6-mm2 Hugh Dickins
2004-05-14 19:06 ` 2.6.6-mm2 Kevin O'Connor
2004-05-14 19:36 ` 2.6.6-mm2 Chris Wright
2004-05-14 19:42 ` 2.6.6-mm2 Kevin O'Connor
2004-05-13 12:14 ` 2.6.6-mm2 Matt H.
2004-05-13 18:24 ` 2.6.6-mm2 Andrew Morton
2004-05-13 22:40 ` 2.6.6-mm2 Greg KH
2004-05-13 13:42 ` 2.6.6-mm2 Paolo Ornati
2004-05-13 15:07 ` 2.6.6-mm2 Lorenzo Allegrucci
2004-05-13 18:55 ` 2.6.6-mm2 Andrew Morton
2004-05-13 19:41 ` 2.6.6-mm2 Lorenzo Allegrucci
2004-05-14 17:48 ` 2.6.6-mm2 R. J. Wysocki
2004-05-14 17:47 ` 2.6.6-mm2 Christoph Hellwig
2004-05-14 21:20 ` 2.6.6-mm2 R. J. Wysocki
2004-05-14 23:56 ` 2.6.6-mm2 Joseph Fannin
2004-05-14 23:58 ` 2.6.6-mm2 Chris Wright
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=20040513180124.C22989@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@myrealbox.com \
/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
all inboxes | Powered by JetHome®