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>] [thread-next>] [day] [month] [year] [list]

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

> -----Original Message-----
> From: morning_wood [mailto:se_cur_ity@...mail.com] 
> Sent: Friday, August 29, 2003 11:19 AM
> To: Charles Ballowe; full-disclosure@...ts.netsys.com
> Subject: Re: [Full-Disclosure] Authorities eye MSBlaster suspect
> 
> 
> if the worm was active in anticipation of a patch that 
> intoduced a new exploit vector and it took advantage of that, 
> is'nt the vendor ( microsoft ) to blame then? As well there 
> was plenty of advanced warning on this exploit long before 
> msblast was an issue. It seems to me that it is each admins 
> responsiblity, if they were affected ( infected ) not the 
> coder. if this were the case the LastStage(of)Delerium would 
> be the blamed party for developing and releasing the exploit, 
> but alas.. they are not of USA orgin. SUE LITIGATE BLAME PROCECUTE
> 
So you would blame murder victims for being in the wrong place?  Or rape
victims for wearing the wrong clothing?

Nice set of ethics there.

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