<?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:go='http://ns.gigaom.com/'
xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Updated: Many Unknowns In Twitter Document Breach</title>
	<atom:link href="http://gigaom.com/2009/07/15/many-unknowns-in-twitter-document-breach/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2009/07/15/many-unknowns-in-twitter-document-breach/</link>
	<description></description>
	<lastBuildDate>Sat, 11 Feb 2012 00:50:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Twitter: How to Increase Yor Followers on Auto-Pilot and Make Sure Cheaters are Caught</title>
		<link>http://gigaom.com/2009/07/15/many-unknowns-in-twitter-document-breach/#comment-217717</link>
		<dc:creator><![CDATA[Twitter: How to Increase Yor Followers on Auto-Pilot and Make Sure Cheaters are Caught]]></dc:creator>
		<pubDate>Mon, 20 Jul 2009 02:47:06 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=59023#comment-217717</guid>
		<description><![CDATA[[...] Updated: Many Unknowns In Twitter Document Breach [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Updated: Many Unknowns In Twitter Document Breach [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard</title>
		<link>http://gigaom.com/2009/07/15/many-unknowns-in-twitter-document-breach/#comment-217716</link>
		<dc:creator><![CDATA[Richard]]></dc:creator>
		<pubDate>Fri, 17 Jul 2009 16:18:37 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=59023#comment-217716</guid>
		<description><![CDATA[Passwords aren&#039;t really enough to keep confidential data secure in the cloud.  Just like traditional VPN access, companies that are serious about security should require use of two-factor authentication - a password known by the user, AND a randomly-changing number generated by a hardware token.  In fact this is what my company uses for employees needing web access from outside the firewall to the internally-hosted corporate email.

I don&#039;t know if Google Apps offers this, but it really needs it to make a dent in the corporate market.]]></description>
		<content:encoded><![CDATA[<p>Passwords aren&#8217;t really enough to keep confidential data secure in the cloud.  Just like traditional VPN access, companies that are serious about security should require use of two-factor authentication &#8211; a password known by the user, AND a randomly-changing number generated by a hardware token.  In fact this is what my company uses for employees needing web access from outside the firewall to the internally-hosted corporate email.</p>
<p>I don&#8217;t know if Google Apps offers this, but it really needs it to make a dent in the corporate market.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A.j</title>
		<link>http://gigaom.com/2009/07/15/many-unknowns-in-twitter-document-breach/#comment-217715</link>
		<dc:creator><![CDATA[A.j]]></dc:creator>
		<pubDate>Thu, 16 Jul 2009 22:51:03 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=59023#comment-217715</guid>
		<description><![CDATA[Apprarently Evan Williams did not give techcrunch the go ahead on publishing the documents :
http://twitter.com/ev/status/2676203744]]></description>
		<content:encoded><![CDATA[<p>Apprarently Evan Williams did not give techcrunch the go ahead on publishing the documents :<br />
<blockquote class='twitter-tweet'>@<a href="https://twitter.com/TechCrunch">TechCrunch</a> @<a href="https://twitter.com/arrington">arrington</a> &quot;we have been given the green light by Twitter to post this information&quot; What?! By whom? That&#039;s not our understanding&mdash; <br />Evan Williams (@ev) <a href='http://twitter.com/#!/ev/status/2676203744' data-datetime='2009-07-16T21:07:09+00:00'>July 16, 2009</a></p></blockquote>
]]></content:encoded>
	</item>
	<item>
		<title>By: Griffon</title>
		<link>http://gigaom.com/2009/07/15/many-unknowns-in-twitter-document-breach/#comment-217714</link>
		<dc:creator><![CDATA[Griffon]]></dc:creator>
		<pubDate>Thu, 16 Jul 2009 04:10:10 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=59023#comment-217714</guid>
		<description><![CDATA[Yeah... I kind of wish that techcrunch had taken a pass.... these are not smoking gun documents that the release of  can be seen to serve the public good, even in some offhand way. There is a world of difference printing a little ink around what one get&#039;s from some inside contacts over lunch and useing stuff burgled in this fashion, and the techcrunch line about news is what they don&#039;t want you to print... blahblah just dose not hold up IMO. The whole thing is so valley wag, in the worst possible way. Ah well, so the valley turns... I&#039;m going to do my best to tune the rest of this out.]]></description>
		<content:encoded><![CDATA[<p>Yeah&#8230; I kind of wish that techcrunch had taken a pass&#8230;. these are not smoking gun documents that the release of  can be seen to serve the public good, even in some offhand way. There is a world of difference printing a little ink around what one get&#8217;s from some inside contacts over lunch and useing stuff burgled in this fashion, and the techcrunch line about news is what they don&#8217;t want you to print&#8230; blahblah just dose not hold up IMO. The whole thing is so valley wag, in the worst possible way. Ah well, so the valley turns&#8230; I&#8217;m going to do my best to tune the rest of this out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Security Breach At Twitter; Twitter Plans To Be The 1st Internet Service To Reach 1 BILLION Users! &#124; TechDusts</title>
		<link>http://gigaom.com/2009/07/15/many-unknowns-in-twitter-document-breach/#comment-217713</link>
		<dc:creator><![CDATA[Security Breach At Twitter; Twitter Plans To Be The 1st Internet Service To Reach 1 BILLION Users! &#124; TechDusts]]></dc:creator>
		<pubDate>Wed, 15 Jul 2009 20:38:47 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=59023#comment-217713</guid>
		<description><![CDATA[[...] GIGAOM : Many Unknowns In Twitter Document Breach by Jordan Golson [...]]]></description>
		<content:encoded><![CDATA[<p>[...] GIGAOM : Many Unknowns In Twitter Document Breach by Jordan Golson [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: courtney benson</title>
		<link>http://gigaom.com/2009/07/15/many-unknowns-in-twitter-document-breach/#comment-217712</link>
		<dc:creator><![CDATA[courtney benson]]></dc:creator>
		<pubDate>Wed, 15 Jul 2009 20:28:58 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=59023#comment-217712</guid>
		<description><![CDATA[Some of the docs have already shown up on Techcrunch.  From my perspective far to many companies including many Fortune 2000 types don&#039;t pay enough attention to security issues. This is one of the reasons we hear so much about breaches after the fact. I think Twitter will all the publicity should have expected the possibility of an event and hired someone - outsourced or otherwise to provide the troops with do&#039;s and don&#039;t and to tighten up logical security systems.]]></description>
		<content:encoded><![CDATA[<p>Some of the docs have already shown up on Techcrunch.  From my perspective far to many companies including many Fortune 2000 types don&#8217;t pay enough attention to security issues. This is one of the reasons we hear so much about breaches after the fact. I think Twitter will all the publicity should have expected the possibility of an event and hired someone &#8211; outsourced or otherwise to provide the troops with do&#8217;s and don&#8217;t and to tighten up logical security systems.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jamie Lin</title>
		<link>http://gigaom.com/2009/07/15/many-unknowns-in-twitter-document-breach/#comment-217711</link>
		<dc:creator><![CDATA[Jamie Lin]]></dc:creator>
		<pubDate>Wed, 15 Jul 2009 19:27:14 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=59023#comment-217711</guid>
		<description><![CDATA[Though I hate to say this, I have to agree with Arrington on this particular issue and he should indeed post the documents.  Here are my thoughts:
http://linjamie.com/2009/07/15/why-michael-arrington-should-post-twitter-docs/]]></description>
		<content:encoded><![CDATA[<p>Though I hate to say this, I have to agree with Arrington on this particular issue and he should indeed post the documents.  Here are my thoughts:<br />
<a href="http://linjamie.com/2009/07/15/why-michael-arrington-should-post-twitter-docs/" rel="nofollow">http://linjamie.com/2009/07/15/why-michael-arrington-should-post-twitter-docs/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jamie</title>
		<link>http://gigaom.com/2009/07/15/many-unknowns-in-twitter-document-breach/#comment-217710</link>
		<dc:creator><![CDATA[Jamie]]></dc:creator>
		<pubDate>Wed, 15 Jul 2009 19:19:15 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=59023#comment-217710</guid>
		<description><![CDATA[Twitter&#039;s confirmation that the breach occured kinda makes that particular conspiracy theory a non-starter, no?]]></description>
		<content:encoded><![CDATA[<p>Twitter&#8217;s confirmation that the breach occured kinda makes that particular conspiracy theory a non-starter, no?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: إختراق تويتر...مرة آخرى!! &#124; تيدوز</title>
		<link>http://gigaom.com/2009/07/15/many-unknowns-in-twitter-document-breach/#comment-217709</link>
		<dc:creator><![CDATA[إختراق تويتر...مرة آخرى!! &#124; تيدوز]]></dc:creator>
		<pubDate>Wed, 15 Jul 2009 19:12:52 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=59023#comment-217709</guid>
		<description><![CDATA[[...] [ GigaOM [...]]]></description>
		<content:encoded><![CDATA[<p>[...] [ GigaOM [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jordan Golson</title>
		<link>http://gigaom.com/2009/07/15/many-unknowns-in-twitter-document-breach/#comment-217708</link>
		<dc:creator><![CDATA[Jordan Golson]]></dc:creator>
		<pubDate>Wed, 15 Jul 2009 18:48:06 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=59023#comment-217708</guid>
		<description><![CDATA[Yes, that&#039;s true -- and one of the major trade-offs of the cloud.

&quot;Physical access is access,&quot; as the saying goes. With the cloud, you (and everyone else) has &quot;physical&quot; access from anywhere. Sort of.]]></description>
		<content:encoded><![CDATA[<p>Yes, that&#8217;s true &#8212; and one of the major trade-offs of the cloud.</p>
<p>&#8220;Physical access is access,&#8221; as the saying goes. With the cloud, you (and everyone else) has &#8220;physical&#8221; access from anywhere. Sort of.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Krishna Santani</title>
		<link>http://gigaom.com/2009/07/15/many-unknowns-in-twitter-document-breach/#comment-217707</link>
		<dc:creator><![CDATA[Krishna Santani]]></dc:creator>
		<pubDate>Wed, 15 Jul 2009 17:58:02 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=59023#comment-217707</guid>
		<description><![CDATA[You can&#039;t rely on third party applications like google doc for keeping up your confidential documents.  I also think this whole episode is fabricated by Arrignton who is always interested in spreading rumors and creating controversies in order to gain some mileage.]]></description>
		<content:encoded><![CDATA[<p>You can&#8217;t rely on third party applications like google doc for keeping up your confidential documents.  I also think this whole episode is fabricated by Arrignton who is always interested in spreading rumors and creating controversies in order to gain some mileage.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WD</title>
		<link>http://gigaom.com/2009/07/15/many-unknowns-in-twitter-document-breach/#comment-217706</link>
		<dc:creator><![CDATA[WD]]></dc:creator>
		<pubDate>Wed, 15 Jul 2009 17:49:31 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=59023#comment-217706</guid>
		<description><![CDATA[&gt;I suspect it comes down to poor data handling and security on Twitter’s part, and weak password reset protocols on the part of Google — not some fundamental weakness of the “cloud.”

But part of the Twitter weakness was having documents outside the domain of their control, and hence, that is part of the fundamental weakness of the &#039;cloud&#039;.]]></description>
		<content:encoded><![CDATA[<p>&gt;I suspect it comes down to poor data handling and security on Twitter’s part, and weak password reset protocols on the part of Google — not some fundamental weakness of the “cloud.”</p>
<p>But part of the Twitter weakness was having documents outside the domain of their control, and hence, that is part of the fundamental weakness of the &#8216;cloud&#8217;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

