<?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>about:mozilla &#187; Security</title>
	<atom:link href="http://blog.mozilla.com/about_mozilla/category/security/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mozilla.com/about_mozilla</link>
	<description></description>
	<lastBuildDate>Tue, 17 Nov 2009 14:29:55 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Mozilla and certification authorities</title>
		<link>http://blog.mozilla.com/about_mozilla/2008/08/22/mozilla-and-certification-authorities/</link>
		<comments>http://blog.mozilla.com/about_mozilla/2008/08/22/mozilla-and-certification-authorities/#comments</comments>
		<pubDate>Fri, 22 Aug 2008 18:16:49 +0000</pubDate>
		<dc:creator>deb</dc:creator>
				<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://blog.mozilla.com/about_mozilla/?p=69</guid>
		<description><![CDATA[Frank Hecker writes, &#8220;Johnathan Nightingale recently addressed a very common question, namely why Firefox doesn&#8217;t automatically accept self-signed SSL certificates as being valid.  I don&#8217;t have much to add to Johnathan&#8217;s discussion of the issues with self-signed certificates, but speaking on behalf of the Mozilla Foundation I do want to address some of the [...]]]></description>
			<content:encoded><![CDATA[<p>Frank Hecker <a href="http://blog.hecker.org/2008/08/20/mozilla-and-certification-authorities/">writes</a>, &#8220;Johnathan Nightingale recently addressed a very common question, namely why <a href="http://blog.johnath.com/2008/08/05/ssl-question-corner/">Firefox doesn&#8217;t automatically accept self-signed SSL certificates as being valid</a>.  I don&#8217;t have much to add to Johnathan&#8217;s discussion of the issues with self-signed certificates, but speaking on behalf of the Mozilla Foundation I do want to address some of the comments that I&#8217;ve seen people make with regard to SSL certificates, certification authorities (CAs), and Mozilla.&#8221;  <a href="http://blog.hecker.org/2008/08/20/mozilla-and-certification-authorities/">Frank&#8217;s blog post</a> addresses some of the most common misconceptions related to Mozilla and CAs, debunking some of the more commonly repeated myths that come up in discussions on the topic.  </p>
]]></content:encoded>
			<wfw:commentRss>http://blog.mozilla.com/about_mozilla/2008/08/22/mozilla-and-certification-authorities/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>TippingPoint vulnerability patched in Firefox 3.0.1 and 2.0.0.16</title>
		<link>http://blog.mozilla.com/about_mozilla/2008/07/18/tippingpoint-vulnerability-patched-in-firefox-301-and-20016/</link>
		<comments>http://blog.mozilla.com/about_mozilla/2008/07/18/tippingpoint-vulnerability-patched-in-firefox-301-and-20016/#comments</comments>
		<pubDate>Fri, 18 Jul 2008 12:44:25 +0000</pubDate>
		<dc:creator>deb</dc:creator>
				<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://blog.mozilla.com/about_mozilla/?p=19</guid>
		<description><![CDATA[A vulnerability in the way Firefox handles CSS allows an attacker to take advantage of an integer overflow and execute arbitrary code.  In order for the attack to be successful, a user must browse to a malicious site.  The security advisory is available here.  This critical vulnerability was reported to Mozilla before [...]]]></description>
			<content:encoded><![CDATA[<p>A vulnerability in the way Firefox handles CSS allows an attacker to take advantage of an integer overflow and execute arbitrary code.  In order for the attack to be successful, a user must browse to a malicious site.  The security advisory is available <a href="http://www.mozilla.org/security/announce/2008/mfsa2008-34.html">here</a>.  This critical vulnerability was reported to Mozilla before details were available publicly.  By keeping the details of the issue private until a fix was made available, TippingPoint and Mozilla were able to minimize the risk to users.  For more information, please see the <a href="http://blog.mozilla.com/security/2008/07/16/tippingpoint-vulnerability-patched-in-firefox-301-and-20016/">Mozilla Security Blog</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.mozilla.com/about_mozilla/2008/07/18/tippingpoint-vulnerability-patched-in-firefox-301-and-20016/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
