full-disclosure - Publishing exploit code

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: <42C4346D.3080107@csuohio.edu>
Date: Thu Jun 30 19:06:09 2005
From: michael.holstein at csuohio.edu (Michael Holstein)
Subject: Publishing exploit code - what is it good for

> What I need is a security administrator, CSO, IT manager or sys admin that can 
> explain why they find public exploits are good for THEIR organizations. Maybe 
> we can start changing public opinion with regards to full disclosure, and 
> hopefully start with this opinion leader.

Easy .. so we can develop ways to test for the problem.

Public exploit code leads (usually almost instantly) to 
development/improvement of Nessus, Snort, etc. rules.

Cheers,

Michael Holstein CISSP GCIA
Cleveland State University