full-disclosure - Authorities eye MSBlaster suspect

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <871080DEC5874D41B4E3AFC5C400611E03F60955@UTDEVS02.campus.ad.utdallas.edu>
From: pauls at utdallas.edu (Schmehl, Paul L)
Subject: Authorities eye MSBlaster suspect

> -----Original Message-----
> From: Ben Nelson [mailto:lists@...om600.org] 
> Sent: Friday, August 29, 2003 11:57 AM
> To: morning_wood 
> Cc: full-disclosure@...ts.netsys.com
> Subject: Re: [Full-Disclosure] Authorities eye MSBlaster suspect
> 
> 
> You need to keep in mind that affected != infected.  Many of 
> us admins who don't even administrate a single windows box 
> were affected by amount of bandwidth consumed by people who 
> were infected.  This thing effectively created a denial of 
> service on many networks and any host trying to use that 
> network (be it an infected windows box or one of my hundreds of unix
> boxes) was, at the very least, significantly slowed down.

Sobig did that as well.  Even without a single infection on your
network, the support people were overwhelmed with phone calls and
emails, some mail servers collapsed under the load, technical staff
consumed time looking for workarounds and stopgap measures to keep the
stupid bounce and virus warning messages out.  The cost is enormous,
even without being infected.  And it affects every single user, whether
they were using Windows, *nix or Mac.

Paul Schmehl (pauls@...allas.edu)
Adjunct Information Security Officer
The University of Texas at Dallas
AVIEN Founding Member
http://www.utdallas.edu/~pauls/