mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "'Christoph Hellwig'" <hch@infradead.org>
To: Crispin Cowan <crispin@wirex.com>
Cc: torvalds@transmeta.com, LA Walsh <law@tlinx.org>,
	linux-security-module@wirex.com, linux-kernel@vger.kernel.org
Subject: Re: [BK PATCH] LSM changes for 2.5.59
Date: Mon, 10 Feb 2003 08:39:17 +0000	[thread overview]
Message-ID: <20030210083917.A16926@infradead.org> (raw)
In-Reply-To: <3E4763C8.5090100@wirex.com>; from crispin@wirex.com on Mon, Feb 10, 2003 at 12:33:12AM -0800

On Mon, Feb 10, 2003 at 12:33:12AM -0800, Crispin Cowan wrote:
> Am I parsing this correctly, that we actually agree on something? :-) 
> I.e. that the idea of moving all the security logic to a module has merit.

Yes.  If we want so support security models more complicated than plain
UNIX DAC (an especially more than one of those) there's no way around
moving all access control out of the core kernel.

> Naturally, I disagree that we should remove the current LSM. The current 
> version was designed to be what Linus asked for. Many LSM people like 
> the idea of moving all the security logic out to a module, as it makes 
> the interface much cleaner. But it is also waaay beyond the scope of 
> what Linus asked for. It involves re-factoring so much code that we did 
> not think it could be done correctly on the first try, never mind trying 
> to get many code maintainers to accept much larger patches.

Well, usually adding changes to the core kernel in a proper way needs
major refactoring of code - the approach of adding a small, "non-invasive"
hack here and there leads to the typical mess seen in commercial operating
systems, and in Linux we've avoided that mostly so far.

As far keeping the current LSM hooks:  I'm very unhappy with the design
of the, that's one point.  The other point I'm extremly unhappy with
adding them without adding it's users.  I'll shut up and be quite until
2.7 opens if you get a meaningfull LSM module merged that actually uses
those hooks.  If you don't get one in by 2.6-test I will send patches
to remove those unused hooks.


  reply	other threads:[~2003-02-10  8:29 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-06 15:02 Stephen D. Smalley
2003-02-06 15:18 ` Christoph Hellwig
2003-02-06 17:16   ` David Wagner
2003-02-06 17:45     ` Christoph Hellwig
2003-02-06 17:51   ` Alan Cox
2003-02-08  2:20   ` jmjones
2003-02-09 20:06     ` Christoph Hellwig
2003-02-10  1:39       ` Crispin Cowan
2003-02-10  3:02         ` LA Walsh
2003-02-10  3:40           ` Crispin Cowan
2003-02-10  7:34             ` LA Walsh
2003-02-10  8:11               ` Chris Wright
2003-02-10  8:21             ` 'Christoph Hellwig'
2003-02-10  8:33               ` Crispin Cowan
2003-02-10  8:39                 ` 'Christoph Hellwig' [this message]
2003-02-10 13:31             ` Alan Cox
2003-02-10 17:29             ` Casey Schaufler
2003-02-12  8:12               ` side issues of baloney with that ham...(was LSM changes for 2.5.59) LA Walsh
2003-02-10 20:51             ` [BK PATCH] LSM changes for 2.5.59 LA Walsh
2003-02-10 21:36               ` David Wagner
2003-02-10 22:14             ` Bill Davidsen
2003-02-11  1:35               ` Dave Jones
2003-02-11 13:59                 ` the modules problems Roman Zippel
2003-02-11 19:44                 ` [BK PATCH] LSM changes for 2.5.59 Bill Davidsen
2003-02-10  4:06           ` J Sloan
2003-02-10  5:59       ` David Wagner
2003-02-10  7:31         ` Christoph Hellwig
2003-02-08  4:13   ` Miles Bader
  -- strict thread matches above, loose matches on Subject: below --
2003-02-13  4:08 Mika Kukkonen
2003-02-12 16:58 Makan Pourzandi (LMC)
2003-02-12 18:45 ` 'Christoph Hellwig'
2003-02-12 19:11 ` magniett
2003-02-12 18:38   ` 'Christoph Hellwig'
2003-02-12 22:22     ` Crispin Cowan
2003-02-12 15:37 Pete Loscocco
     [not found] <b28k4f$hp4$1@abraham.cs.berkeley.edu>
2003-02-12  8:27 ` LA Walsh
2003-02-10 19:57 Stephen D. Smalley
2003-02-10 22:38 ` LA Walsh
2003-02-10 16:55 Stephen D. Smalley
2003-02-11  8:05 ` Christoph Hellwig
2003-02-13 11:08   ` Chris Wright
2003-02-05 16:59 Stephen D. Smalley
2003-02-05 16:47 Stephen D. Smalley
2003-02-05 16:49 ` Christoph Hellwig
2003-02-05 22:07   ` Greg KH
2003-02-05 22:30     ` Christoph Hellwig
2003-02-05 22:39       ` Russell Coker
2003-02-05 22:41         ` Christoph Hellwig
2003-02-05 15:00 Stephen D. Smalley
2003-02-05 15:34 ` Christoph Hellwig
2003-02-05 16:26 ` Mark Hahn
2003-02-05 13:45 Stephen D. Smalley
2003-02-05 14:13 ` Christoph Hellwig
2003-02-05  4:15 Greg KH
2003-02-05  8:47 ` Christoph Hellwig

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=20030210083917.A16926@infradead.org \
    --to=hch@infradead.org \
    --cc=crispin@wirex.com \
    --cc=law@tlinx.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@wirex.com \
    --cc=torvalds@transmeta.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®