<?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>hubflanger &#187; security</title>
	<atom:link href="http://hubflanger.com/tag/security/feed/" rel="self" type="application/rss+xml" />
	<link>http://hubflanger.com</link>
	<description>adventures in code</description>
	<lastBuildDate>Mon, 29 Mar 2010 22:41:12 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<atom:link rel='hub' href='http://hubflanger.com/?pushpress=hub'/>
		<item>
		<title>iPhone and Social Networking security concerns</title>
		<link>http://hubflanger.com/iphone-and-social-networking-security-concerns/</link>
		<comments>http://hubflanger.com/iphone-and-social-networking-security-concerns/#comments</comments>
		<pubDate>Mon, 11 Aug 2008 02:53:14 +0000</pubDate>
		<dc:creator>Peng</dc:creator>
				<category><![CDATA[iPhone]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[Social Networking]]></category>
		<category><![CDATA[Twitter]]></category>

		<guid isPermaLink="false">http://hubflanger.com/iphone-and-social-networking-security-concerns/</guid>
		<description><![CDATA[Today, while I was updating my passwords on a few of my social network profiles, I came across a serious security hole found in many of these services. During the course of the day, most of us are likely to rely on various devices such as mobile phones and desktop computers, to update our statuses [...]]]></description>
			<content:encoded><![CDATA[<p>Today, while I was updating my passwords on a few of my social network profiles, I came across a serious security hole found in many of these services. During the course of the day, most of us are likely to rely on various devices such as mobile phones and desktop computers, to update our statuses on our social network profiles. When one uses a client such as Safari on the iPhone, or the web browser on a Blackberry, one&#8217;s login info is often cached on the browser. After I changed my Twitter password using the web browser on my Mac, I discovered that I was able to pull up my Twitter profile on my iPhone&#8217;s Safari browser and proceed to update my status successfully, all without being prompted to login again using my new password.<span id="more-77"></span></p>
<p>I then tested a couple of other popular services such as HelloTxt and Ping.fm by changing my passwords using Safari on my Mac. Both these sites also allowed me to update my status through my cached profile pages on iPhone/Safari without any user authentication. What&#8217;s the big deal here? Well, for one thing, should your mobile device fall into the wrong hands, whoever it is will have unbridled access to your social profile(s) and assume your online identity. </p>
<p>Many of these sites also allow you to update your status vis SMS or Email. Any person in possession of your device can easily attempt a malicious act by texting or emailing status updates, masquerading as YOU. And since no password is ever required to SMS or Email, your security is equally compromised as rendered by the cached pages on the web browser.</p>
<p>Native apps such as Twitterific on the iPhone fair slightly better as the startup process involves actual login authentication, so changing your password is actually effective in blocking unauthorized access. But what good is that when there are so many other loopholes one can exploit?</p>
<p>With these security concerns in mind, &#8220;remote-wipe&#8221; would be a welcome feature indeed.</p>
]]></content:encoded>
			<wfw:commentRss>http://hubflanger.com/iphone-and-social-networking-security-concerns/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
