full-disclosure - McAfee VirusScan vs Metasploit Framework v2.x

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: <BAY19-DAV4A60B115FC4049FBB762CD9440@phx.gbl>
Date: Sat Dec 10 00:58:20 2005
From: se_cur_ity at hotmail.com (Morning Wood)
Subject: McAfee VirusScan vs Metasploit Framework v2.x

// look, no top post !!!

> Looks like some overzealous idiot at McAfee added "Trojan" signatures for
> 202 files in the latest version of the Metasploit Framework. If you use
> the Framework for your job and have a McAfee support contract, *please*
> call them and let them know that their product is incorrectly tagging a
> standard security tool as a "Trojan" and that this is interfering with
> your ability to conduct business.

the external payloads ( such as vncdll.dll ), could be considered a
"possible malware threat"
but not the whole package. ( although i guess if kiddies can root your
server, upload msf, launch msfweb, that would give you a remote attack
platform... right ). Further, to include these sigs on a desktop product is
just ignorant.

mw