<?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 for Mozilla Security Blog</title>
	<atom:link href="http://blog.mozilla.com/security/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mozilla.com/security</link>
	<description></description>
	<lastBuildDate>Thu, 19 Nov 2009 15:36:11 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Component Directory Lockdown &#8211; New in Firefox 3.6 by Daniel Veditz</title>
		<link>http://blog.mozilla.com/security/2009/11/16/component-directory-lockdown-new-in-firefox-3-6/comment-page-1/#comment-108403</link>
		<dc:creator>Daniel Veditz</dc:creator>
		<pubDate>Thu, 19 Nov 2009 15:36:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/security/?p=213#comment-108403</guid>
		<description>I read too quickly and assumed you were talking about this blog post, but you were talking about addon compatibility version checks which is something else entirely. Beta users do sign up for a little pain in that regard, but you can help if you like by using the Addon Compatibility Reporter which will reenable all of your addons and let you report which ones work and which don&#039;t.

https://addons.mozilla.org/en-US/firefox/addon/15003

Or you can wait until after we ship 3.6 by which point most of the addons should be compatible.</description>
		<content:encoded><![CDATA[<p>I read too quickly and assumed you were talking about this blog post, but you were talking about addon compatibility version checks which is something else entirely. Beta users do sign up for a little pain in that regard, but you can help if you like by using the Addon Compatibility Reporter which will reenable all of your addons and let you report which ones work and which don&#8217;t.</p>
<p><a href="https://addons.mozilla.org/en-US/firefox/addon/15003" rel="nofollow">https://addons.mozilla.org/en-US/firefox/addon/15003</a></p>
<p>Or you can wait until after we ship 3.6 by which point most of the addons should be compatible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Component Directory Lockdown &#8211; New in Firefox 3.6 by Daniel Veditz</title>
		<link>http://blog.mozilla.com/security/2009/11/16/component-directory-lockdown-new-in-firefox-3-6/comment-page-1/#comment-108402</link>
		<dc:creator>Daniel Veditz</dc:creator>
		<pubDate>Thu, 19 Nov 2009 15:30:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/security/?p=213#comment-108402</guid>
		<description>This feature is not about addons, this prevents 3rd party software from hooking into Firefox in a way that is guaranteed to break (and does) at the next major update. Possibly on a minor update for binary components depending if they were using an interface we had to patch. This was never a recommended or even documented mechanism for extending Firefox, and we&#039;ve found a large percentage of the crashes experienced by Firefox 3.5 users is due to 3rd party components hooked in this way.

Plugins and Addons hooked in through the documented places certainly do cause their share of stability problems also, but since it is possible for users to know about and manage them we do let you make your own tradeoff between functionality and possible instability.</description>
		<content:encoded><![CDATA[<p>This feature is not about addons, this prevents 3rd party software from hooking into Firefox in a way that is guaranteed to break (and does) at the next major update. Possibly on a minor update for binary components depending if they were using an interface we had to patch. This was never a recommended or even documented mechanism for extending Firefox, and we&#8217;ve found a large percentage of the crashes experienced by Firefox 3.5 users is due to 3rd party components hooked in this way.</p>
<p>Plugins and Addons hooked in through the documented places certainly do cause their share of stability problems also, but since it is possible for users to know about and manage them we do let you make your own tradeoff between functionality and possible instability.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Component Directory Lockdown &#8211; New in Firefox 3.6 by Zetaprime</title>
		<link>http://blog.mozilla.com/security/2009/11/16/component-directory-lockdown-new-in-firefox-3-6/comment-page-1/#comment-108399</link>
		<dc:creator>Zetaprime</dc:creator>
		<pubDate>Thu, 19 Nov 2009 06:10:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/security/?p=213#comment-108399</guid>
		<description>Is there anyway to disable this feature? I&#039;d like to be able to decide which addons I can keep and not have Firefox tell me I can&#039;t use them. I already had to uninstall 3.6 beta 3 and go back to beta 2 to get my addons back. Let me decide if I can live with a certain degree of instability in exchange for the functionality many of these addons provide.</description>
		<content:encoded><![CDATA[<p>Is there anyway to disable this feature? I&#8217;d like to be able to decide which addons I can keep and not have Firefox tell me I can&#8217;t use them. I already had to uninstall 3.6 beta 3 and go back to beta 2 to get my addons back. Let me decide if I can live with a certain degree of instability in exchange for the functionality many of these addons provide.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Component Directory Lockdown &#8211; New in Firefox 3.6 by Daniel Veditz</title>
		<link>http://blog.mozilla.com/security/2009/11/16/component-directory-lockdown-new-in-firefox-3-6/comment-page-1/#comment-108397</link>
		<dc:creator>Daniel Veditz</dc:creator>
		<pubDate>Wed, 18 Nov 2009 19:47:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/security/?p=213#comment-108397</guid>
		<description>In what other application is it normal to modify their installation directory? We have published for years several appropriate ways to extend Firefox and this was not one of them. It happened to work, but it was never a supported way for 3rd parties to modify a Firefox installation.</description>
		<content:encoded><![CDATA[<p>In what other application is it normal to modify their installation directory? We have published for years several appropriate ways to extend Firefox and this was not one of them. It happened to work, but it was never a supported way for 3rd parties to modify a Firefox installation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Component Directory Lockdown &#8211; New in Firefox 3.6 by Dis Gruntled</title>
		<link>http://blog.mozilla.com/security/2009/11/16/component-directory-lockdown-new-in-firefox-3-6/comment-page-1/#comment-108396</link>
		<dc:creator>Dis Gruntled</dc:creator>
		<pubDate>Wed, 18 Nov 2009 18:35:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/security/?p=213#comment-108396</guid>
		<description>Once again, Mozilla shows love to their large developer base by easing in a significant change thru a tried-and-true deprecation process, whereby developers are encouraged to make the necessary changes over a period of time, many months in advance of Firefox dropping a key feature.

Wait... um...  OK, scratch that.  Nevermind.</description>
		<content:encoded><![CDATA[<p>Once again, Mozilla shows love to their large developer base by easing in a significant change thru a tried-and-true deprecation process, whereby developers are encouraged to make the necessary changes over a period of time, many months in advance of Firefox dropping a key feature.</p>
<p>Wait&#8230; um&#8230;  OK, scratch that.  Nevermind.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Component Directory Lockdown &#8211; New in Firefox 3.6 by Daniel Veditz</title>
		<link>http://blog.mozilla.com/security/2009/11/16/component-directory-lockdown-new-in-firefox-3-6/comment-page-1/#comment-108390</link>
		<dc:creator>Daniel Veditz</dc:creator>
		<pubDate>Tue, 17 Nov 2009 21:42:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/security/?p=213#comment-108390</guid>
		<description>To put &quot;20 times a day&quot; in perspective that&#039;s about how many crashes we&#039;re currently seeing from a few hundred 3.6 Beta users put together.</description>
		<content:encoded><![CDATA[<p>To put &#8220;20 times a day&#8221; in perspective that&#8217;s about how many crashes we&#8217;re currently seeing from a few hundred 3.6 Beta users put together.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Component Directory Lockdown &#8211; New in Firefox 3.6 by Daniel Veditz</title>
		<link>http://blog.mozilla.com/security/2009/11/16/component-directory-lockdown-new-in-firefox-3-6/comment-page-1/#comment-108389</link>
		<dc:creator>Daniel Veditz</dc:creator>
		<pubDate>Tue, 17 Nov 2009 21:35:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/security/?p=213#comment-108389</guid>
		<description>Firefox 3.6 has not been released yet, you do not have &quot;ff 3.6 final&quot;. Keep reporting those crashes: that&#039;s how we know which ones are the most important to focus on. If you&#039;re crashing 20 times a day, though, you&#039;re suffering from some software incompatibility between Firefox and something else on your system. Please visit the forums at http://support.mozilla.com and they can help you figure out what&#039;s going on from you reported crashes and probably help you identify the culprit.</description>
		<content:encoded><![CDATA[<p>Firefox 3.6 has not been released yet, you do not have &#8220;ff 3.6 final&#8221;. Keep reporting those crashes: that&#8217;s how we know which ones are the most important to focus on. If you&#8217;re crashing 20 times a day, though, you&#8217;re suffering from some software incompatibility between Firefox and something else on your system. Please visit the forums at <a href="http://support.mozilla.com" rel="nofollow">http://support.mozilla.com</a> and they can help you figure out what&#8217;s going on from you reported crashes and probably help you identify the culprit.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Component Directory Lockdown &#8211; New in Firefox 3.6 by Babua</title>
		<link>http://blog.mozilla.com/security/2009/11/16/component-directory-lockdown-new-in-firefox-3-6/comment-page-1/#comment-108387</link>
		<dc:creator>Babua</dc:creator>
		<pubDate>Tue, 17 Nov 2009 13:25:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/security/?p=213#comment-108387</guid>
		<description>ff 3.6 final has also been crashing frequently in my Windows 7. About 20 times today. It is a very poor show. I installed the latest version today only.</description>
		<content:encoded><![CDATA[<p>ff 3.6 final has also been crashing frequently in my Windows 7. About 20 times today. It is a very poor show. I installed the latest version today only.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Component Directory Lockdown &#8211; New in Firefox 3.6 by David Naylor</title>
		<link>http://blog.mozilla.com/security/2009/11/16/component-directory-lockdown-new-in-firefox-3-6/comment-page-1/#comment-108386</link>
		<dc:creator>David Naylor</dc:creator>
		<pubDate>Tue, 17 Nov 2009 10:38:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/security/?p=213#comment-108386</guid>
		<description>Woah, huge user win.

No more shady deals when installing other software. At least not with Firefox add-ons bundled.

Being in control is one of the main reasons for using Firefox, and that just got even better with this change.</description>
		<content:encoded><![CDATA[<p>Woah, huge user win.</p>
<p>No more shady deals when installing other software. At least not with Firefox add-ons bundled.</p>
<p>Being in control is one of the main reasons for using Firefox, and that just got even better with this change.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Mozilla Plugin Check Now Live by Daniel Veditz</title>
		<link>http://blog.mozilla.com/security/2009/10/13/mozilla-plugin-check-now-live/comment-page-1/#comment-108338</link>
		<dc:creator>Daniel Veditz</dc:creator>
		<pubDate>Mon, 09 Nov 2009 18:50:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/security/?p=186#comment-108338</guid>
		<description>sendadiet:

The Plugin Check page was released as a bit of an experiment. We&#039;re working on translations but wanted to get feedback before we got that done. The upcoming Firefox 3.6 refers people to this page and we expect translated versions of Firefox will have translated versions of the Plugin Check to link to.

(from Google translate):
La página Plugin cheque fue lanzado como un poco de un experimento. Estamos trabajando en la traducción, pero quería recibir comentarios antes de llegar a hacerlo bien. El próximo Firefox 3.6 se refiere la gente a esta página y esperamos versiones traducidas de Firefox se han traducido las versiones de los Comprobar plug-in para el vínculo.</description>
		<content:encoded><![CDATA[<p>sendadiet:</p>
<p>The Plugin Check page was released as a bit of an experiment. We&#8217;re working on translations but wanted to get feedback before we got that done. The upcoming Firefox 3.6 refers people to this page and we expect translated versions of Firefox will have translated versions of the Plugin Check to link to.</p>
<p>(from Google translate):<br />
La página Plugin cheque fue lanzado como un poco de un experimento. Estamos trabajando en la traducción, pero quería recibir comentarios antes de llegar a hacerlo bien. El próximo Firefox 3.6 se refiere la gente a esta página y esperamos versiones traducidas de Firefox se han traducido las versiones de los Comprobar plug-in para el vínculo.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
