<?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: iPhone 2.0.2 Security Flaw puts your info at risk</title>
	<atom:link href="http://www.iphonebuzz.com/iphone-202-security-flaw-puts-your-info-at-risk-274527.php/feed" rel="self" type="application/rss+xml" />
	<link>http://www.iphonebuzz.com/iphone-202-security-flaw-puts-your-info-at-risk-274527.php</link>
	<description>tracking the iPhone revolution</description>
	<lastBuildDate>Sun, 21 Mar 2010 03:14:42 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: jack parler</title>
		<link>http://www.iphonebuzz.com/iphone-202-security-flaw-puts-your-info-at-risk-274527.php/comment-page-1#comment-52655</link>
		<dc:creator>jack parler</dc:creator>
		<pubDate>Mon, 13 Apr 2009 04:18:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.iphonebuzz.com/?p=4527#comment-52655</guid>
		<description>I like this theme you are using... what is it?</description>
		<content:encoded><![CDATA[<p>I like this theme you are using&#8230; what is it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MG</title>
		<link>http://www.iphonebuzz.com/iphone-202-security-flaw-puts-your-info-at-risk-274527.php/comment-page-1#comment-34418</link>
		<dc:creator>MG</dc:creator>
		<pubDate>Thu, 28 Aug 2008 17:46:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.iphonebuzz.com/?p=4527#comment-34418</guid>
		<description>Is illustrating the flaw to the general public a very wise thing to do? I guess it may expedite a resolution from Apple, but it also gives everyone a blueprint on how to exploit the security flaw. Why not post the recipe for a dirty bomb while we&#039;re at it?</description>
		<content:encoded><![CDATA[<p>Is illustrating the flaw to the general public a very wise thing to do? I guess it may expedite a resolution from Apple, but it also gives everyone a blueprint on how to exploit the security flaw. Why not post the recipe for a dirty bomb while we&#8217;re at it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ChiefBroady</title>
		<link>http://www.iphonebuzz.com/iphone-202-security-flaw-puts-your-info-at-risk-274527.php/comment-page-1#comment-34409</link>
		<dc:creator>ChiefBroady</dc:creator>
		<pubDate>Thu, 28 Aug 2008 14:26:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.iphonebuzz.com/?p=4527#comment-34409</guid>
		<description>I agree with Rick, this is a biggy. I have a full 8 digit security code, and i could get to most of my Data with this bug, within less time than it takes me to enter the code...</description>
		<content:encoded><![CDATA[<p>I agree with Rick, this is a biggy. I have a full 8 digit security code, and i could get to most of my Data with this bug, within less time than it takes me to enter the code&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick</title>
		<link>http://www.iphonebuzz.com/iphone-202-security-flaw-puts-your-info-at-risk-274527.php/comment-page-1#comment-34356</link>
		<dc:creator>Rick</dc:creator>
		<pubDate>Wed, 27 Aug 2008 12:26:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.iphonebuzz.com/?p=4527#comment-34356</guid>
		<description>This is big... I can see several corporations rolling back iphone/exchange support until this is fixed. Corporate secure emails/data is not secure even if they have set the exchange option requiring that synchronized handsets are secured behind a pass code.</description>
		<content:encoded><![CDATA[<p>This is big&#8230; I can see several corporations rolling back iphone/exchange support until this is fixed. Corporate secure emails/data is not secure even if they have set the exchange option requiring that synchronized handsets are secured behind a pass code.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
