Search: Home Bugtraq Vulnerabilities Mailing Lists Jobs Tools Beta Programs
Exploit Code on Trial
Kevin Poulsen, SecurityFocus 2003-11-23

Security pros gathering at a Stanford University Law School conference on responsible vulnerability disclosure Saturday harmonized on the principle that vendors should be privately notified of holes in their products, and given at least some time to produce a patch before any public disclosure is made. But there was pronounced disagreement on the question of whether or not researchers should publicly release proof-of-concept code to demonstrate a vulnerability.

Comments Mode:
Exploit Code on Trial 2003-11-24
Anonymous
Obviously, giving out the exploit code is the best way to put everyone on an equal footing. If a handful of people have it, but nobody else, there is an inherent inequality that leads to much more serious computer security problems than those we currently see.

Having exploits to software that I'm running is the only way I can reasonably test security measures I have in place, since investigating and developing security exploits is not feasable without a huge budget. One way to get a huge budget is to sell your discoveries to professional criminals, the other is to let everyone hand out their discoveries freely, that way each organization only foots a small portion of the overall bill to discover all the known security problems.

[ reply ]

Link to this comment: http://www.securityfocus.com/comments/articles/7511/23824#23824
Screw the vendors 2003-11-24
Anonymous (2 replies)
Screw the vendors 2003-11-25
Rodrigo Otaviano <rodrigo (at) otaviano (dot) com [email concealed]>
Exploit Code on Trial 2003-11-24
Bob Radvanovsky
Exploit Code on Trial 2003-11-24
Anonymous
Exploit Code on Trial 2003-11-24
TW
Exploit Code on Trial 2003-11-25
Leif Ericksen
Exploit Code on Trial - final word 2003-11-25
Anonymous (1 replies)
Exploit Code on Trial 2003-11-25
Camel
Loss of money 2003-11-29
bl0rf
Exploit Code on Trial 2003-12-02
Anonymous
Exploit Code on Trial 2003-12-02
Anonymous







 

Privacy Statement
Copyright 2009, SecurityFocus