All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom <tom@lemuria.org>
To: David Eaves <deaves@plansys.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: Fw: [ISN] IBM earns Linux certification
Date: Fri, 8 Aug 2003 11:01:58 +0200	[thread overview]
Message-ID: <20030808090158.GC8977@lemuria.org> (raw)
In-Reply-To: <01d001c35d11$ca9deb00$6418a8c0@PSIMONT2>

On Thu, Aug 07, 2003 at 11:29:08AM -0700, David Eaves wrote:
> Yes it's true the the door got a little wider for Linux. But first of all,
> EAL2, and EAL3 are barely adequate for e-commerce in general, and not for a
> level of threat posed to military systems in time of war, by a highly

In real life, however, most e-commerce systems wouldn't even get
EAL1 if they tried.


> EAL4 is required even for relatively ordinary protection between information
> enclaves. The CC system goes up to EAL7, which requires formal proofs of
> linkage between security targets, protection profiles, and the design and
> implementation of the products in question. The outlook even for SE-linux is

EAL7 is very much a pipe dream. I don't see how any system could ever
reach it. Definitely no existing system, you'd have to start from
scratch, with EAL7 as your main target.


> that nobody will be able to access it who is not supposed to. The Windows
> product lines already have EAL4+ (what the plus means I don't know) versus

The plus usually means they also satisfy one or more requirements of
the higher level.


--
This message was distributed to subscribers of the selinux mailing 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.

  parent reply	other threads:[~2003-08-08  9:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-07 18:29 Fw: [ISN] IBM earns Linux certification David Eaves
2003-08-07 20:45 ` Florian Weimer
2003-08-08  9:01 ` Tom [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-08-07 21:19 David Eaves

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=20030808090158.GC8977@lemuria.org \
    --to=tom@lemuria.org \
    --cc=deaves@plansys.com \
    --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.