<?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: Google Account Consolidation – Real World Security Concerns – An Involuntary Case&#160;Study</title>
	<atom:link href="http://www.searchenginejournal.com/google-account-consolidation-%e2%80%93-real-world-security-concerns-%e2%80%93-an-involuntary-case-study/6244/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.searchenginejournal.com/google-account-consolidation-%e2%80%93-real-world-security-concerns-%e2%80%93-an-involuntary-case-study/6244/</link>
	<description></description>
	<lastBuildDate>Wed, 15 Feb 2012 00:21:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Winooski</title>
		<link>http://www.searchenginejournal.com/google-account-consolidation-%e2%80%93-real-world-security-concerns-%e2%80%93-an-involuntary-case-study/6244/comment-page-1/#comment-876335</link>
		<dc:creator>Winooski</dc:creator>
		<pubDate>Thu, 17 Jan 2008 17:32:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginejournal.com/google-account-consolidation-%e2%80%93-real-world-security-concerns-%e2%80%93-an-involuntary-case-study/6244/#comment-876335</guid>
		<description>What a frightening story! I&#039;m happy to hear that it was resolved, though sorry to hear it took a not-insignificant amount of effort.

What really caught my eye, though, is the fact that this story is appearing at the same time as Yahoo! announcing that it&#039;s joining the OpenID initiative (see http://searchengineland.com/080117-082924.php ). If ever there was evidence that a universal login is not a good idea, Carsten&#039;s &quot;case study&quot; is it.</description>
		<content:encoded><![CDATA[<p>What a frightening story! I&#8217;m happy to hear that it was resolved, though sorry to hear it took a not-insignificant amount of effort.</p>
<p>What really caught my eye, though, is the fact that this story is appearing at the same time as Yahoo! announcing that it&#8217;s joining the OpenID initiative (see <a href="http://searchengineland.com/080117-082924.php" rel="nofollow">http://searchengineland.com/080117-082924.php</a> ). If ever there was evidence that a universal login is not a good idea, Carsten&#8217;s &#8220;case study&#8221; is it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CarstenCumbrowski</title>
		<link>http://www.searchenginejournal.com/google-account-consolidation-%e2%80%93-real-world-security-concerns-%e2%80%93-an-involuntary-case-study/6244/comment-page-1/#comment-872722</link>
		<dc:creator>CarstenCumbrowski</dc:creator>
		<pubDate>Wed, 16 Jan 2008 04:57:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginejournal.com/google-account-consolidation-%e2%80%93-real-world-security-concerns-%e2%80%93-an-involuntary-case-study/6244/#comment-872722</guid>
		<description>Hi Oliver, 

that Google is not a figurehead when it comes to customer service is known and I also have to give them credit that they realized it themselves and work on improving on that.

Customer service is one thing and security another though. Those things should probably not even be handled by the same department. 

The reporting of a security breach to customer service should raise a red flag and trigger the involvement of the security department and taken very serious. Time works for the attacker who was able to break into the system. 

Not responding to such threats is irresponsible. 

To make a real-life comparison,  an ill response like demonstrated in my case in case of a 911 call that reports that a robbery is currently in process could result into people getting hurt or killed, not to mention that it is harder to find the robber, after the fact than it is while the robbery is still in progress.</description>
		<content:encoded><![CDATA[<p>Hi Oliver, </p>
<p>that Google is not a figurehead when it comes to customer service is known and I also have to give them credit that they realized it themselves and work on improving on that.</p>
<p>Customer service is one thing and security another though. Those things should probably not even be handled by the same department. </p>
<p>The reporting of a security breach to customer service should raise a red flag and trigger the involvement of the security department and taken very serious. Time works for the attacker who was able to break into the system. </p>
<p>Not responding to such threats is irresponsible. </p>
<p>To make a real-life comparison,  an ill response like demonstrated in my case in case of a 911 call that reports that a robbery is currently in process could result into people getting hurt or killed, not to mention that it is harder to find the robber, after the fact than it is while the robbery is still in progress.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oliver Taco</title>
		<link>http://www.searchenginejournal.com/google-account-consolidation-%e2%80%93-real-world-security-concerns-%e2%80%93-an-involuntary-case-study/6244/comment-page-1/#comment-872659</link>
		<dc:creator>Oliver Taco</dc:creator>
		<pubDate>Wed, 16 Jan 2008 04:17:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginejournal.com/google-account-consolidation-%e2%80%93-real-world-security-concerns-%e2%80%93-an-involuntary-case-study/6244/#comment-872659</guid>
		<description>I&#039;m amazed you found a human being.  I have NEVER had such bad support for paid services as I have at google.

Ok, Sears, once, on a fridge rebate.

But that is not very good company, is it?

-OT</description>
		<content:encoded><![CDATA[<p>I&#8217;m amazed you found a human being.  I have NEVER had such bad support for paid services as I have at google.</p>
<p>Ok, Sears, once, on a fridge rebate.</p>
<p>But that is not very good company, is it?</p>
<p>-OT</p>
]]></content:encoded>
	</item>
</channel>
</rss>

