The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Hans Reiser <reiser@namesys.com>
Cc: LA Walsh <law@sgi.com>,
	reiserfs-dev@namesys.com,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"reiserfs-list@namesys.com" <reiserfs-list@namesys.com>
Subject: Re: Security hooks, "standard linux security" & embedded use
Date: Thu, 12 Jul 2001 11:25:04 -0700	[thread overview]
Message-ID: <20010712112504.E32683@kroah.com> (raw)
In-Reply-To: <3B49F602.DB39B3A@sgi.com> <3B4DDFD8.27C1C3D9@namesys.com>
In-Reply-To: <3B4DDFD8.27C1C3D9@namesys.com>; from reiser@namesys.com on Thu, Jul 12, 2001 at 09:35:20PM +0400

On Thu, Jul 12, 2001 at 09:35:20PM +0400, Hans Reiser wrote:
> Hi Linda,
> 
> This seems very much in line with what Reiser4 is doing for DARPA, and what SE Linux is doing for
> the NSA.  Or at least what Linus told the SE Linux folks he would like them to write.:-)
> 
> I am quite supportive of what you advocate generally, and I look forward to cooperating with you in
> the details.

The details can be currently found in the most recent patch against
2.4.6 at:
	http://lsm.immunix.org/patches/lsm-2001_07_06-2.4.6.patch.gz

There's a bit more information available, including the latest version
of the patch at all times, available as a bitkeeper repository at:
	http://lsm.immunix.org/

thanks,

greg k-h

  reply	other threads:[~2001-07-12 18:28 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 ` Security hooks, "standard linux security" & embedded use Hans Reiser
2001-07-12 18:25   ` Greg KH [this message]
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
     [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=20010712112504.E32683@kroah.com \
    --to=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