mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Anton Altaparmakov <aia21@cam.ac.uk>
To: Greg KH <greg@kroah.com>
Cc: Hans Reiser <reiser@namesys.com>, LA Walsh <law@sgi.com>,
	reiserfs-dev@namesys.com, linux-kernel@vger.kernel.org,
	reiserfs-list@namesys.com
Subject: Re: Security hooks, "standard linux security" & embedded use
Date: Thu, 12 Jul 2001 20:04:05 +0100	[thread overview]
Message-ID: <5.1.0.14.2.20010712195903.00a83d10@pop.cus.cam.ac.uk> (raw)
In-Reply-To: <20010712114729.B735@kroah.com>
In-Reply-To: <5.1.0.14.2.20010712192608.0365e588@pop.cus.cam.ac.uk> <3B49F602.DB39B3A@sgi.com> <3B4DDFD8.27C1C3D9@namesys.com> <5.1.0.14.2.20010712192608.0365e588@pop.cus.cam.ac.uk>

At 19:47 12/07/2001, Greg KH wrote:
>On Thu, Jul 12, 2001 at 07:37:36PM +0100, Anton Altaparmakov wrote:
> >
> > This seems very good in view of implementing ACL support for NTFS, too. -
> > We have all the NTFS layout knowledge to do it now. We just lack the
> > kernel/user space infrastructure.
> >
> > When designing this modular security infrastructure it would be useful if
> > it is made generic enough to allow callbacks into user space for 
> permission
> > checking.
>
>The current model lets you do whatever you want in your kernel module.
>It imposes no policy, that's up to you.

Ok, that's fair enough. A wrapper module could always be written that then 
in turn invokes user space. That's good enough for me although it makes for 
additional overhead but I guess that is not too bad.

>All the better to keep userspace callbacks for security out of my
>kernels, for that way is ripe for problems (for specific examples why,
>see the linux-security-module mailing list archives.)

Oh, sure. There are problems. I don't deny that. But I am not too sure that 
those problems outweigh the problems created by putting in huge amounts of 
code into the kernel which could live outside it just as well. - IMHO the 
kernel should be as small as possible rather than contain everything under 
the sun just because it's easier to do that way...

Best regards,

Anton


-- 
   "Nothing succeeds like success." - Alexandre Dumas
-- 
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Linux NTFS Maintainer / WWW: http://linux-ntfs.sf.net/
ICQ: 8561279 / WWW: http://www-stu.christs.cam.ac.uk/~aia21/


  parent reply	other threads:[~2001-07-12 19:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3B49F602.DB39B3A@sgi.com>
2001-07-12 17:35 ` Hans Reiser
2001-07-12 18:25   ` Greg KH
2001-07-12 19:04   ` Anton Altaparmakov [this message]
2001-07-12 18:37 ` Anton Altaparmakov
2001-07-12 18:47   ` Greg KH
2001-07-12 19:16     ` LA Walsh
     [not found] <20010712112102.D32683@kroah.com>
2001-07-12 20:32 ` Crispin Cowan

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=5.1.0.14.2.20010712195903.00a83d10@pop.cus.cam.ac.uk \
    --to=aia21@cam.ac.uk \
    --cc=greg@kroah.com \
    --cc=law@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiser@namesys.com \
    --cc=reiserfs-dev@namesys.com \
    --cc=reiserfs-list@namesys.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®