Full Disclosure mailing list archives
RE : [Secure Network Operations, Inc.] Full Disclosure != Exploit Release
From: "Nicolas Villatte" <Nicolas.Villatte () advalvas be>
Date: Tue, 28 Jan 2003 20:22:32 +0100
I am sorry but people who made this virus does not appear as script kiddies to me. Do you prefer to be aware of the exploit like the ones that will use it after some modifications or do you prefer only some "elite" is able to harm the systems? Personally, I prefer to die seeing my enemy than being stabbed. -----Message d'origine----- De : full-disclosure-admin () lists netsys com [mailto:full-disclosure-admin () lists netsys com] De la part de Strategic Reconnaissance Team Envoyé : lundi 27 janvier 2003 3:19 À : full-disclosure () lists netsys com Objet : [Full-Disclosure] [Secure Network Operations, Inc.] Full Disclosure != Exploit Release 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:
smime.p7s
Description:
Current thread:
- [Secure Network Operations, Inc.] Full Disclosure != Exploit Release Strategic Reconnaissance Team (Jan 27)
- RE : [Secure Network Operations, Inc.] Full Disclosure != Exploit Release Nicolas Villatte (Jan 28)
- Re: RE : [Secure Network Operations, Inc.] Full Disclosure != Exploit Release Day Jay (Jan 28)
- Re: RE : [Secure Network Operations, Inc.] Full Disclosure != Exploit Release ATD (Jan 28)
- Re: RE : [Secure Network Operations, Inc.] Full Disclosure != Exploit Release Day Jay (Jan 28)
- Re: RE : [Secure Network Operations, Inc.] Full Disclosure != Exploit Release KF (Jan 28)
- Re: RE : [Secure Network Operations, Inc.] Full Disclosure != Exploit Release Day Jay (Jan 28)
- Re: RE : [Secure Network Operations, Inc.] Full Disclosure != Exploit Release KF (Jan 28)
- Re: RE : [Secure Network Operations, Inc.] Full Disclosure != Exploit Release Steve Poirot (Jan 28)
- Re: RE : [Secure Network Operations, Inc.] Full Disclosure != Exploit Release Berend-Jan Wever (Jan 29)
- Re: RE : [Secure Network Operations, Inc.] Full Disclosure != Exploit Release ATD (Jan 29)
- Re: RE : [Secure Network Operations, Inc.] Full Disclosure != Exploit Release Day Jay (Jan 28)
- RE : [Secure Network Operations, Inc.] Full Disclosure != Exploit Release Nicolas Villatte (Jan 28)