<?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: Twitter Vulnerability History</title>
	<atom:link href="http://blogsecurity.net/social-networking/twitter-vulnerability-history/feed" rel="self" type="application/rss+xml" />
	<link>http://blogsecurity.net/social-networking/twitter-vulnerability-history</link>
	<description>Always something worth reading...</description>
	<lastBuildDate>Fri, 12 Mar 2010 11:09:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Twitter Web Worm Causes Havoc</title>
		<link>http://blogsecurity.net/social-networking/twitter-vulnerability-history/comment-page-1#comment-16376</link>
		<dc:creator>Twitter Web Worm Causes Havoc</dc:creator>
		<pubDate>Tue, 14 Apr 2009 15:40:39 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/?p=444#comment-16376</guid>
		<description>[...] Well it looks like we can add this to our recent Twiiter vulnerability history post. [...]</description>
		<content:encoded><![CDATA[<p>[...] Well it looks like we can add this to our recent Twiiter vulnerability history post. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Serj</title>
		<link>http://blogsecurity.net/social-networking/twitter-vulnerability-history/comment-page-1#comment-16294</link>
		<dc:creator>Serj</dc:creator>
		<pubDate>Sat, 21 Mar 2009 09:22:05 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/?p=444#comment-16294</guid>
		<description>Need to change your password every month and everything will be fine</description>
		<content:encoded><![CDATA[<p>Need to change your password every month and everything will be fine</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hiroshi</title>
		<link>http://blogsecurity.net/social-networking/twitter-vulnerability-history/comment-page-1#comment-16177</link>
		<dc:creator>hiroshi</dc:creator>
		<pubDate>Sun, 22 Feb 2009 17:52:28 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/?p=444#comment-16177</guid>
		<description>Very good article. Thanks. I just changed my twitter password again.</description>
		<content:encoded><![CDATA[<p>Very good article. Thanks. I just changed my twitter password again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chung Bey Luen</title>
		<link>http://blogsecurity.net/social-networking/twitter-vulnerability-history/comment-page-1#comment-16152</link>
		<dc:creator>Chung Bey Luen</dc:creator>
		<pubDate>Wed, 18 Feb 2009 17:31:53 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/?p=444#comment-16152</guid>
		<description>I also noticed that Twitter has been getting into serious security issue since 2008. I believe Twitter should invest to make it more secure, at least making us feel safe.</description>
		<content:encoded><![CDATA[<p>I also noticed that Twitter has been getting into serious security issue since 2008. I believe Twitter should invest to make it more secure, at least making us feel safe.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Twitter and Security &#124; der-eremit.de</title>
		<link>http://blogsecurity.net/social-networking/twitter-vulnerability-history/comment-page-1#comment-16143</link>
		<dc:creator>Twitter and Security &#124; der-eremit.de</dc:creator>
		<pubDate>Tue, 17 Feb 2009 21:27:32 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/?p=444#comment-16143</guid>
		<description>[...] Luckily David Kierznowski of blogsecurity.net already did so and so I&#8217;m pleased to refer you to his article: Twitter Vulnerability History [...]</description>
		<content:encoded><![CDATA[<p>[...] Luckily David Kierznowski of blogsecurity.net already did so and so I&#8217;m pleased to refer you to his article: Twitter Vulnerability History [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
