From: Pat Gilliland <gilliland@sympatico.ca>
To: oclug <oclug@lists.oclug.on.ca>
Cc: linux-8086@vger.kernel.org
Subject: Point to ponder
Date: Wed, 04 Dec 2002 13:44:58 -0500 [thread overview]
Message-ID: <3DEE4D2A.BBE0ECDE@sympatico.ca> (raw)
Interesting thought posted on the ELKS list (linux-8086@vger.kernel.org)
Please note the cc before replying
<snip>
BTW, does the use of Linux for military purposes make the open source
development community legitimate targets? I indeed do think so.
Commercial
sw licences specifically prohibite critical applications (nuclear
powerplants, life support and the like) which conveniently covers
military
use, so they are not agreeing to that. Linus should better look out for
the bearded man with thin face...
Sincerely: Tamas Feher
<snip>
My take would be that the Linux/Open Source community has little to
worry about from (to be polite) non-western aligned groups. Opens
Source puts powerful non-proprietary tools in the hands of anyone with a
modem and time. Access to source ensures western/hostile intelligence
agencies have not put any backdoors in. The global development community
ensures that a user is not dependant on single source software supplier
bowing to pressure from government to remove support from "undesirable"
groups.
I can see Microsoft being encouraged by Bush to NOT allow (strictly for
example) Hezbollah to register their copies of XP. No-one can stop them
from using Linux. Do the very attributes that make Linux and opensource
so powerful and flexible present a security threat to certain parties?
reply other threads:[~2002-12-04 18:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3DEE4D2A.BBE0ECDE@sympatico.ca \
--to=gilliland@sympatico.ca \
--cc=linux-8086@vger.kernel.org \
--cc=oclug@lists.oclug.on.ca \
/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