<?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: Firefox and Mozilla Patch Exploit</title>
	<atom:link href="http://www.forevergeek.com/2005/02/firefox_and_mozilla_patch_exploit/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.forevergeek.com/2005/02/firefox_and_mozilla_patch_exploit/</link>
	<description>Nerds are for Dorks</description>
	<lastBuildDate>Fri, 10 Feb 2012 21:04:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Konstantinos</title>
		<link>http://www.forevergeek.com/2005/02/firefox_and_mozilla_patch_exploit/#comment-10199</link>
		<dc:creator>Konstantinos</dc:creator>
		<pubDate>Wed, 09 Feb 2005 14:10:23 +0000</pubDate>
		<guid isPermaLink="false">http://forevergeek.com/?p=1209#comment-10199</guid>
		<description>Speaking of Firefox upgrades, do you still have to remove the version installed, before upgrading to another build?</description>
		<content:encoded><![CDATA[<p>Speaking of Firefox upgrades, do you still have to remove the version installed, before upgrading to another build?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Someone</title>
		<link>http://www.forevergeek.com/2005/02/firefox_and_mozilla_patch_exploit/#comment-10198</link>
		<dc:creator>Someone</dc:creator>
		<pubDate>Wed, 09 Feb 2005 07:04:34 +0000</pubDate>
		<guid isPermaLink="false">http://forevergeek.com/?p=1209#comment-10198</guid>
		<description>Personally, I don&#039;t see how it really fixesa problem unless they are releasing an actual PATCH to the released version of Firefox. Telling a corporation with 500 machines (or 5,000) running Firefox that they need to download the nightly build instead of patching the released build is not really acceptable. That nightly build will have all sorts of bugs from other code churn. Do people really think that it doesn&#039;t matter?

When I get an IE patch, it&#039;s a PATCH to the SHIPPED version so I don&#039;t have to go redeploy the entire browser (and an untested version at that).</description>
		<content:encoded><![CDATA[<p>Personally, I don&#8217;t see how it really fixesa problem unless they are releasing an actual PATCH to the released version of Firefox. Telling a corporation with 500 machines (or 5,000) running Firefox that they need to download the nightly build instead of patching the released build is not really acceptable. That nightly build will have all sorts of bugs from other code churn. Do people really think that it doesn&#8217;t matter?</p>
<p>When I get an IE patch, it&#8217;s a PATCH to the SHIPPED version so I don&#8217;t have to go redeploy the entire browser (and an untested version at that).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil Ringnalda</title>
		<link>http://www.forevergeek.com/2005/02/firefox_and_mozilla_patch_exploit/#comment-10197</link>
		<dc:creator>Phil Ringnalda</dc:creator>
		<pubDate>Wed, 09 Feb 2005 05:12:45 +0000</pubDate>
		<guid isPermaLink="false">http://forevergeek.com/?p=1209#comment-10197</guid>
		<description>I think it&#039;s fantastic how much good &quot;press&quot; Firefox is getting for that 12 hour fix, when you consider the fact that, um, it ain&#039;t a fix for the &#039;sploit, it&#039;s a fix for the fact that until sometime in December, we were ignoring a whole set of prefs including the one to disable IDNs, except for right when you set them. That fix enables you not get phished by letting you completely prevent yourself from getting to domains with non-ASCII characters (except of course that there&#039;s generally an ASCII-only alternative around, since the 800lb gorilla hasn&#039;t implemented IDN yet).</description>
		<content:encoded><![CDATA[<p>I think it&#8217;s fantastic how much good &#8220;press&#8221; Firefox is getting for that 12 hour fix, when you consider the fact that, um, it ain&#8217;t a fix for the &#8216;sploit, it&#8217;s a fix for the fact that until sometime in December, we were ignoring a whole set of prefs including the one to disable IDNs, except for right when you set them. That fix enables you not get phished by letting you completely prevent yourself from getting to domains with non-ASCII characters (except of course that there&#8217;s generally an ASCII-only alternative around, since the 800lb gorilla hasn&#8217;t implemented IDN yet).</p>
]]></content:encoded>
	</item>
</channel>
</rss>

