<?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/"
		xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Four information points on Twitter phishing</title>
	<atom:link href="http://www.mckeay.net/2009/01/05/four-information-points-on-twitter-phishing/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mckeay.net/2009/01/05/four-information-points-on-twitter-phishing/</link>
	<description>The views of one man on security, privacy and anything else that catches his attention.  The views expressed on this blog do not reflect the views of my employer or anyone other than myself.</description>
	<lastBuildDate>Thu, 02 Feb 2012 21:45:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Martin</title>
		<link>http://www.mckeay.net/2009/01/05/four-information-points-on-twitter-phishing/comment-page-1/#comment-4057</link>
		<dc:creator>Martin</dc:creator>
		<pubDate>Tue, 06 Jan 2009 18:11:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.mckeay.net/2009/01/05/four-information-points-on-twitter-phishing/#comment-4057</guid>
		<description>Richard,

How about we meet half-way on this one:  Yes, it is a problem with how Twitter manages user names and passwords but it&#039;s also a problem with people putting in their information when they should know better.  There were alarms raised before this point, but maybe they weren&#039;t enough.

Martin</description>
		<content:encoded><![CDATA[<p>Richard,</p>
<p>How about we meet half-way on this one:  Yes, it is a problem with how Twitter manages user names and passwords but it&#8217;s also a problem with people putting in their information when they should know better.  There were alarms raised before this point, but maybe they weren&#8217;t enough.</p>
<p>Martin</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: stiennon</title>
		<link>http://www.mckeay.net/2009/01/05/four-information-points-on-twitter-phishing/comment-page-1/#comment-4056</link>
		<dc:creator>stiennon</dc:creator>
		<pubDate>Tue, 06 Jan 2009 17:48:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.mckeay.net/2009/01/05/four-information-points-on-twitter-phishing/#comment-4056</guid>
		<description>Yes, it *is* a Twitter problem.  No security issue should ever come down to &quot;it&#039;s the damn users&quot;.  Technology *can* solve this.  In many cases the issue is with the third parties who request credentials so they can plug into the API&#039;s.   Grader.com does not ask for your Twitter password. Neither does tweetstats.  

Twitter will solve this. They have to, or spammers will ruin their business model (such as it is.)

-Stiennon</description>
		<content:encoded><![CDATA[<p>Yes, it *is* a Twitter problem.  No security issue should ever come down to &#8220;it&#8217;s the damn users&#8221;.  Technology *can* solve this.  In many cases the issue is with the third parties who request credentials so they can plug into the API&#8217;s.   Grader.com does not ask for your Twitter password. Neither does tweetstats.  </p>
<p>Twitter will solve this. They have to, or spammers will ruin their business model (such as it is.)</p>
<p>-Stiennon</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Liquidmatrix Security Digest &#187; Security Briefing - January 6th</title>
		<link>http://www.mckeay.net/2009/01/05/four-information-points-on-twitter-phishing/comment-page-1/#comment-4053</link>
		<dc:creator>Liquidmatrix Security Digest &#187; Security Briefing - January 6th</dc:creator>
		<pubDate>Tue, 06 Jan 2009 14:28:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.mckeay.net/2009/01/05/four-information-points-on-twitter-phishing/#comment-4053</guid>
		<description>[...] Four information points on Twitter phishing - McKeay [...]</description>
		<content:encoded><![CDATA[<p>[...] Four information points on Twitter phishing &#8211; McKeay [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

