All of lore.kernel.org
 help / color / mirror / Atom feed
From: Crispin Cowan <crispin@wirex.com>
To: Greg KH <greg@kroah.com>
Cc: LA Walsh <law@sgi.com>,
	linux-security-module@wirex.com, linux-kernel@vger.kernel.org
Subject: Re: Security hooks, "standard linux security" & embedded use
Date: Thu, 12 Jul 2001 13:32:53 -0700	[thread overview]
Message-ID: <3B4E0975.FEB8CEA1@wirex.com> (raw)
In-Reply-To: <20010712112102.D32683@kroah.com>

Greg KH wrote:

> LA Walsh wrote:
> > Dear Linus et al.,
> >         Sorry for the 'form' letter instead of individual names, but I
> > didn't want to have to send this out separately to every kernel developer
> > I know on LKML.
> >
> >         I am asking for your input on the concept of moving the standard
> > Linux security checks into a "Linux Security Module".

For those who haven't heard, this topic is part of ongoing development of the
LSM (Linux Security Module) project.  The intent is to enhance the existing
LKM such that effective security modules can be written.  This was inspired by
comments from Linus during the SELinux presentation at the Linux 2.5 summit.

As Greg K-H said, the home page for LSM is here  http://lsm.immunix.org/   The
intent is to get a minimal set of common "hooks" into the mainline Linux 2.5
kernel such that many of the would-be security-enhancing packages for Linux
are happy.  Much of the effort involved in LSM involves working towards a
consensus of what we all (security) people can live with, such that the Linux
kernel community will accept it.

There was a "Kernel Security Extensions" BOF at USENIX last month, which
largely became a LSM BOF.  For a great summary of the current state of LSM,
check out this very nice write-up at LWN
http://lwn.net/2001/0704/security.php3  It pretty accurately captures the
state of consensus now, and the issues we're working to resolve before
LSM comes and bothers Linus with a patch.

In warming up for coming to bother y'all with a patch, we had a meeting with
Ted Ts'o at USENIX.  Ted indicated to us that, by and large, most of the
consensus represented in the LWN write-up is going in the right direction for
acceptance into the main Linux kernel.  If that is NOT true, we certainly want
to hear about it.

Please cc: linux-security-module@wirex.com on this topic.  The LSM list is
closed to non-subscribers, but I run the mailman moderation of the list, and I
will silently approve any post that is topical.

Thanks,
    Crispin

--
Crispin Cowan, Ph.D.
Chief Scientist, WireX Communications, Inc. http://wirex.com
Security Hardened Linux Distribution:       http://immunix.org
Available for purchase: http://wirex.com/Products/Immunix/purchase.html


       reply	other threads:[~2001-07-12 20:33 UTC|newest]

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

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=3B4E0975.FEB8CEA1@wirex.com \
    --to=crispin@wirex.com \
    --cc=greg@kroah.com \
    --cc=law@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@wirex.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.