From: Scott Robert Ladd <coyote@coyotegulch.com>
To: Andrew Walrond <andrew@walrond.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BK2CVS problem
Date: Thu, 06 Nov 2003 08:27:02 -0500 [thread overview]
Message-ID: <3FAA4C26.9080900@coyotegulch.com> (raw)
In-Reply-To: <200311061141.00595.andrew@walrond.org>
Andrew Walrond wrote:
> Somebody getting access to and inserting exploits directly into the linux
> source is not something we should take lightly. Whilst we understand the
> limits of the problem, the fact that it happened at all could get /.'d out of
> all proportion and be used to seriously undermine linux's reputation
Well, it's hit /. and OSNews already this morning.
Mainstream media is now aware of Linux; for better or worse, someday, an
issue like this is going to leak beyond Slashdot onto the pages of the
Wall Street Journal and ZDNet. Maybe not this time -- but eventually.
Open development is the ultimate in honesty -- and honesty leaves us
vulnerable to being bitten by the ignorati and anti-freedom forces.
--
Scott Robert Ladd
Coyote Gulch Productions (http://www.coyotegulch.com)
Software Invention for High-Performance Computing
next prev parent reply other threads:[~2003-11-06 13:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-05 20:45 BK2CVS problem Larry McVoy
2003-11-05 20:58 ` Matthew Dharm
2003-11-05 22:23 ` Larry McVoy
2003-11-05 22:33 ` Zwane Mwaikambo
2003-11-05 22:51 ` Andries Brouwer
2003-11-06 7:07 ` Brian McGroarty
2003-11-06 11:41 ` Andrew Walrond
2003-11-06 12:02 ` nosp
2003-11-06 12:02 ` Xavier Bestel
2003-11-06 13:27 ` Scott Robert Ladd [this message]
2003-11-06 13:59 ` Richard B. Johnson
-- strict thread matches above, loose matches on Subject: below --
2003-11-05 22:48 Chad Kitching
2003-11-05 22:53 ` Zwane Mwaikambo
2003-11-05 23:03 ` Larry McVoy
2003-11-06 0:52 ` Tomas Szepe
2003-11-06 1:57 ` Andreas Dilger
2003-11-06 2:20 ` Linus Torvalds
2003-11-06 3:01 ` Larry McVoy
2003-11-06 10:40 ` Matthias Andree
2003-11-06 4:09 ` Scott Robert Ladd
2003-11-06 10:06 ` bert hubert
2003-11-06 13:22 ` Theodore Ts'o
2003-11-06 14:43 ` Rik van Riel
2003-11-06 15:56 ` Linus Torvalds
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=3FAA4C26.9080900@coyotegulch.com \
--to=coyote@coyotegulch.com \
--cc=andrew@walrond.org \
--cc=linux-kernel@vger.kernel.org \
/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