full-disclosure - RE: 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>] [day] [month] [year] [list]

Message-ID: <1c36dfc405063010135c35755@mail.gmail.com>
Date: Thu Jun 30 18:45:48 2005
From: matthewhuston at gmail.com (Matt Huston)
Subject: RE: Publishing exploit code - what is it good for

I remember using a published exploit to show proof positive something 
malicious could be done to an email gateway. This so frightened the
higher ups they instituted a rigorous security policy and encouraged
me to keep abreast of constant developments. I have free reign to use
any code be it malicious or trustworthy to secure the systems I am
responsible for now.