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

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]

From: rms at computerbytesman.com (Richard M. Smith)
Subject: [Secure Network Operations, Inc.] Full Disclosure != Exploit Release

Today, it's a decision made by the security researcher and the company
they work for who gets what exploit code.  Down the road, my expectation
is that the question will be addressed in courts via civil lawsuits.  

Richard

-----Original Message-----
From: Day Jay [mailto:d4yj4y@...oo.com] 
Sent: Wednesday, January 29, 2003 5:16 PM
To: Richard M. Smith
Cc: full-disclosure@...ts.netsys.com
Subject: RE: [Full-Disclosure] [Secure Network Operations, Inc.] Full
Disclosure != Exploit Release

And what makes you think that you and your friends who
share your dozen exploits are the right hands? What
because you have the skill to write them, you are the
right hands?

Who decides who can have what?

That's what I thought.

> 
> OTOH we know that public proof-of-concept examples
> are going to get into
> the wrong hands.
> 
> Richard
> 

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com