full-disclosure - Re: RE: Patching networks redux (fwd)

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

Message-Id: <200608230347.k7N3lTM2029170@turing-police.cc.vt.edu>
Date: Tue, 22 Aug 2006 23:47:29 -0400
From: Valdis.Kletnieks@...edu
To: jack mcwilliams <jaxxxson2@...plepc.com>
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: RE: Patching networks redux (fwd)

On Tue, 22 Aug 2006 14:51:45 CDT, jack mcwilliams said:

> do you have a patch or suggestion to cure this kind of error?????

Well, either you sent it, or a virus forged your name on it.  If you did it,
don't do it again.  If a virus did it, complain to the place that sent you
the error message and tell them not to send messages to unverified source
addresses when the A/V tool *knows* the purported source of the virus is
forged.

> ------=_NextPart_000_0021_01C6C5E4.9523BB00
> Content-Type: application/octet-stream;
> name="ATT00083.lnk"

I'm not a Windows guy, but aren't *.lnk files considered evil virus-spawn? :)

Content of type "application/pgp-signature" skipped

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/