full-disclosure - MS Blaster author / morning

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: <200308301337.h7UDbd46082208@mailserver2.hushmail.com>
From: darren at hushmail.com (darren@...hmail.com)
Subject: MS Blaster author / morning_wood misinformed

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Donald,

Interesting (child-like) thoughts, but in reality, this society we live
in has laws.

If a person leaves the door to their home unlocked one evening (consciously
or mistakenly) and someone chooses to go inside and ransacks the place.
Sure the homeowner probably should have locked the door, but doing so
didn't give the attacker just cause to go inside and cause the person
grief.

It's still a crime. And if caught, the result will still be the same
whether you're in the USA, Canada, Germany or China...

Do not pass go. Do not collect $200. Go directly to jail (or at least
pay some fines).

Darren

From: "morning_wood" <se_cur_ity@...mail.com>
To: "Charles Ballowe" <hangman-fulldisclosure@...elballs.org>,
   <full-disclosure@...ts.netsys.com>
Subject: Re: [Full-Disclosure] Authorities eye MSBlaster suspect
Date: Fri, 29 Aug 2003 09:18:48 -0700

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

as long as the general public remains uneducated ( and many Fortune500
admins) we will continue to see this type of action against coders for
blame, not the people actualy responsible for allowing thier infrastructure
to become targets in the first place. im sure this ignorance is a byproduct
of the weak mind of most Americans as they are in a constant state to
blame other for thier own problems, this can be seen everywhere in todays
American society... commonly refered as to the "poor me" syndrome.. Q.
why did you murder the victim? A. my father never told me he loved me
( real answer - you pulled the triger )

Q. why was my network compromised?
A. because of someone else
( real answer - you suck at internet )

muh 2 bytes,
morning_wood
-----BEGIN PGP SIGNATURE-----
Note: This signature can be verified at https://www.hushtools.com/verify
Version: Hush 2.3

wkYEARECAAYFAj9QqKIACgkQVkUxEVe6w3tiUACdE6EKxDx9XneySVWt9tXT3nzOp2MA
nR8r2bPtQ9ZpsW4NbDsJs4MKM7w5
=YOHD
-----END PGP SIGNATURE-----