<?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: Extensions at War</title>
	<atom:link href="http://www.gnucitizen.org/blog/extensions-at-war/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gnucitizen.org/blog/extensions-at-war/</link>
	<description>Information Security Think Tank</description>
	<lastBuildDate>Sat, 02 Feb 2013 17:50:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.1</generator>
	<item>
		<title>By: rwizard</title>
		<link>http://www.gnucitizen.org/blog/extensions-at-war/comment-page-1/#comment-127779</link>
		<dc:creator>rwizard</dc:creator>
		<pubDate>Thu, 20 Aug 2009 15:41:11 +0000</pubDate>
		<guid isPermaLink="false">https://www.gnucitizen.org/?p=3171#comment-127779</guid>
		<description>One would like to believe that Giorgio learned his lesson.  But I notice that we are slowly but surely creeping back toward his &quot;new nano-update every five minutes&quot; behavior.  A behavior many believe was intended to drive ad revenue.  And I found his apology to sound more like &quot;I am sorry everyone is mad at me, but I really was provoked by the other guy&quot; than &quot;I was wrong, and there can be no justification for what I did&quot;.  So, while there isn&#039;t a comparable alternative, and we are stuck with NoScript for now, I really hope that someone will come along and give us another option.  I think the only things Giorgio learned is that we can&#039;t really do without NoScript, and as long as he is just a little more careful, he can probably get away with a lot.</description>
		<content:encoded><![CDATA[<p>One would like to believe that Giorgio learned his lesson.  But I notice that we are slowly but surely creeping back toward his &#8220;new nano-update every five minutes&#8221; behavior.  A behavior many believe was intended to drive ad revenue.  And I found his apology to sound more like &#8220;I am sorry everyone is mad at me, but I really was provoked by the other guy&#8221; than &#8220;I was wrong, and there can be no justification for what I did&#8221;.  So, while there isn&#8217;t a comparable alternative, and we are stuck with NoScript for now, I really hope that someone will come along and give us another option.  I think the only things Giorgio learned is that we can&#8217;t really do without NoScript, and as long as he is just a little more careful, he can probably get away with a lot.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pdp</title>
		<link>http://www.gnucitizen.org/blog/extensions-at-war/comment-page-1/#comment-126808</link>
		<dc:creator>pdp</dc:creator>
		<pubDate>Sun, 03 May 2009 13:27:54 +0000</pubDate>
		<guid isPermaLink="false">https://www.gnucitizen.org/?p=3171#comment-126808</guid>
		<description>I agree. Also, it is quite fascinating the way the whole situation spanned out. We live in very interesting times :)</description>
		<content:encoded><![CDATA[<p>I agree. Also, it is quite fascinating the way the whole situation spanned out. We live in very interesting times :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mindcorrosive</title>
		<link>http://www.gnucitizen.org/blog/extensions-at-war/comment-page-1/#comment-126805</link>
		<dc:creator>mindcorrosive</dc:creator>
		<pubDate>Sun, 03 May 2009 11:39:58 +0000</pubDate>
		<guid isPermaLink="false">https://www.gnucitizen.org/?p=3171#comment-126805</guid>
		<description>True, Giorgio managed to piss both users and devs with this ill-thought attempt to fund the NoScript development. However, the offending whitelist filters and obfuscation have been removed completely from NoScript as of version 1.9.2.6, together with appologies from Giorgio. 

I seriously doubt that the NoScript team had any harmful intent with pushing the filters to the users, but the way they present it to the users was less than ideal. In fact, I would gladly accept the whitelist filters if I am informed *in advance* what are they doing, together with an option not to install them. 

As for sneaking malicious code, it&#039;s a danger on virtually any platform that allows outside outside addons/plugins. I&#039;m not sure how Mozilla deals with the situation, but AFAIK the extensions undergo testing and control before their acceptance in the official addon repository. But it&#039;s virtually impossible to test every version of every addon for malicious activity. It&#039;s just a matter of trust, the same trust that one gives to their FOSS provider, distribution vendor, or ISP. There&#039;s always a possibility that someone will go rogue, with so many people on the chain. But at some point you need to trust someone to get things done.

Otherwise, the alternative is a closed and isolated platform -- and that&#039;s not going to work (just look how much flak Apple accumulates on rejecting third-party iPhone apps).</description>
		<content:encoded><![CDATA[<p>True, Giorgio managed to piss both users and devs with this ill-thought attempt to fund the NoScript development. However, the offending whitelist filters and obfuscation have been removed completely from NoScript as of version 1.9.2.6, together with appologies from Giorgio. </p>
<p>I seriously doubt that the NoScript team had any harmful intent with pushing the filters to the users, but the way they present it to the users was less than ideal. In fact, I would gladly accept the whitelist filters if I am informed *in advance* what are they doing, together with an option not to install them. </p>
<p>As for sneaking malicious code, it&#8217;s a danger on virtually any platform that allows outside outside addons/plugins. I&#8217;m not sure how Mozilla deals with the situation, but AFAIK the extensions undergo testing and control before their acceptance in the official addon repository. But it&#8217;s virtually impossible to test every version of every addon for malicious activity. It&#8217;s just a matter of trust, the same trust that one gives to their FOSS provider, distribution vendor, or ISP. There&#8217;s always a possibility that someone will go rogue, with so many people on the chain. But at some point you need to trust someone to get things done.</p>
<p>Otherwise, the alternative is a closed and isolated platform &#8212; and that&#8217;s not going to work (just look how much flak Apple accumulates on rejecting third-party iPhone apps).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
