All of lore.kernel.org
 help / color / mirror / Atom feed
From: Casey Schaufler <casey@sgi.com>
To: Nelson Rush <palisade@users.sourceforge.net>
Cc: SELinux List <selinux@tycho.nsa.gov>
Subject: Re: Ros: Re: enhanced security for Linux, from Stephen Smalley
Date: Tue, 16 Jan 2001 09:16:34 -0800	[thread overview]
Message-ID: <3A6481F2.227294F8@sgi.com> (raw)
In-Reply-To: NOEOKAOLIKKJHIJHDNJGCEGMCAAA.palisade@users.sourceforge.net

Nelson Rush wrote:
> 
> >> The confidentiality lattice just wasn't designed with these things in
> >> mind.
> >
> >The confidentiality lattice is to system security what
> >Froot Loops are to a nutritious breakfast.
> 
> Fruit loops has more vitamins than Cocoa Puffs or Wheaties or HoneyComb
> cereal, less calories than Raisin Nut Bran or Waffle Crisps, no cholesterol,
> and less sodium than Cap'n Crunch Peanut Butter Crunch.

It doesn't matter which it is, so long as the kids eat
(the good part of) breakfast before they go off to school.
Similarly, I can help an installation meet their security
needs by providing the security feature, in this case the
confidentiality lattice, which they've screamed and yelled
and threatened to hold their breath until the turn blue
if they can't have it.

Sorry for the obscure comparison. I do that sometimes.

-- 

Casey Schaufler				Manager, Trust Technology, SGI
casey@sgi.com				voice: 650.933.1634
casey_p@pager.sgi.com			Pager: 888.220.0607

--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  reply	other threads:[~2001-01-16 17:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-10 15:58 Ros: Re: enhanced security for Linux, from Stephen Smalley Badger, Lee
2001-01-10 17:52 ` Casey Schaufler
2001-01-13  1:18   ` Nelson Rush
2001-01-16 17:16     ` Casey Schaufler [this message]
2001-01-16 19:51       ` Nelson Rush

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=3A6481F2.227294F8@sgi.com \
    --to=casey@sgi.com \
    --cc=palisade@users.sourceforge.net \
    --cc=selinux@tycho.nsa.gov \
    /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.