<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: More on Bugfinding</title>
	<atom:link href="http://spiresecurity.com/?feed=rss2&#038;p=442" rel="self" type="application/rss+xml" />
	<link>http://spiresecurity.com/?p=442</link>
	<description>Risk and Cybersecurity Analysis</description>
	<lastBuildDate>Wed, 21 Aug 2013 23:28:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Pete</title>
		<link>http://spiresecurity.com/?p=442&#038;cpage=1#comment-726</link>
		<dc:creator>Pete</dc:creator>
		<pubDate>Sun, 02 Apr 2006 01:47:58 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=442#comment-726</guid>
		<description><![CDATA[@Robert -

1. If a 12 yr old can find vulns, it really wouldn&#039;t be exercising my intellectual capabilities to do so, right? So why don&#039;t you want to exercise yours? Why don&#039;t you hire a bunch of 12 yr olds to do this work?

2. If you can&#039;t quantify these things, I suggest exercising a little more intellectual capability. It&#039;s really quite simple. A 12 yr old could do it.

3. Why do you equate exploits with incidents? One exploit can be the cause of many incidents, right? So if there have been many more undercover exploits, then name 3, please. Thanks. (Btw, if you know this for a fact, then wouldn&#039;t it be the responsible thing to disclose this information?)

4. Thanks for making my point for me with your sendmail bug example. Why on earth would we want that information discovered and disclosed by the good guys given that we know how quickly the bad guys will react? We&#039;ve gone x years (how far back does this vuln go?) without a single bad guy exploiting that vuln and yet now you are suggesting it is a problem? What about all of those previous years? What are you doing today about the *next* Sendmail vulnerability?

5. I happen to think the important information already *is* underground and you are providing enterprises with comfort food of patching to make their problems go away when they actually aren&#039;t going away. Talk about lulling.

6. It is always amusing that bugfinders think that if they didn&#039;t find the vulnerabilities, then nothing would actually happen - no exploits, no incidents, no nothing. And if you think stuff would happen, then who would be lulled into a false sense of security? Wouldn&#039;t the normal reaction to a (presumably) unexpected exploit be something quite a bit more than a lull?


]]></description>
		<content:encoded><![CDATA[<p>@Robert -</p>
<p>1. If a 12 yr old can find vulns, it really wouldn&#8217;t be exercising my intellectual capabilities to do so, right? So why don&#8217;t you want to exercise yours? Why don&#8217;t you hire a bunch of 12 yr olds to do this work?</p>
<p>2. If you can&#8217;t quantify these things, I suggest exercising a little more intellectual capability. It&#8217;s really quite simple. A 12 yr old could do it.</p>
<p>3. Why do you equate exploits with incidents? One exploit can be the cause of many incidents, right? So if there have been many more undercover exploits, then name 3, please. Thanks. (Btw, if you know this for a fact, then wouldn&#8217;t it be the responsible thing to disclose this information?)</p>
<p>4. Thanks for making my point for me with your sendmail bug example. Why on earth would we want that information discovered and disclosed by the good guys given that we know how quickly the bad guys will react? We&#8217;ve gone x years (how far back does this vuln go?) without a single bad guy exploiting that vuln and yet now you are suggesting it is a problem? What about all of those previous years? What are you doing today about the *next* Sendmail vulnerability?</p>
<p>5. I happen to think the important information already *is* underground and you are providing enterprises with comfort food of patching to make their problems go away when they actually aren&#8217;t going away. Talk about lulling.</p>
<p>6. It is always amusing that bugfinders think that if they didn&#8217;t find the vulnerabilities, then nothing would actually happen &#8211; no exploits, no incidents, no nothing. And if you think stuff would happen, then who would be lulled into a false sense of security? Wouldn&#8217;t the normal reaction to a (presumably) unexpected exploit be something quite a bit more than a lull?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert E. Lee</title>
		<link>http://spiresecurity.com/?p=442&#038;cpage=1#comment-725</link>
		<dc:creator>Robert E. Lee</dc:creator>
		<pubDate>Sun, 02 Apr 2006 01:10:45 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=442#comment-725</guid>
		<description><![CDATA[&gt; I am not sure why I value bugfinder intelligence more than they do themselves (they seem to think that any average Joe can find the vulnerabilities they find; I think they are pretty smart and often find vulnerabilities that attackers never would).

This is a perception you have because you aren&#039;t actively trying to understand the technology deep enough to look for bugs.  You likely have the intellectual capabilities to do so, but because you have not exercised them, the bug finding game seems like magic.  It&#039;s not.  It&#039;s quite easy.  I&#039;ve seen 12 year olds do it.

Your view is also skewed because you attempt to quantify things you can&#039;t measure.  I know for a fact there have been more than 10 &quot;undercover&quot; exploits in the past ten years.  I&#039;d estimate the true incidents are likely in the thousands.

&gt; Bugfinders are ultimately like the street people who want to clean your windshield at a stoplight, do it with muddy water, then expect to be paid for it with gratitude and money. It’s not (necessarily) to say their heart isn’t in the right place, but forced charity that is destructive is pretty hard to be thankful for no matter how much the giver wants to believe it is helpful.

This quote is comedy gold. :)  I may end up using it on a T-Shirt this year in Vegas.

&gt; I think folks should disclose as little as possible and wait as long as possible while still remaining secure from any exploit of the vulns in question.

You realize that this doesn&#039;t work though without a trusted computing base.  Look at the recent Sendmail bug as a case in point.  Based on very limited, and somewhat initially misleading information in the form of an advisory/patch release, in less than 4 hours time we were able to figure out what the vulnerability was and the initial attack vector required to exploit it.  Within 2 days time it was possible to get our PoC to a semi-reliable level.  There are attackers out there that are a lot more gifted at the exploit writing game than we are.  If you release the patches, you are effectively releasing the vulnerability details.  So what&#039;s your solution now, to remain in the world of &quot;responsible disclosure&quot;, should we shame software companies into never admiting security weakness and never releasing patches, because that provides the details of the problem?

Your advocated stance on disclosure, if espoused by law makers, would take the currently freely exchanged information underground.  Can&#039;t say for sure what the outcome would be, but the measureable security for organizations would most likely be a lot worse than it is now, partially because you can not quantify that which can not be measured, and partially because people will be lulled into a false sense of security.

Your angst is somewhat understandable, but unfortunately off target.

Robert
]]></description>
		<content:encoded><![CDATA[<p>> I am not sure why I value bugfinder intelligence more than they do themselves (they seem to think that any average Joe can find the vulnerabilities they find; I think they are pretty smart and often find vulnerabilities that attackers never would).</p>
<p>This is a perception you have because you aren&#8217;t actively trying to understand the technology deep enough to look for bugs.  You likely have the intellectual capabilities to do so, but because you have not exercised them, the bug finding game seems like magic.  It&#8217;s not.  It&#8217;s quite easy.  I&#8217;ve seen 12 year olds do it.</p>
<p>Your view is also skewed because you attempt to quantify things you can&#8217;t measure.  I know for a fact there have been more than 10 &#8220;undercover&#8221; exploits in the past ten years.  I&#8217;d estimate the true incidents are likely in the thousands.</p>
<p>> Bugfinders are ultimately like the street people who want to clean your windshield at a stoplight, do it with muddy water, then expect to be paid for it with gratitude and money. It’s not (necessarily) to say their heart isn’t in the right place, but forced charity that is destructive is pretty hard to be thankful for no matter how much the giver wants to believe it is helpful.</p>
<p>This quote is comedy gold. <img src='http://spiresecurity.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />   I may end up using it on a T-Shirt this year in Vegas.</p>
<p>> I think folks should disclose as little as possible and wait as long as possible while still remaining secure from any exploit of the vulns in question.</p>
<p>You realize that this doesn&#8217;t work though without a trusted computing base.  Look at the recent Sendmail bug as a case in point.  Based on very limited, and somewhat initially misleading information in the form of an advisory/patch release, in less than 4 hours time we were able to figure out what the vulnerability was and the initial attack vector required to exploit it.  Within 2 days time it was possible to get our PoC to a semi-reliable level.  There are attackers out there that are a lot more gifted at the exploit writing game than we are.  If you release the patches, you are effectively releasing the vulnerability details.  So what&#8217;s your solution now, to remain in the world of &#8220;responsible disclosure&#8221;, should we shame software companies into never admiting security weakness and never releasing patches, because that provides the details of the problem?</p>
<p>Your advocated stance on disclosure, if espoused by law makers, would take the currently freely exchanged information underground.  Can&#8217;t say for sure what the outcome would be, but the measureable security for organizations would most likely be a lot worse than it is now, partially because you can not quantify that which can not be measured, and partially because people will be lulled into a false sense of security.</p>
<p>Your angst is somewhat understandable, but unfortunately off target.</p>
<p>Robert</p>
]]></content:encoded>
	</item>
</channel>
</rss>
