full-disclosure - The MSBlast Conspiracy Theory

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

Message-ID: <00fd01c36351$4074c0c0$186310ac@beast24>
From: mike at blakogre.com (Mike Vasquez)
Subject: The MSBlast Conspiracy Theory

Ya, but I think it's just as likely someone who had very little coding
knowledge, but wanted to be the first to get a worm out.  If they subscribe
to the list, they're probably laughing at the conspiracy theories being put
forth.

Mike, AEIOU, and sometimes Y

----- Original Message ----- 
From: "Jeremiah Cornelius" <jeremiah@....net>
To: <full-disclosure@...ts.netsys.com>
Sent: Friday, August 15, 2003 8:54 AM
Subject: [fd] Re: [Full-Disclosure] The MSBlast Conspiracy Theory


> On Thursday 14 August 2003 09:55 pm, Weezer Hutchins wrote:
> > This was such a benign implementation of the serious DCOM security risk,
> > that my conspiracy theory is ... Microsoft had this worm released on
> > purpose in an attempt to get everyone to patch their machines before a
> > really threatening version was released.
> >
>
> Well,
> MSBlast was kludged together poorly enough. That in itself is another
> indicator supporting your theory.
>
> -- 
> Jeremiah Cornelius, CISSP, CCNA, MCSE
> Information Security Technology
> email: jcorneli@...mail.com - mobile: 415.235.7689