From: "Michael H. Warfield" <mhw@wittsend.com>
To: Gerhard Mack <gmack@innerfire.net>
Cc: Bob Lorenzini <hwm@newportharbornet.com>, linux-kernel@vger.kernel.org
Subject: Re: Linux Worm (fwd)
Date: Fri, 23 Mar 2001 15:30:59 -0500 [thread overview]
Message-ID: <20010323153059.A9319@alcove.wittsend.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0103230947250.14872-100000@newportharbornet.com> <Pine.LNX.4.10.10103231028250.9403-100000@innerfire.net>
In-Reply-To: <Pine.LNX.4.10.10103231028250.9403-100000@innerfire.net>; from gmack@innerfire.net on Fri, Mar 23, 2001 at 10:31:49AM -0800
On Fri, Mar 23, 2001 at 10:31:49AM -0800, Gerhard Mack wrote:
> On Fri, 23 Mar 2001, Bob Lorenzini wrote:
> > I'm annoyed when persons post virus alerts to unrelated lists but this
> > is a serious threat. If your offended flame away.
> This should be a wake up call... distributions need to stop using product
> with consistently bad security records.
Bullshit.
This is a wake up call that admins need to keep installations up
to date. When a security hole is found, I DON'T CARE if it's in a package
with a good security record or a poor security record. It has to be
fixed and you can't put it off. Certainly not in the current climate
with script driven worms like Ramen and 1i0n.
Having a poor security record is a warning to the developers that
it's time to clean up their act and do better. Sendmail use to be the
bug of the month club. Hell! It use to be the bug of the week club. Last
couple of years, it's been pretty solid. If you only went on security
track record, we would all be using MMDF, which is still arguibly the most
secure mail transport around. MMDF has had what? One advisory in something
like 15 years of deployment? It was the default MTA in SCO Unix for
years and was mandated at military installations for a long time... Still,
when that one advisory comes out, you better update or you are toast.
You don't solely rely on packages that have "good security records"
never getting broken and then become complacent. Sites that do that are
what we call "Warez" sites. :-/
> Gerhard
> --
> Gerhard Mack
> gmack@innerfire.net
> <>< As a computer I find your faith in technology amusing.
Mike
--
Michael H. Warfield | (770) 985-6132 | mhw@WittsEnd.com
(The Mad Wizard) | (678) 463-0932 | http://www.wittsend.com/mhw/
NIC whois: MHW9 | An optimist believes we live in the best of all
PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of it!
next prev parent reply other threads:[~2001-03-23 20:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-23 17:49 Bob Lorenzini
2001-03-23 18:30 ` [OT] " Jonathan Morton
2001-03-23 18:31 ` Gerhard Mack
2001-03-23 18:51 ` [OT] " Doug McNaught
2001-03-23 19:39 ` Michael Bacarella
2001-03-23 22:19 ` Herbert Xu
2001-03-24 0:39 ` Edward S. Marshall
2001-03-24 17:11 ` Jesse Pollard
2001-03-24 17:50 ` Edward S. Marshall
2001-03-24 19:02 ` Sandy Harris
2001-03-23 18:56 ` Dax Kelson
2001-03-23 19:08 ` Jeremy Jackson
2001-03-23 20:30 ` Michael H. Warfield [this message]
2001-03-26 15:07 ` Richard B. Johnson
2001-03-26 15:24 ` Gregory Maxwell
2001-03-26 16:02 ` Bob_Tracy
2001-03-26 16:11 ` offtopic " John Jasen
2001-03-26 18:53 ` Ben Ford
2001-03-27 1:14 ` Drew Bertola
2001-03-26 15:40 ` David Weinehall
2001-03-26 16:51 ` Bob Lorenzini
2001-03-26 16:51 ` Henning P. Schmiedehausen
2001-03-26 18:32 ` Stephen Satchell
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=20010323153059.A9319@alcove.wittsend.com \
--to=mhw@wittsend.com \
--cc=gmack@innerfire.net \
--cc=hwm@newportharbornet.com \
--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
all inboxes | Powered by JetHome®