From: Casey Schaufler <casey@sgi.com>
To: Pedro Rosa <Pedro.Rosa@ksu.ru>
Cc: Chris <smithchr@mindspring.com>,
securedistros@nl.linux.org, selinux@tycho.nsa.gov
Subject: Re: Is this mail list dead?
Date: Tue, 13 Mar 2001 11:57:57 -0800 [thread overview]
Message-ID: <3AAE7BC5.50DA0CB@sgi.com> (raw)
In-Reply-To: 3AAE0C68.1030404@ksu.ru
Pedro Rosa wrote:
> I would say that securing Linux in a distro structure would be the same
> as forcing C2 to every Windows install.... Yeah try to use such an
> install...
Every commercial OS today has a C2 option. The lack
of a C2 version of Linux has been a serious inhibitor
to adoption in the marketplace. I would guess you're
refering to the first NT evaluation, which supported
no networking and no removable media. Building a C2
(CAPP in Common Criteria jargon) Linux distribution
is easier than getting corporate marketing types to
see the value. Say, I bet I know what You do!
--
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.
next prev parent reply other threads:[~2001-03-13 19:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.32.0103121443130.16938-100000@arwin.microunity.com>
[not found] ` <3AAD5908.73A44E4C@wirex.com>
2001-03-12 23:40 ` Is this mail list dead? Tracy R Reed
2001-03-13 4:29 ` Chris
2001-03-13 12:02 ` Pedro Rosa
2001-03-13 19:57 ` Casey Schaufler [this message]
2001-03-14 11:35 ` Pedro Rosa
[not found] ` <3AAEB0F5.57BBA301@gmx.de>
[not found] ` <20010313161336.E4500@ultraviolet.org>
2001-03-14 22:38 ` securedistros mailing list subscription info [was: Re: Is this mail list dead?] Martin Stricker
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=3AAE7BC5.50DA0CB@sgi.com \
--to=casey@sgi.com \
--cc=Pedro.Rosa@ksu.ru \
--cc=securedistros@nl.linux.org \
--cc=selinux@tycho.nsa.gov \
--cc=smithchr@mindspring.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.