public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tracy R Reed <treed@ultraviolet.org>
To: Kevin <kevin@pheared.net>
Cc: Jason Czerak <Jason-Czerak@Jasnik.net>, linux-kernel@vger.kernel.org
Subject: Re: Suggestions for linux security patches
Date: Fri, 21 Dec 2001 03:07:06 -0800	[thread overview]
Message-ID: <20011221030706.A4518@ultraviolet.org> (raw)
In-Reply-To: <1008794926.842.6.camel@neworder> <Pine.GSO.4.40.0112200017280.1846-100000@eclipse.pheared.net>
In-Reply-To: <Pine.GSO.4.40.0112200017280.1846-100000@eclipse.pheared.net>; from kevin@pheared.net on Thu, Dec 20, 2001 at 12:19:41AM -0500

[-- Attachment #1: Type: text/plain, Size: 692 bytes --]

On Thu, Dec 20, 2001 at 12:19:41AM -0500, Kevin wrote:
> Has anyone tried the NSA linux security setup?  I've looked it over but
> haven't gone so far as to actually run it.

I have and it is very impressive. It looks much more manageable and more
flexible than LIDS. I have played with LIDS quite extensively but having
used both now I really prefer the concept of processes running in
different domains over just assigning capabilities. I'm still learning how
to configure SE Linux though. They are both rather daunting.

-- 
Tracy Reed      http://www.ultraviolet.org
If Microsoft built cars instead of software, the airbag system would say
"Are you sure?" before going off.

[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]

      reply	other threads:[~2001-12-21 10:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-19 20:48 Suggestions for linux security patches Jason Czerak
2001-12-19 21:28 ` Tomas Konir
2001-12-19 21:44 ` Jason Czerak
2001-12-19 23:50 ` Chris Wright
2001-12-20  5:19 ` Kevin
2001-12-21 11:07   ` Tracy R Reed [this message]

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=20011221030706.A4518@ultraviolet.org \
    --to=treed@ultraviolet.org \
    --cc=Jason-Czerak@Jasnik.net \
    --cc=kevin@pheared.net \
    --cc=linux-kernel@vger.kernel.org \
    /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