[<prev] [next>] [day] [month] [year] [list]
Message-ID: <871080DEC5874D41B4E3AFC5C400611E06B476E4@UTDEVS02.campus.ad.utdallas.edu>
From: pauls at utdallas.edu (Schmehl, Paul L)
Subject: Re: [RHSA-2003:279-01] Updated OpenSSH packages fix potential vulnerability
> -----Original Message-----
> From: Matt Collins [mailto:matt@...es.com]
> Sent: Wednesday, September 17, 2003 4:21 AM
> To: kernelclue@...hmail.com
> Cc: full-disclosure@...ts.netsys.com
> Subject: Re: [Full-Disclosure] Re: [RHSA-2003:279-01] Updated
> OpenSSH packages fix potential vulnerability
>
> I tend to agree - if you want redhat patches subscribe to
> their security mailing list. If redhat find a new bug, they of course
> should post it to bugtraq, full disclosure, or their
> communications medium
> of choice.
>
Now we're back to the same silly discussion we have every time list
traffic goes up. Filter, fer cryin' out loud, and be done with it.
Utility of a list is entirely a beast of your own creation. The list is
a useful or useless as you make it, by the way that you use it.
Just think how much fun it is for someone who has to be concerned about
*numerous* systems to have to subscribe to *every* security annoucement
list for *every* vendor rather than simply getting all the messages on
one list - this one. Every coin has two sides.
The thing that surprises me about *this* argument is that the very
people who ought to be the most competent at appropriate filtering are
the very ones complaining about "list flood" from "Linux" vendors (never
mind the fact that this one affects damn near every platform in the
world, including Mac OS X and Windows.)
Paul Schmehl (pauls@...allas.edu)
Adjunct Information Security Officer
The University of Texas at Dallas
AVIEN Founding Member
http://www.utdallas.edu/~pauls/
Powered by blists - more mailing lists