<?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: New express exploit reporting feature and L$ bounty</title>
	<atom:link href="http://blog.secondlife.com/2006/07/31/new-express-exploit-reporting-feature-and-l-bounty/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.secondlife.com/2006/07/31/new-express-exploit-reporting-feature-and-l-bounty/</link>
	<description>By Linden Lab</description>
	<pubDate>Wed, 07 Jan 2009 13:25:04 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Official Linden Blog &#187; Blog Archive Update: Exploit bounty rules and stuff &#171;</title>
		<link>http://blog.secondlife.com/2006/07/31/new-express-exploit-reporting-feature-and-l-bounty/#comment-208124</link>
		<dc:creator>Official Linden Blog &#187; Blog Archive Update: Exploit bounty rules and stuff &#171;</dc:creator>
		<pubDate>Mon, 09 Apr 2007 17:49:36 +0000</pubDate>
		<guid isPermaLink="false">http://lindenlab.wordpress.com/2006/07/31/new-express-exploit-reporting-feature-and-l-bounty/#comment-208124</guid>
		<description>[...] Thursday, August 17th, 2006 at 10:11 AM PDT by: Brent Linden   I&#8217;ve updated both my original post and my follow up post with new information, bounty collection rule clarifications and some more [...]</description>
		<content:encoded><![CDATA[<p>[...] Thursday, August 17th, 2006 at 10:11 AM PDT by: Brent Linden   I&#8217;ve updated both my original post and my follow up post with new information, bounty collection rule clarifications and some more [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: biglietti</title>
		<link>http://blog.secondlife.com/2006/07/31/new-express-exploit-reporting-feature-and-l-bounty/#comment-153274</link>
		<dc:creator>biglietti</dc:creator>
		<pubDate>Fri, 16 Feb 2007 11:28:49 +0000</pubDate>
		<guid isPermaLink="false">http://lindenlab.wordpress.com/2006/07/31/new-express-exploit-reporting-feature-and-l-bounty/#comment-153274</guid>
		<description>luogo fine, sapete..</description>
		<content:encoded><![CDATA[<p>luogo fine, sapete..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Trusted Worlds &#187; Bug Bounties in Second Life</title>
		<link>http://blog.secondlife.com/2006/07/31/new-express-exploit-reporting-feature-and-l-bounty/#comment-10800</link>
		<dc:creator>Trusted Worlds &#187; Bug Bounties in Second Life</dc:creator>
		<pubDate>Mon, 23 Oct 2006 16:39:37 +0000</pubDate>
		<guid isPermaLink="false">http://lindenlab.wordpress.com/2006/07/31/new-express-exploit-reporting-feature-and-l-bounty/#comment-10800</guid>
		<description>[...] Companies paying bounties for bugs and particularly security exploits is notÂ particularly new, there are even business models for standalone companies built around the idea. But I still found this Second Life blog post interesting,Â andÂ certainly topical.Â LindenÂ recentlyÂ closedÂ outÂ aÂ limitedÂ timeÂ offerÂ ofÂ $10kÂ perÂ exploit. [...]</description>
		<content:encoded><![CDATA[<p>[...] Companies paying bounties for bugs and particularly security exploits is notÂ particularly new, there are even business models for standalone companies built around the idea. But I still found this Second Life blog post interesting,Â andÂ certainly topical.Â LindenÂ recentlyÂ closedÂ outÂ aÂ limitedÂ timeÂ offerÂ ofÂ $10kÂ perÂ exploit. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Seraphim Vixen</title>
		<link>http://blog.secondlife.com/2006/07/31/new-express-exploit-reporting-feature-and-l-bounty/#comment-8867</link>
		<dc:creator>Seraphim Vixen</dc:creator>
		<pubDate>Sat, 14 Oct 2006 17:26:10 +0000</pubDate>
		<guid isPermaLink="false">http://lindenlab.wordpress.com/2006/07/31/new-express-exploit-reporting-feature-and-l-bounty/#comment-8867</guid>
		<description>actually even with the inconvience of not being on temporarily i'm glad u all r checking into these things as i myself am a creator and would not want such things to happen to my things so i applaud all of u in sl working so hard to protect all of us :)</description>
		<content:encoded><![CDATA[<p>actually even with the inconvience of not being on temporarily i&#8217;m glad u all r checking into these things as i myself am a creator and would not want such things to happen to my things so i applaud all of u in sl working so hard to protect all of us <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Official Linden Blog &#187; Blog Archive Grid temporarily closed to investigate permissions exploit &#171;</title>
		<link>http://blog.secondlife.com/2006/07/31/new-express-exploit-reporting-feature-and-l-bounty/#comment-7974</link>
		<dc:creator>Official Linden Blog &#187; Blog Archive Grid temporarily closed to investigate permissions exploit &#171;</dc:creator>
		<pubDate>Sat, 14 Oct 2006 14:05:54 +0000</pubDate>
		<guid isPermaLink="false">http://lindenlab.wordpress.com/2006/07/31/new-express-exploit-reporting-feature-and-l-bounty/#comment-7974</guid>
		<description>[...] [7:00 AM PDT] I&#8217;m still here, still reading comments. I wanted to communicate that: (1) if we could have broadcast a warning and given more time to prepare to log off, we would have, because we reserve grid closures for the most serious issues; (2) there&#8217;s no evidence this is a deliberate &#8220;grid attack&#8221;, but an exploit; and (3) I was woken out of bed to get on this, as were several other Lindens, so it must be important. [...]</description>
		<content:encoded><![CDATA[<p>[...] [7:00 AM PDT] I&#8217;m still here, still reading comments. I wanted to communicate that: (1) if we could have broadcast a warning and given more time to prepare to log off, we would have, because we reserve grid closures for the most serious issues; (2) there&#8217;s no evidence this is a deliberate &#8220;grid attack&#8221;, but an exploit; and (3) I was woken out of bed to get on this, as were several other Lindens, so it must be important. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zen Zeddmore</title>
		<link>http://blog.secondlife.com/2006/07/31/new-express-exploit-reporting-feature-and-l-bounty/#comment-1234</link>
		<dc:creator>Zen Zeddmore</dc:creator>
		<pubDate>Tue, 12 Sep 2006 02:50:00 +0000</pubDate>
		<guid isPermaLink="false">http://lindenlab.wordpress.com/2006/07/31/new-express-exploit-reporting-feature-and-l-bounty/#comment-1234</guid>
		<description>* The bug can be used to steal or create Linden Dollars (L$).
   3. You must not use the exploit for personal gain. 

Could you please suggest appropriate protocal to legally and unoffensily comply with BOTH of the above?</description>
		<content:encoded><![CDATA[<p>* The bug can be used to steal or create Linden Dollars (L$).<br />
   3. You must not use the exploit for personal gain. </p>
<p>Could you please suggest appropriate protocal to legally and unoffensily comply with BOTH of the above?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: slothbear</title>
		<link>http://blog.secondlife.com/2006/07/31/new-express-exploit-reporting-feature-and-l-bounty/#comment-1233</link>
		<dc:creator>slothbear</dc:creator>
		<pubDate>Fri, 18 Aug 2006 00:42:10 +0000</pubDate>
		<guid isPermaLink="false">http://lindenlab.wordpress.com/2006/07/31/new-express-exploit-reporting-feature-and-l-bounty/#comment-1233</guid>
		<description>Using the â€œsecondlifeâ€? tag on a post in the Second Life Blog is kind of extra. It tends to obscure the Tag Cloud (where secondlife is currently the biggest tag).</description>
		<content:encoded><![CDATA[<p>Using the â€œsecondlifeâ€? tag on a post in the Second Life Blog is kind of extra. It tends to obscure the Tag Cloud (where secondlife is currently the biggest tag).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SuezanneC Baskerville</title>
		<link>http://blog.secondlife.com/2006/07/31/new-express-exploit-reporting-feature-and-l-bounty/#comment-1232</link>
		<dc:creator>SuezanneC Baskerville</dc:creator>
		<pubDate>Thu, 17 Aug 2006 22:55:26 +0000</pubDate>
		<guid isPermaLink="false">http://lindenlab.wordpress.com/2006/07/31/new-express-exploit-reporting-feature-and-l-bounty/#comment-1232</guid>
		<description>I suppose the restrictions mean I should not file an exploit report for every occurrence of gray textures with white outlines.  Darn.</description>
		<content:encoded><![CDATA[<p>I suppose the restrictions mean I should not file an exploit report for every occurrence of gray textures with white outlines.  Darn.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brent Linden</title>
		<link>http://blog.secondlife.com/2006/07/31/new-express-exploit-reporting-feature-and-l-bounty/#comment-1231</link>
		<dc:creator>Brent Linden</dc:creator>
		<pubDate>Thu, 17 Aug 2006 17:15:44 +0000</pubDate>
		<guid isPermaLink="false">http://lindenlab.wordpress.com/2006/07/31/new-express-exploit-reporting-feature-and-l-bounty/#comment-1231</guid>
		<description>When I mentioned possibly blocking the reports sent by those without payment information, I merely meant that we could block on that because this instant exploit reporting feature could be abused. After thinking more about it, a resident age limit does seem like the way to go. I will discuss it with development and see what can be done. Please note that any restriction placed &lt;strong&gt;will not&lt;/strong&gt; affect your ability to report regular bugs. It merely won't allow you to report bugs with the "Exploit" feature (or, if it does, it won't flag them to be emailed to my phone at 3 am :)

Check out my &lt;a href="http://blog.secondlife.com/2006/08/14/when-an-exploit-isnt-an-exploit/" rel="nofollow"&gt;update&lt;/a&gt; on how the new feature is working and some of the changes we're making. Watch for further up-to-the-minute information in this blog!</description>
		<content:encoded><![CDATA[<p>When I mentioned possibly blocking the reports sent by those without payment information, I merely meant that we could block on that because this instant exploit reporting feature could be abused. After thinking more about it, a resident age limit does seem like the way to go. I will discuss it with development and see what can be done. Please note that any restriction placed <strong>will not</strong> affect your ability to report regular bugs. It merely won&#8217;t allow you to report bugs with the &#8220;Exploit&#8221; feature (or, if it does, it won&#8217;t flag them to be emailed to my phone at 3 am <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /><br />
Check out my <a href="http://blog.secondlife.com/2006/08/14/when-an-exploit-isnt-an-exploit/" rel="nofollow">update</a> on how the new feature is working and some of the changes we&#8217;re making. Watch for further up-to-the-minute information in this blog!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chase Cournoyer</title>
		<link>http://blog.secondlife.com/2006/07/31/new-express-exploit-reporting-feature-and-l-bounty/#comment-1230</link>
		<dc:creator>Chase Cournoyer</dc:creator>
		<pubDate>Thu, 17 Aug 2006 04:57:52 +0000</pubDate>
		<guid isPermaLink="false">http://lindenlab.wordpress.com/2006/07/31/new-express-exploit-reporting-feature-and-l-bounty/#comment-1230</guid>
		<description>Excellent. Never seen a more dedicated Linden :P. Just wondering how many people will ACTUALLY use this after the bounty is over :O</description>
		<content:encoded><![CDATA[<p>Excellent. Never seen a more dedicated Linden :P. Just wondering how many people will ACTUALLY use this after the bounty is over :O</p>
]]></content:encoded>
	</item>
</channel>
</rss>
