[Secure Network Operations, Inc.] Full Disclosure != Exploit Release

[Strategic Reconnaissance Team <recon () snosoft com>]

All, 

I have been following the subject of full disclosure for a while, and as
most of you know, have dealt with some of the issues that full
disclosure can cause (HP/Secure Network Operations/DMCA).  While the
idea of full disclosure is a good idea, and while we support it, we feel
that the exploit source code should not be released to everyone.

It is possible to prove a vulnerability exists by releasing well written
advisories.  Because of this fact, proof of concept code (exploit
source) is not a requirement for the education of the possibly
vulnerable. Releasing non-malicious exploit code is also not an option
as any local script bunny/kiddie can easily render it functional.

Proof of concept code is useful for legitimate contract based
penetration tests. It is also useful for study as it demonstrates
fundamental flaws computers today (not built in security). But again,
proof of concept code is not for everyone.

I am interested in hearing the opinions of the people on this list. If
you are for exploit source disclosure, I would like to hear arguments
supported by facts, that explain why.  I am equally interested in
reasons why not to disclose information. 

With that said, Secure Network Operations, Inc. will no longer be
releasing functional proof of concept code. We may release sufficiently
detailed advisories. 

        
-- 
Sincerely, 
        Adriel T. Desautels
        Secure Network Operations, Inc. (SNOsoft)
        phone: (978) 263-3829  | http://www.snosoft.com
        --------------------------------------------------------------
        http://www.snosoft.com/documents/SNOsoft-corporate-outline.pdf
        BEDD 0FAD 4CE2 6399 551F  86F5 B036 A540 D47C EC101

Attachment: signature.asc
Description: This is a digitally signed message part