<?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>Twitter Bulletin &#187; hack</title>
	<atom:link href="http://www.twitterbulletin.com/tag/hack/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.twitterbulletin.com</link>
	<description>Your daily dose of twitter</description>
	<lastBuildDate>Wed, 14 Apr 2010 17:00:31 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>A Month Of Twitter Bugs</title>
		<link>http://www.twitterbulletin.com/2009/07/01/a-month-of-twitter-bugs/</link>
		<comments>http://www.twitterbulletin.com/2009/07/01/a-month-of-twitter-bugs/#comments</comments>
		<pubDate>Wed, 01 Jul 2009 02:39:13 +0000</pubDate>
		<dc:creator>Chris Brandrick</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[api]]></category>
		<category><![CDATA[hack]]></category>
		<category><![CDATA[password]]></category>
		<category><![CDATA[twitpwn]]></category>
		<category><![CDATA[vulnerability]]></category>

		<guid isPermaLink="false">http://www.twitterbulletin.com/?p=167</guid>
		<description><![CDATA[A word of warning, when using Twitter this month, be it on the web or via your favorite app just be careful not to give your details away. The guys over at Twitpwn have declared July to be the &#8216;Month of Twitter Bugs&#8216;, but according to them they do not intend harm, they just have [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: left; margin-right: 10px; padding-top: 14px;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.twitterbulletin.com%2F2009%2F07%2F01%2Fa-month-of-twitter-bugs%2F"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.twitterbulletin.com%2F2009%2F07%2F01%2Fa-month-of-twitter-bugs%2F" height="61" width="51" /></a></div><p>A word of <strong>warning</strong>, when using Twitter this month, be it on the web or via your favorite app just be careful not to give your details away. The guys over at <a title="Twitpwn" href="http://twitpwn.com/" target="_blank">Twitpwn</a> have declared July to be the &#8216;<em>Month of Twitter Bugs</em>&#8216;, but according to them they do not intend harm, they just have a desire to expose vulnerabilities with current systems in order to force them to be fixed, they also claim they will give warnings, read on to see what they said in full:</p>
<blockquote><p>I’ve decided to declare July 2009 as “Month of Twitter Bugs” (MoTB). I’m doing so in order to raise the awareness of the Twitter API issue I recently <a href="http://aviv.raffon.net/2009/05/18/CrossWeb20Scripting.aspx" target="_blank">blogged about</a>. MoTB could have been easily converted to any other “Month of Web2.0 service bugs”, and I hope that Twitter and other Web2.0 API providers will work closely with their API consumers to develop more secure products.</p>
<p>Each day I will publish a new vulnerability in a 3rd party Twitter service on the <a href="http://twitpwn.com/" target="_blank">twitpwn.com</a><a id="KonaLink2" class="kLink" style="text-decoration: underline ! important; position: static;" href="http://edge.i-hacked.com/july-1st-is-twittersec-day#" target="undefined"></a> web site. As those vulnerabilities can be exploited to create a Twitter worm, I’m going to give the 3rd party service provider<a id="KonaLink3" class="kLink" style="text-decoration: underline ! important; position: static;" href="http://edge.i-hacked.com/july-1st-is-twittersec-day#" target="undefined"></a><span style="color: green;"> </span>and Twitter at-least 24 hours heads-up before I publish the vulnerability.</p></blockquote>
<p>So while it may sound harmless enough (if developers take notice of warnings) we do recomend to <strong><em>change your password</em></strong>, just in case.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.twitterbulletin.com/2009/07/01/a-month-of-twitter-bugs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

