<?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: Investigating Google&#8217;s Security Breach</title>
	<atom:link href="http://blog.alertsec.com/2010/01/investigating-googles-security-breach/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.alertsec.com/2010/01/investigating-googles-security-breach/</link>
	<description></description>
	<lastBuildDate>Sun, 30 Oct 2011 06:12:22 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Security Updates are Signs of Insecurity &#124; Alertsec Xpress Data Security Blog</title>
		<link>http://blog.alertsec.com/2010/01/investigating-googles-security-breach/comment-page-1/#comment-5644</link>
		<dc:creator>Security Updates are Signs of Insecurity &#124; Alertsec Xpress Data Security Blog</dc:creator>
		<pubDate>Mon, 22 Feb 2010 04:11:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.alertsec.com/?p=378#comment-5644</guid>
		<description>[...] security patch is developed only after an exploit is discovered by a cyber intruder. For example, Google&#8217;s infamous security breach revealed fatal coding errors in Microsoft&#8217;s Internet Explorer browser. In response, Microsoft [...]</description>
		<content:encoded><![CDATA[<p>[...] security patch is developed only after an exploit is discovered by a cyber intruder. For example, Google&#8217;s infamous security breach revealed fatal coding errors in Microsoft&#8217;s Internet Explorer browser. In response, Microsoft [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

