From: "Paul Wolfson" <paulwolfson@attbi.com>
To: "McFadden, Ken" <ken.mcfadden@lmco.com>,
"'Russell Coker'" <russell@coker.com.au>,
"JW" <jw@centraltexasit.com>, "SE Linux" <selinux@tycho.nsa.gov>
Cc: "Haigh, Tom" <tom_haigh@securecomputing.com>,
"'Admissions Office'" <admissions@internet.edu.nf>,
"Carsten Grohmann" <carsten.grohmann@dr-baldeweg.de>,
"Paul Wolfson" <paulwolfson@attbi.com>
Subject: Outside observer comments
Date: Tue, 4 Jun 2002 21:43:16 -0500 [thread overview]
Message-ID: <007801c20c3a$bf5ee920$0200000a@wb1> (raw)
In-Reply-To: 31A81CDD9175D411815100508BE32AA60142F388@emss02m13.ems.lmco.com
Hello,
I recently added myself to the SELinux listserver because of genuine shared
concerns about securing open source computing. NSA is correct to be doing
this initiative and linux in its evolution will be better for it.
Now, from the few dozen emails that have come across my screen are any
indication, bickering is counter-productive. It resembles government
procurement at its worst. In that atmosphere I am afraid that there is
little that I will be able to contribute. My company, is relatively new,
but has principal engineers who hold or have held DoD clearance at TS and
higher and would be interested in contributing to this effort. If someone
on this list is a good POC let me know and perhaps we will be in a position
to help.
Perhaps this isn't the best forum to post such a blast as this, but its
intent at least is well meant.
Paul Wolfson, Ph.D.
Principal and President
Process and System Integration, Inc.
PO Box 118524
Carrollton, TX 75011-8524
----- Original Message -----
From: "McFadden, Ken" <ken.mcfadden@lmco.com>
To: "'Russell Coker'" <russell@coker.com.au>; "JW" <jw@centraltexasit.com>;
"SE Linux" <selinux@tycho.nsa.gov>
Cc: "Haigh, Tom" <tom_haigh@securecomputing.com>; "'Admissions Office'"
<admissions@internet.edu.nf>; "Carsten Grohmann"
<carsten.grohmann@dr-baldeweg.de>
Sent: Tuesday, June 04, 2002 5:28 PM
Subject: RE: Sorry, read this one: Re: SELinux Dumb Questions
> Once again, We are doing this for NSA and GNU NOT SECURE COMPUTING!!!!!!!
> If Tom has a problem <<snip>> treat it as GNU per NSA's web page!!!!!!!
>
--
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:[~2002-06-05 2:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 22:28 Sorry, read this one: Re: SELinux Dumb Questions McFadden, Ken
2002-06-05 1:34 ` Admissions Office
2002-06-05 3:07 ` Russell Coker
2002-06-05 3:43 ` Admissions Office
2002-06-05 2:43 ` Paul Wolfson [this message]
2002-06-05 3:14 ` Outside observer comments Russell Coker
2002-06-05 4:07 ` JW
2002-06-05 4:28 ` Russell Coker
2002-06-05 7:29 ` Tom
2003-07-04 16:51 ` SE Linux & Education Ryan Emge
2002-06-07 6:28 ` Russell Coker
2002-06-05 7:26 ` Sorry, read this one: Re: SELinux Dumb Questions Tom
-- strict thread matches above, loose matches on Subject: below --
2002-06-04 23:37 Roland.Jones
2002-06-05 5:34 ` Outside Observer Comments Paul Wolfson
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='007801c20c3a$bf5ee920$0200000a@wb1' \
--to=paulwolfson@attbi.com \
--cc=admissions@internet.edu.nf \
--cc=carsten.grohmann@dr-baldeweg.de \
--cc=jw@centraltexasit.com \
--cc=ken.mcfadden@lmco.com \
--cc=russell@coker.com.au \
--cc=selinux@tycho.nsa.gov \
--cc=tom_haigh@securecomputing.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.