<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>. ..::Hyn172.info::..  .  Nguyễn Hồng Hải &#187; mozilla</title>
	<atom:link href="http://nguyenhonghai.com/tag/mozilla/feed/" rel="self" type="application/rss+xml" />
	<link>http://nguyenhonghai.com</link>
	<description></description>
	<lastBuildDate>Sat, 11 Jun 2011 19:49:11 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
		<item>
		<title>Firefox Update Closes Security Holes, Thunderbird Still Vulnerable</title>
		<link>http://nguyenhonghai.com/2009/03/06/firefox-update-closes-security-holes-thunderbird-still-vulnerable/</link>
		<comments>http://nguyenhonghai.com/2009/03/06/firefox-update-closes-security-holes-thunderbird-still-vulnerable/#comments</comments>
		<pubDate>Fri, 06 Mar 2009 04:13:01 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Diary]]></category>
		<category><![CDATA[firefox]]></category>
		<category><![CDATA[mozilla]]></category>

		<guid isPermaLink="false">http://nguyenhonghai.com/?p=138</guid>
		<description><![CDATA[The latest update to the open-source browser shores up a number of security risks, including some that Mozilla says could be exploited by an attacker to run commands on a vulnerable computer. But the flaws still affect the current Thunderbird release, 2.0.0.19. One of the bugs involves a library used for PNG images, and could [...]]]></description>
		<wfw:commentRss>http://nguyenhonghai.com/2009/03/06/firefox-update-closes-security-holes-thunderbird-still-vulnerable/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
