<?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: Humble Helps</title>
	<atom:link href="http://coffeetocode.net/2010/05/humble-helps/feed/" rel="self" type="application/rss+xml" />
	<link>http://coffeetocode.net/2010/05/humble-helps/</link>
	<description>Percolating Ideas on Computing &#38; Security</description>
	<lastBuildDate>Fri, 22 Oct 2010 01:28:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Michael Hamilton</title>
		<link>http://coffeetocode.net/2010/05/humble-helps/comment-page-1/#comment-253</link>
		<dc:creator>Michael Hamilton</dc:creator>
		<pubDate>Fri, 25 Jun 2010 03:39:21 +0000</pubDate>
		<guid isPermaLink="false">http://coffeetocode.net/?p=220#comment-253</guid>
		<description>Excellent post.  I agree completely that consulting skills are important during a negotiation on something so sensitive as vulnerability disclosure.  I would note that the product vendor also has something to learn here.

    - mkh</description>
		<content:encoded><![CDATA[<p>Excellent post.  I agree completely that consulting skills are important during a negotiation on something so sensitive as vulnerability disclosure.  I would note that the product vendor also has something to learn here.</p>
<p>    &#8211; mkh</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel</title>
		<link>http://coffeetocode.net/2010/05/humble-helps/comment-page-1/#comment-188</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Sun, 20 Jun 2010 00:35:00 +0000</pubDate>
		<guid isPermaLink="false">http://coffeetocode.net/?p=220#comment-188</guid>
		<description>The latest version of OpenCart 1.4.8 does not have a problem with CSRF attacks. It is very secure.</description>
		<content:encoded><![CDATA[<p>The latest version of OpenCart 1.4.8 does not have a problem with CSRF attacks. It is very secure.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Senta</title>
		<link>http://coffeetocode.net/2010/05/humble-helps/comment-page-1/#comment-123</link>
		<dc:creator>Senta</dc:creator>
		<pubDate>Tue, 01 Jun 2010 21:21:39 +0000</pubDate>
		<guid isPermaLink="false">http://coffeetocode.net/?p=220#comment-123</guid>
		<description>I found this blog post very thoughtful, and very wise. And for the record, I thought along the same lines as Norbert did. 

Patrick: I think the approach you (&amp; Norbert) outlined will help more people in the end. And to me, that&#039;s what&#039;s important.</description>
		<content:encoded><![CDATA[<p>I found this blog post very thoughtful, and very wise. And for the record, I thought along the same lines as Norbert did. </p>
<p>Patrick: I think the approach you (&amp; Norbert) outlined will help more people in the end. And to me, that&#8217;s what&#8217;s important.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Norbert Griffin</title>
		<link>http://coffeetocode.net/2010/05/humble-helps/comment-page-1/#comment-104</link>
		<dc:creator>Norbert Griffin</dc:creator>
		<pubDate>Tue, 25 May 2010 11:43:05 +0000</pubDate>
		<guid isPermaLink="false">http://coffeetocode.net/?p=220#comment-104</guid>
		<description>Hi Patrick

I can’t help but think about the Dale Carnegie book “How to win friends and influence”. 

If Ben’s goal was to get the CSRF issue, fixed then really he needs to change his approach. Each one of the 12 items below can apply.

Twelve Ways to Win People to Your Way of Thinking
1.	Avoid arguments.
2.	Show respect for the other person&#039;s opinions. Never tell someone they are wrong.
3.	If you&#039;re wrong, admit it quickly and emphatically.
4.	Begin in a friendly way.
5.	Start with questions the other person will answer yes to.
6.	Let the other person do the talking.
7.	Let the other person feel the idea is his/hers.
8.	Try honestly to see things from the other person&#039;s point of view.
9.	Sympathize with the other person.
10.	Appeal to noble motives.
11.	Dramatize your ideas.
12.	Throw down a challenge &amp; don&#039;t talk negative when the person is absent, talk about only positive.

So much of what we do as security professional requires this. I’m sure the majority of technical people feel their systems are secure. Who wants to admit they don’t understand what they are doing? Who wants to be told they screwed up? There is a better way.

We have to be influential in our approach. Showing respect and being friendly are always important. 

Good work on the article

Cheers,
Norbert Griffin</description>
		<content:encoded><![CDATA[<p>Hi Patrick</p>
<p>I can’t help but think about the Dale Carnegie book “How to win friends and influence”. </p>
<p>If Ben’s goal was to get the CSRF issue, fixed then really he needs to change his approach. Each one of the 12 items below can apply.</p>
<p>Twelve Ways to Win People to Your Way of Thinking<br />
1.	Avoid arguments.<br />
2.	Show respect for the other person&#8217;s opinions. Never tell someone they are wrong.<br />
3.	If you&#8217;re wrong, admit it quickly and emphatically.<br />
4.	Begin in a friendly way.<br />
5.	Start with questions the other person will answer yes to.<br />
6.	Let the other person do the talking.<br />
7.	Let the other person feel the idea is his/hers.<br />
8.	Try honestly to see things from the other person&#8217;s point of view.<br />
9.	Sympathize with the other person.<br />
10.	Appeal to noble motives.<br />
11.	Dramatize your ideas.<br />
12.	Throw down a challenge &amp; don&#8217;t talk negative when the person is absent, talk about only positive.</p>
<p>So much of what we do as security professional requires this. I’m sure the majority of technical people feel their systems are secure. Who wants to admit they don’t understand what they are doing? Who wants to be told they screwed up? There is a better way.</p>
<p>We have to be influential in our approach. Showing respect and being friendly are always important. </p>
<p>Good work on the article</p>
<p>Cheers,<br />
Norbert Griffin</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick Thomas</title>
		<link>http://coffeetocode.net/2010/05/humble-helps/comment-page-1/#comment-99</link>
		<dc:creator>Patrick Thomas</dc:creator>
		<pubDate>Mon, 24 May 2010 18:16:08 +0000</pubDate>
		<guid isPermaLink="false">http://coffeetocode.net/?p=220#comment-99</guid>
		<description>Hi All,

Thanks for commenting. Yes, I&#039;m with you guys; I think Ben did a good thing, and actually did go above and beyond (further than I&#039;d probably have gone before authoring this post). With the post I was just trying to think about how far beyond one would have to go to get through to the truly truculent. 

Ali,
Yup; public disclosure always has to be on the table in our minds, but there&#039;s no need to whip it out in the first email. 

Rafal,
The patch-breaking behavior just does it for me: that&#039;s beyond ridiculous, though it does show that ego is in play ;) I think that probably vindicates Ben that nothing would have made the difference, but my post was a bit of a thought experiment anyway.

CG,
Yes! OWASP FTW! Though, I did note that the countermeasures  discussion on the CSRF page is java-centric. The ideas are of course portable, but maybe the page should make that clear. (http://www.owasp.org/index.php/Cross-Site_Request_Forgery_%28CSRF%29_Prevention_Cheat_Sheet)

Good to see some new faces!

Cheers,
~PST</description>
		<content:encoded><![CDATA[<p>Hi All,</p>
<p>Thanks for commenting. Yes, I&#8217;m with you guys; I think Ben did a good thing, and actually did go above and beyond (further than I&#8217;d probably have gone before authoring this post). With the post I was just trying to think about how far beyond one would have to go to get through to the truly truculent. </p>
<p>Ali,<br />
Yup; public disclosure always has to be on the table in our minds, but there&#8217;s no need to whip it out in the first email. </p>
<p>Rafal,<br />
The patch-breaking behavior just does it for me: that&#8217;s beyond ridiculous, though it does show that ego is in play <img src='http://coffeetocode.net/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' />  I think that probably vindicates Ben that nothing would have made the difference, but my post was a bit of a thought experiment anyway.</p>
<p>CG,<br />
Yes! OWASP FTW! Though, I did note that the countermeasures  discussion on the CSRF page is java-centric. The ideas are of course portable, but maybe the page should make that clear. (<a href="http://www.owasp.org/index.php/Cross-Site_Request_Forgery_%28CSRF%29_Prevention_Cheat_Sheet" rel="nofollow">http://www.owasp.org/index.php/Cross-Site_Request_Forgery_%28CSRF%29_Prevention_Cheat_Sheet</a>)</p>
<p>Good to see some new faces!</p>
<p>Cheers,<br />
~PST</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Psychology of &#34;Secure Code&#34; - Following the White Rabbit - A Practical Security Blog -</title>
		<link>http://coffeetocode.net/2010/05/humble-helps/comment-page-1/#comment-98</link>
		<dc:creator>Psychology of &#34;Secure Code&#34; - Following the White Rabbit - A Practical Security Blog -</dc:creator>
		<pubDate>Mon, 24 May 2010 15:08:29 +0000</pubDate>
		<guid isPermaLink="false">http://coffeetocode.net/?p=220#comment-98</guid>
		<description>[...] Recently I&#039;ve seen a few good posts out there that reminded me just how and why this is such a difficult battle.&#160; The matter of the [...]</description>
		<content:encoded><![CDATA[<p>[...] Recently I&#39;ve seen a few good posts out there that reminded me just how and why this is such a difficult battle.&nbsp; The matter of the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CG</title>
		<link>http://coffeetocode.net/2010/05/humble-helps/comment-page-1/#comment-94</link>
		<dc:creator>CG</dc:creator>
		<pubDate>Mon, 24 May 2010 13:10:08 +0000</pubDate>
		<guid isPermaLink="false">http://coffeetocode.net/?p=220#comment-94</guid>
		<description>i agree with having tact and being cognizant of others feelings (especially developers--it is their baby you are beating up on). BUT if you sell a product and have customers especially when processing payments is involved the developer may need to swallow some pride when confronted with a security issue, you owe it to your customers who paid for your product.

Daniel should be happy that Ben even sent him an email about the problem before going public or blogging on it.  The lack of knowledge about basic web attacks also means that the opencart team should probably spend some time on the OWASP site.</description>
		<content:encoded><![CDATA[<p>i agree with having tact and being cognizant of others feelings (especially developers&#8211;it is their baby you are beating up on). BUT if you sell a product and have customers especially when processing payments is involved the developer may need to swallow some pride when confronted with a security issue, you owe it to your customers who paid for your product.</p>
<p>Daniel should be happy that Ben even sent him an email about the problem before going public or blogging on it.  The lack of knowledge about basic web attacks also means that the opencart team should probably spend some time on the OWASP site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rafal Los</title>
		<link>http://coffeetocode.net/2010/05/humble-helps/comment-page-1/#comment-93</link>
		<dc:creator>Rafal Los</dc:creator>
		<pubDate>Mon, 24 May 2010 13:08:48 +0000</pubDate>
		<guid isPermaLink="false">http://coffeetocode.net/?p=220#comment-93</guid>
		<description>Interesting perspective ... I do see both sides of it .  The escalation into the 5-year-old playground mentality when the developer (purposely?) breaks the patch is just stupid though.  I&#039;m not sure I could believe attributing that to the early offensive take by Ben.

Sad.

/Raf</description>
		<content:encoded><![CDATA[<p>Interesting perspective &#8230; I do see both sides of it .  The escalation into the 5-year-old playground mentality when the developer (purposely?) breaks the patch is just stupid though.  I&#8217;m not sure I could believe attributing that to the early offensive take by Ben.</p>
<p>Sad.</p>
<p>/Raf</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 0xAli</title>
		<link>http://coffeetocode.net/2010/05/humble-helps/comment-page-1/#comment-92</link>
		<dc:creator>0xAli</dc:creator>
		<pubDate>Mon, 24 May 2010 12:38:36 +0000</pubDate>
		<guid isPermaLink="false">http://coffeetocode.net/?p=220#comment-92</guid>
		<description>
It&#039;s not only OpenCart, even &quot;big&quot; some vendors *cough* microsoft *cough* ignore some reports and such.
And IMHO the only way to deal with security-by-obscurity vendors is publishing vulnerabilities [after a note/letter/email].

Ben went very very far, i don&#039;t think i&#039;d go like that :P

-0xAli</description>
		<content:encoded><![CDATA[<p>It&#8217;s not only OpenCart, even &#8220;big&#8221; some vendors *cough* microsoft *cough* ignore some reports and such.<br />
And IMHO the only way to deal with security-by-obscurity vendors is publishing vulnerabilities [after a note/letter/email].</p>
<p>Ben went very very far, i don&#8217;t think i&#8217;d go like that <img src='http://coffeetocode.net/wp-includes/images/smilies/icon_razz.gif' alt=':P' class='wp-smiley' /> </p>
<p>-0xAli</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tweets that mention Coffee To Code » Blog Archive » Humble Helps -- Topsy.com</title>
		<link>http://coffeetocode.net/2010/05/humble-helps/comment-page-1/#comment-91</link>
		<dc:creator>Tweets that mention Coffee To Code » Blog Archive » Humble Helps -- Topsy.com</dc:creator>
		<pubDate>Mon, 24 May 2010 06:58:36 +0000</pubDate>
		<guid isPermaLink="false">http://coffeetocode.net/?p=220#comment-91</guid>
		<description>[...] This post was mentioned on Twitter by Roer.com - the Blog!, kakroo. kakroo said: Humble Helps http://bit.ly/aqY9Wc #Security [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by Roer.com &#8211; the Blog!, kakroo. kakroo said: Humble Helps <a href="http://bit.ly/aqY9Wc" rel="nofollow">http://bit.ly/aqY9Wc</a> #Security [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

