i
>
>
>
> -Original Message-
> From: hellNbak [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, January 29, 2003 11:16 PM
> To: Ron DuFresne
> Cc: Strategic Reconnaissance Team; Nicolas Villatte;
> [EMAIL PROTECTED]
> Subject: Re: RE : RE : [Full-Disclosure] [Secure
nt: Wednesday, January 29, 2003 3:00 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: RE : RE : [Full-Disclosure] [Secure Network Operations,
> Inc.] FullDisclosure != Exploit Release
>
>
> Hi!
> From a security professional's point of view, releasing an exploit is
>
Ron DuFresne
Cc: Strategic Reconnaissance Team; Nicolas Villatte;
[EMAIL PROTECTED]
Subject: Re: RE : RE : [Full-Disclosure] [Secure Network Operations,
Inc.] FullDisclosure != Exploit Release
Thanks for adding zero value Ron.
We are not talking about working with vendors or notifying vendors
illatte <[EMAIL PROTECTED]>,
> > [EMAIL PROTECTED]
> > Subject: Re: RE : RE : [Full-Disclosure] [Secure Network Operations,
> > Inc.] FullDisclosure != Exploit Release
> >
> > On Tue, 28 Jan 2003, hellNbak wrote:
> >
> >
> > [SNIP]
>
lt;[EMAIL PROTECTED]>,
> [EMAIL PROTECTED]
> Subject: Re: RE : RE : [Full-Disclosure] [Secure Network Operations,
> Inc.] FullDisclosure != Exploit Release
>
> On Tue, 28 Jan 2003, hellNbak wrote:
>
>
> [SNIP]
>
> >
> > So I say release the
: Re: RE : RE : [Full-Disclosure] [Secure Network Operations,
Inc.]FullDisclosure != Exploit Release
Good points,
One question remains however. If we are to attach exploit code
to our
advisories, how do we protect the innocent from attacks by malicious
people using our exploit code? I hon
Good points,
One question remains however. If we are to attach exploit code to our
advisories, how do we protect the innocent from attacks by malicious
people using our exploit code? I honestly believe that exploits are
digital munitions that should be distributed under restrictions. Do y
