<?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: What Can Twitter Do About Hacking?</title>
	<atom:link href="http://www.reputationdefenderblog.com/2009/11/25/what-can-twitter-do-about-hacking/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.reputationdefenderblog.com/2009/11/25/what-can-twitter-do-about-hacking/</link>
	<description>ReputationDefender Blog &#124; Online Privacy, Online Reputation Management, Identity Management</description>
	<lastBuildDate>Wed, 10 Mar 2010 06:33:52 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Reputation Defender : Facebook Shutting Down Regional Networks, Improving Privacy Controls</title>
		<link>http://www.reputationdefenderblog.com/2009/11/25/what-can-twitter-do-about-hacking/comment-page-1/#comment-10449</link>
		<dc:creator>Reputation Defender : Facebook Shutting Down Regional Networks, Improving Privacy Controls</dc:creator>
		<pubDate>Wed, 02 Dec 2009 21:29:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.reputationdefenderblog.com/?p=1625#comment-10449</guid>
		<description>[...] for reaching the 350 million user milestone, and let us hope that other social media companies (Twitter comes to mind) show the same level of commitment to [...]</description>
		<content:encoded><![CDATA[<p>[...] for reaching the 350 million user milestone, and let us hope that other social media companies (Twitter comes to mind) show the same level of commitment to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Prefect</title>
		<link>http://www.reputationdefenderblog.com/2009/11/25/what-can-twitter-do-about-hacking/comment-page-1/#comment-10367</link>
		<dc:creator>Prefect</dc:creator>
		<pubDate>Thu, 26 Nov 2009 02:40:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.reputationdefenderblog.com/?p=1625#comment-10367</guid>
		<description>Celebrities having their Twitter accounts cracked doesn’t seem like a new problem, and indeed Britney did report herself dead via Twitter back on June 28th. But there is a difference, and that is that many of the openings for easily brute forcing the Twitter password via the web site have closed. Note I said easily, don’t spam the comments with speculation on how the account was compromised (unless its high quality speculation), we know quite well that Twitter is still far from security nirvana.

Twitter has been slowly closing loop holes in their authentication process over the course of this year. Back in September we pointed out the reCAPTCHA implementation on login that shows up when you enter too many bad authentication attempts, a key difference in the process from when the rash of prominent account break-ins occurred earlier in the year (including the notable crack of a Twitter admin’s account). Twitter has more recently started to lock out accounts for an hour when they provide too many bad passwords (a lousy idea from a security perspective, but we’ll get into that some other time).

In Breaking Twitter we showed how Twitter rate limits were not enforced as advertised in their API documentation, allowing brute force of passwords via the API. Well that hole has somewhat closed.

From:
http://praetorianprefect.com/archives/2009/11/not-the-haus-of-gaga-too/</description>
		<content:encoded><![CDATA[<p>Celebrities having their Twitter accounts cracked doesn’t seem like a new problem, and indeed Britney did report herself dead via Twitter back on June 28th. But there is a difference, and that is that many of the openings for easily brute forcing the Twitter password via the web site have closed. Note I said easily, don’t spam the comments with speculation on how the account was compromised (unless its high quality speculation), we know quite well that Twitter is still far from security nirvana.</p>
<p>Twitter has been slowly closing loop holes in their authentication process over the course of this year. Back in September we pointed out the reCAPTCHA implementation on login that shows up when you enter too many bad authentication attempts, a key difference in the process from when the rash of prominent account break-ins occurred earlier in the year (including the notable crack of a Twitter admin’s account). Twitter has more recently started to lock out accounts for an hour when they provide too many bad passwords (a lousy idea from a security perspective, but we’ll get into that some other time).</p>
<p>In Breaking Twitter we showed how Twitter rate limits were not enforced as advertised in their API documentation, allowing brute force of passwords via the API. Well that hole has somewhat closed.</p>
<p>From:<br />
<a href="http://praetorianprefect.com/archives/2009/11/not-the-haus-of-gaga-too/" rel="nofollow">http://praetorianprefect.com/archives/2009/11/not-the-haus-of-gaga-too/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
