<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" 
      xmlns:thr="http://purl.org/syndication/thread/1.0">
  <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php" />
  <link rel="self" type="application/atom+xml" href="http://www.readwriteweb.com/atom.xml" />
  <id>tag:,2008:/1/tag:72.47.210.69,2007://1.5239-</id>
  <updated>2008-07-07T14:33:36Z</updated>
  <title>Comments for OpenID and the Identity Systems of Yahoo, Google &amp; MSN</title>
  
  <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.1</generator>
  <entry>
    <id>tag:72.47.210.69,2007://1.5239</id>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.readwriteweb.com/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=5239" title="OpenID and the Identity Systems of Yahoo, Google &amp; MSN" />
    <published>2007-01-04T03:01:28Z</published>
    <updated>2007-12-16T23:16:41Z</updated>
    <title>OpenID and the Identity Systems of Yahoo, Google &amp; MSN</title>
    <summary>Written by Emre Sokullu and edited by Richard MacManus You may&apos;ve heard of OpenID - it&apos;s a distributed identity management system, a.k.a. a decentralized single sign-on platform. We prepared a screencast to better explain the idea (see Flash movie below). After that we present a more detailed explanation, focusing particularly on Yahoo and Google. In...</summary>
    <author>
      <name>Emre Sokullu</name>
      
    </author>
    
    <category term="Web Design" />
    
    <content type="html" xml:lang="en" xml:base="http://www.readwriteweb.com/">
      <![CDATA[<p><i>Written by Emre Sokullu and edited by Richard MacManus</i></p>

<p><img border="0" src="http://www.readwriteweb.com/images/openid_bigcos.jpg" width="496"
height="175" /></p>

<p>You may've heard of <a href="http://openid.org" title="OpenID">OpenID</a> - it's a
distributed identity management system, a.k.a. a decentralized single sign-on platform.
We prepared a screencast to better explain the idea (see Flash movie below). After that
we present a more detailed explanation, focusing particularly on Yahoo and Google.</p>

<p>In the screencast we use a real world example to show you what OpenID is. Firstly we
create an OpenID account at one of the best known free OpenID servers, <a
href="http://myopenid.com" title="myopenid.com">myopenid.com</a>, then we use our new
account to sign in to the following supported sites: Grou.ps, Zooomr and WikiTravel. Note
that we could use any OpenID provider, like <a href="http://clamid.com"
title="ClaimID">ClaimID</a> or <a href="http://videntity.org"
title="vIdentity">vIdentity</a>, but for the sake of simplicity we've chosen only one.
Here's the screencast:</p>]]>
      <![CDATA[<p><OBJECT CLASSID="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" WIDTH="450" HEIGHT="340" CODEBASE="http://active.macromedia.com/flash5/cabs/swflash.cab#version=5,0,0,0">
<PARAM NAME=movie VALUE="openid.swf">
<PARAM NAME=play VALUE=true>
<PARAM NAME=loop VALUE=false>
<PARAM NAME=quality VALUE=low>
<EMBED SRC="http://www.archive.org/download/OpenID_Screencast/openid.swf" WIDTH=450 HEIGHT=340 quality=low loop=false TYPE="application/x-shockwave-flash" PLUGINSPAGE="http://www.macromedia.com/shockwave/download/index.cgi?P1_Prod_Version=ShockwaveFlash">
</EMBED>
</OBJECT><br />
Note: click the play button to start
</p>

<p>As indicated in the screencast, OpenID saves you from the hassles of creating and
managing new identities for various web app. But it works both ways - service providers
also save time and money by outsourcing their user identity management to this reliable
and neutral network.</p>

<h2>Single Sign-On and The Big Internet Companies</h2>

<p>The big idea in OpenID is providing a decentralized single sign-on platform. Single
sign-on is not a new notion however. Almost all the internet giants, like Yahoo, Google
and MSN, use single sign-on across their properties to lower the threshold of accessing
their services and to create a competitive advantage. The reason they do this is that
signing up is actually a big barrier to entry for users of web apps. Users feel more
comfortable when they don't have to sign up to use an app - it's much easier to give it a
try and it's less time-consuming to start using it. That's why most web sites today try
to keep sign up process as short as possible. Here's a graph which illustrates this:</p>

<p><img src="/images/oid_graph.png" style="HEIGHT:205px; WIDTH:292px" /></p>

<p>From this point of view, OpenID can be seen to resemble Yahoo - the biggest single
sign-on strategy player in the history of the Internet. In the late nineties, Yahoo's
strategy was to create a big portal and make their properties seamlessly accessible via
single sign-on. This could also be called Yahoo's sub-internet - and it worked too for a
while. But then Google came along and swept up everything with a whole new search-centric
approach. In Google's new paradigm, search was the key - but single sign-on was still
used. With Froogle or Google Book Search for example, they could compete with Amazon in
the book sales arena.</p>

<p>Although Google's approach seems more successful now, and the other bigcos have
adopted the search-centric model, single sign-on is still a very important paradigm.
Therefore OpenID can provide the advantages that Google, Yahoo and MSN have, to all other
independent sites - in a decentralized, open fashion.</p>

<h2>A Brief History Of Sign-On Approaches</h2>

<table border="1" cellpadding="3" cellspacing="0" width="515">
<tr>
<td>1994</td>
<td><b>Yahoo</b> Initiates Single Sign-On Paradigm; Company Foundation</td>
</tr>

<tr>
<td>1998</td>
<td><b>MSN</b> Starts its own Single Sign-On Paradigm; Announcement of MSN Passport</td>
</tr>

<tr>
<td>1998</td>
<td><b>Google</b> Initiates Search-Centric Paradigm; Company Foundation</td>
</tr>

<tr>
<td>2002</td>
<td><b>Yahoo</b> Follows up with Search-Centric Paradigm; Acquisition of Inktomi</td>
</tr>

<tr>
<td>2004</td>
<td><b>Google</b> Starts its own Single Sign-On Paradigm; Gmail and Google Accounts</td>
</tr>

<tr>
<td>2004 -2005</td>
<td><b>MSN</b> Follows up with Search-Centric Paradigm; Live.com</td>
</tr>

<tr>
<td>2005</td>
<td><b>OpenID</b> Initiates single sign-on for independent sites; Project Foundation</td>
</tr>
</table><br />

<h2>Origins of OpenID</h2>

<p><a href="http://openid.net/">OpenID</a> was the brainchild of Brad Fitzpatrick, who is
also known for <a href="http://www.danga.com/memcached/">memcached</a> and <a
href="http://www.livejournal.com/">LiveJournal</a> - the popular blogging platform which
was acquired by Six Apart in 2005. Today, OpenID is backed by Six Apart and several
others including VeriSign. Commercial support is the biggest reason for OpenID's
existence and growth. Similar to the RSS effect, OpenID creates many business
opportunities around it. <a href="http://claimid.com/">ClaimID</a> is one of the best
known commercial OpenID providers, whose business model can be compared to
FeedBurner.</p>

<p>OpenID is being managed under meritocracy rules, just like any other big open source
project. Specs are under continuous development. The current spec 1.1 will be deprecated
in favor of the upcoming 2.0, which will feature YADIS service discovery, security
enhancements, anonymous logging capability and XRI (i-name i-number).</p>

<h2>Current Status</h2>

<p>The number of sites that implement OpenID is low for the time being. <a
href="http://zooomr.com">Zooomr</a> is known to rely solely on the OpenID identity
management system. However, many others like <a href="http://grou.ps">Grou.ps</a> (my
company) and <a href="http://wikitravel.org/">WikiTravel</a> are more conservative and
choose to offer OpenID as an option, besides the traditional sign-on model.&nbsp;</p>

<p>Brad Fitzpatrick's LiveJournal is one of the largest OpenID supporting sites, however
it is used only to add comments and not create a fully functional account. Recently
Technorati was invited to initiate OpenID support, however their support is limited to a
few functionalities only - similar to LiveJournal.&nbsp;</p>

<p>OpenID advocates have tried to attract Yahoo and Google for support, but this does not
sound feasible because of the business models established on their proprietary single
sign-on mechanisms. Wikipedia, however, is expected to support OpenID soon - thanks to a
patch created for WikiMedia, the open source wiki software powering the encyclopedia
giant.</p>

<p>As for general OpenID usage, it's impossible to have accurate information on that - as
the system is decentralized. However, the number is certainly not at a satisfactory level
yet, but is expected to gain momentum as of version 2.0 which has greater stability and
will get better media coverage.</p>

<h2>Concerns</h2>

<p>Even though the system is completely decentralized, OpenID still raises privacy
concerns. Some people don't want to have a central place that binds all their accounts.
Another criticism is whether the system is <i>fully</i> de-centralized? As always, this
space is vulnerable to one provider eventually dominating it. So any disequilibria may
put the neutrality of the system under question.</p>]]>
    </content>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.5239-comment:41751</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.5239" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php#c41751" />
    <title>Comment from Chris Matthieu on 2007-01-03</title>
    <author>
        <name>Chris Matthieu</name>
        <uri>http://numly.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://numly.com">
        <![CDATA[<p>Check out the latest Identity 2.0 service from Numly called <a href="http://vouchor.com" rel="nofollow">Vouchor.com</a>.  This service consists of a network of people that have had their real-world identities vouched by others in person.  In addition to establishing someone's real identity online, Vouchor has just unveiled a karma reputation engine as well as a single sign-on (SSO) solution.  Each vouched person is assigned a Vouchor ID which is truly a 19 digit Numly Number.  The SSO API can be called and the Vouchor ID passed along with the user entered password and a boolean true or false is returned to the calling application along with basic meta data about the vouchor.</p>

<p>This establishes:</p>

<p>1) Universal SSO<br />
2) Real-world identity<br />
3) Open reputation</p>

<p>Let me know what you think!</p>]]>
    </content>
    <published>2007-01-04T03:33:08Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.5239-comment:41752</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.5239" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php#c41752" />
    <title>Comment from Terrell Russell on 2007-01-03</title>
    <author>
        <name>Terrell Russell</name>
        <uri>http://weblog.terrellrussell.com/</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://weblog.terrellrussell.com/">
        <![CDATA[<p>Thanks for the links, Chris.</p>

<p>We are planning on bigger things for 2007.  OpenID is a big part of the awakening of identity management by and for individuals.</p>

<p>Terrell<br />
<a href="http://claimID.com" rel="nofollow"><a href="http://claimID.com" rel="nofollow">http://claimID.com</a></a></p>]]>
    </content>
    <published>2007-01-04T04:42:57Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.5239-comment:41753</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.5239" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php#c41753" />
    <title>Comment from Terrell Russell on 2007-01-03</title>
    <author>
        <name>Terrell Russell</name>
        <uri>http://weblog.terrellrussell.com/</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://weblog.terrellrussell.com/">
        <![CDATA[<p>And by Chris, I mean, Emre.</p>]]>
    </content>
    <published>2007-01-04T04:43:57Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.5239-comment:41754</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.5239" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php#c41754" />
    <title>Comment from John Milan on 2007-01-03</title>
    <author>
        <name>John Milan</name>
        <uri>http://intelligantt.blogspot.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://intelligantt.blogspot.com">
        <![CDATA[<p>How would OpenID work with the recent announcement regarding Microformats in Firefox? As I understand it, id information could just as easily be stored in Firefox's Microformat database. Is there a tangible difference if someone authenticates using OpenID versus stored Microformat data via your browser?</p>

<p>Perhaps if I need to hop from machine to machine, but then the question is which approach addresses the mainstream. Without seeing numbers, my guess would be the browser based Microformat database.</p>]]>
    </content>
    <published>2007-01-04T05:01:23Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.5239-comment:41755</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.5239" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php#c41755" />
    <title>Comment from aaron on 2007-01-03</title>
    <author>
        <name>aaron</name>
        <uri>http://charisma18.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://charisma18.com">
        <![CDATA[<p>The privacy/security issue you note isn't with OpenID itself - it's with the OpenID host.  You can always host your own identity.</p>]]>
    </content>
    <published>2007-01-04T05:33:56Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.5239-comment:41756</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.5239" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php#c41756" />
    <title>Comment from Jason on 2007-01-03</title>
    <author>
        <name>Jason</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>"Wikipedia, however, is expected to support OpenID soon - thanks to a patch created for WikiMedia, the open source wiki software powering the encyclopedia giant."</p>

<p>The patch is created for MediaWiki, the actual software.<br />
WikiMedia (the foundation/developers) is planning on rolling out the patch to their MediaWiki software as well as to all their Wiki sites (Wiktionary, WikiPedia, etc.).</p>

<p>Please make note that it matters which one you reference :-).</p>

<p>Also, shame on you. You and every one who touts OpenID, but doesn't allow curious visitors to actually try it on your own site. ;-)</p>

<p>There is a consumer for MT already, officially by SixApart no less.</p>

<p>By the way, Chris;<br />
Vouchor is a stupid concept that is doing nothing but re-inventing the wheel. We already have vouching for identity/security services. It's call SSL and GPG.<br />
Not to mention that both are insanely more supported than some new upstart that introduces nothing new when trying to penetrate the market.<br />
Also, identifying (and undescriptive) numbers should be dead, seeing as ICQ is more or less already.</p>

<p>I apologize if that sounded harsh, but I see the concept as fundamentally stupid given the popular and active technologies we already have.</p>]]>
    </content>
    <published>2007-01-04T07:41:35Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.5239-comment:41757</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.5239" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php#c41757" />
    <title>Comment from old school developer on 2007-01-04</title>
    <author>
        <name>old school developer</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>And one more (mature) identity authentication service that was notably absent from the article and subsequent discussion -- inames.net (http://inames.net/) which is based upon the XRI Open Standards (http://www.xdi.org/).</p>

<p>This article could have used more thorough research.</p>]]>
    </content>
    <published>2007-01-04T08:08:20Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.5239-comment:41758</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.5239" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php#c41758" />
    <title>Comment from Emre Sokullu on 2007-01-04</title>
    <author>
        <name>Emre Sokullu</name>
        <uri>http://emresokullu.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://emresokullu.com">
        <![CDATA[<p>Jason, I didn't get some of your points. But first let me correct this, yes this was a typo, not WikiMedia but MediaWiki or whatever, we know that it's the software that powers Wikipedia. But Wikipedia is subject to use OpenID as well, there are some discussions going on - <a href="http://iwantmyopenid.org/node/12" rel="nofollow"><a href="http://iwantmyopenid.org/node/12" rel="nofollow">http://iwantmyopenid.org/node/12</a></a></p>

<p>MT? You mean MovableType or what?</p>]]>
    </content>
    <published>2007-01-04T08:26:35Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.5239-comment:41759</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.5239" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php#c41759" />
    <title>Comment from Tijs Teulings on 2007-01-04</title>
    <author>
        <name>Tijs Teulings</name>
        <uri>http://blog.tijs.org/</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://blog.tijs.org/">
        <![CDATA[<p>I think the risks of one party dominating the openID space are negligable since it's very easy to host your own openID server . Furthermore you could use your own domain as your openID login and have it delegate authentication to any openID provider you want. When your unhappy with it just switch providers while your id remains the same.</p>]]>
    </content>
    <published>2007-01-04T08:43:07Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.5239-comment:41760</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.5239" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php#c41760" />
    <title>Comment from Jason on 2007-01-04</title>
    <author>
        <name>Jason</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>Yes, I meant MovableType.<br />
There are OpenID consumers for commenters, yet you aren't using one.</p>

<p>I'm always amused when someone speaks about a technology, yet doesn't offer visitors to use it.<br />
Yes, there are other big name sites (LJ, Zooomr, schtuff, etc.) they can use it with, but it's that whole adoption thing, showing off that you support it by actually supporting it in your projects, or ones you assist with (i.e. this blog).</p>

<p>I suppose if you are (speaking generally, not YOU yourself, Emre) were just an editor or some kind of content producer, and not a technical director or CIO or similar, then you'd have no say in it.</p>

<p>But hey, it's 1:45AM and I'm rambling and feel like I'll be misunderstood left and right.<br />
Hopefully some sense and clarification came from this.</p>

<p>All I'm getting at is:<br />
I don't want to enter my name.<br />
I don't want to enter my e-mail address (required! but not shown to the world!).<br />
I don't want to enter my URL.</p>

<p>I want to enter my OpenID, have some magical profile exchange whizbang done for me transparently (barring clicking a "send my information to readwriteweb.com" approval, of course), and be done with it.</p>]]>
    </content>
    <published>2007-01-04T08:50:08Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.5239-comment:41761</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.5239" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php#c41761" />
    <title>Comment from Emre Sokullu on 2007-01-04</title>
    <author>
        <name>Emre Sokullu</name>
        <uri>http://emresokullu.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://emresokullu.com">
        <![CDATA[<p>@Tijs, but who would care that? For me, there's no problem, personally, I'd trust those who dominate as I trust Google, but there would be question marks I think as in the case of Google.</p>]]>
    </content>
    <published>2007-01-04T08:56:37Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.5239-comment:41762</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.5239" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php#c41762" />
    <title>Comment from Sriram Krishnan on 2007-01-04</title>
    <author>
        <name>Sriram Krishnan</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>What about Windows Cardspace and all the identity work from Kim Cameron? I have no idea how that got missed out from this writeup when talking about Microsoft and identity</p>]]>
    </content>
    <published>2007-01-04T10:14:24Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.5239-comment:41763</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.5239" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php#c41763" />
    <title>Comment from Emre Sokullu on 2007-01-04</title>
    <author>
        <name>Emre Sokullu</name>
        <uri>http://emresokullu.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://emresokullu.com">
        <![CDATA[<p>@Sriram: This is rather about single sign on systems - from this perspective, I call OpenID as OpenYahoo</p>]]>
    </content>
    <published>2007-01-04T10:35:46Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.5239-comment:41764</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.5239" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php#c41764" />
    <title>Comment from Richard MacManus on 2007-01-04</title>
    <author>
        <name>Richard MacManus</name>
        <uri>http://www.readwriteweb.com/</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.readwriteweb.com/">
        <![CDATA[<p>Jason, thanks for the suggestion! I will look into this for R/WW, which does indeed use MT.</p>]]>
    </content>
    <published>2007-01-04T10:56:46Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.5239-comment:41765</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.5239" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php#c41765" />
    <title>Comment from Ed Eliot on 2007-01-04</title>
    <author>
        <name>Ed Eliot</name>
        <uri>http://www.ejeliot.com/</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.ejeliot.com/">
        <![CDATA[<p>Also available, but not mentioned here, is Yahoo!s relatively new BBAuth (http://developer.yahoo.com/auth/) service which allows people to use their Yahoo! ID with 3rd party sites - similar in use to Open ID.</p>]]>
    </content>
    <published>2007-01-04T12:48:59Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.5239-comment:41766</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.5239" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php#c41766" />
    <title>Comment from Eric on 2007-01-04</title>
    <author>
        <name>Eric</name>
        <uri>http://thegreateric.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://thegreateric.com">
        <![CDATA[<p>Maybe I'm missing something about the way this is implemented, but doesn't this seem especially prone to phishing attacks?</p>

<p>For example, in the case of Google - I have my "GoogleID" which I use on any www.google.com page. If I find myself on a page www.phishingpage.com and it's asking for my GoogleID, I know something is wrong and I won't enter it. (Ditto for Yahoo, MSN, etc.</p>

<p>With "One ID to rule them all", any one-man web 2.0 company can start legitimately asking for your OpenID account information; the same account information I'd be using to log on to Gmail, for example.</p>

<p>What am I missing here, what protection does OpenID offer against this?</p>]]>
    </content>
    <published>2007-01-04T13:54:17Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.5239-comment:41767</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.5239" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php#c41767" />
    <title>Comment from Terrell Russell on 2007-01-04</title>
    <author>
        <name>Terrell Russell</name>
        <uri>http://weblog.terrellrussell.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://weblog.terrellrussell.com">
        <![CDATA[<p>Eric,</p>

<p>It is the OpenID server's responsibility to smooth the waters for its users an get them used to looking at something personalized (to fight phishing).</p>

<p>The PIP server at VeriSign already does this (and is opensource code underneath) - <a href="http://pip.verisignlabs.com/" rel="nofollow"><a href="http://pip.verisignlabs.com/" rel="nofollow">http://pip.verisignlabs.com/</a></a> - code at - <a href="http://svn.apache.org/repos/asf/incubator/heraldry/idp/pip/trunk/" rel="nofollow"><a href="http://svn.apache.org/repos/asf/incubator/heraldry/idp/pip/trunk/" rel="nofollow">http://svn.apache.org/repos/asf/incubator/heraldry/idp/pip/trunk/</a></a> - housed under the Heraldry project at the Apache foundation.</p>

<p>Upon creation of an account on a PIP server, you are asked to upload a unique personal image that is displayed whenever you return to that server.  It is hard to phish that site since any illegitimate server that looks the same as your home OpenID server would not have that unique uploaded image (only resident in your *real* account).</p>

<p>So yes, this is an issue, but can be effectively dealt with on the server side with some education and expectation setting by the server itself.</p>

<p>Terrell</p>]]>
    </content>
    <published>2007-01-04T14:36:20Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.5239-comment:41768</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.5239" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php#c41768" />
    <title>Comment from seobaby on 2007-01-04</title>
    <author>
        <name>seobaby</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>Thanks for the analysys:-) <br />
btw there's a typo in ClaimID url.</p>]]>
    </content>
    <published>2007-01-04T14:45:11Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.5239-comment:41769</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.5239" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php#c41769" />
    <title>Comment from Dave on 2007-01-04</title>
    <author>
        <name>Dave</name>
        <uri>http://www.steelsphere.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.steelsphere.com">
        <![CDATA[<p>"Here's a graph that illustrates this"</p>

<p>ROFLAMO</p>

<p>I'm going to start designing arbitrary charts of my own too!  Not that I disagree with your premise or the content of the article at all, I just laugh when I see things written as if there is hard data behind information without any references what-so-ever.  I'd be really interested to know which group commissioned and performed the study that generated that graph.</p>]]>
    </content>
    <published>2007-01-04T14:51:25Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.5239-comment:41770</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.5239" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php#c41770" />
    <title>Comment from Thomas Rynne on 2007-01-04</title>
    <author>
        <name>Thomas Rynne</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>If I understand correctly, the way it works is that<br />
www.phishingpage.com ask for your openid url.<br />
Then they redirect you to www.google.com and where you enter your account information, and then google.com redirect you back to www.phishingpage.com.</p>]]>
    </content>
    <published>2007-01-04T15:43:18Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.5239-comment:41771</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.5239" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php#c41771" />
    <title>Comment from itsdex on 2007-01-04</title>
    <author>
        <name>itsdex</name>
        <uri>http://itsdex.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://itsdex.com">
        <![CDATA[<p>Eric, it's not prone to phishing attacks.  We're completing BBAuth yahoo and openid integration for a couple of properties now.  In the case of BBAuth, you bounce out to a Yahoo! page, authenticate, then your site is passed a  user hash and from that the user can start building their profile on your site.  It's just authenticating that they have a valid account with Yahoo!, we don't actually get access to their Yahoo! services, and the user doesn't have to create a new account.</p>

<p>So in your phishing example the site could then allow you to login to their site, but they never get access to your credentials required to read your yahoo mail or  gmail account.    The annoying part about Yahoo! is it expires in 2 weeks so you have that same round trip as far as we can tell to authenticate.</p>

<p>Back to when Microsoft acquired Firefly out of MIT, they set forth on the path of delivering universal authentication.  Unfortunately, it got buried under Microsoftness keep it in their camp, to the point they even had sites needing to certify that they had enough microsoft servers behind the scenes to use the passport.  </p>

<p>The Yahoo! user base is so large that it's highly appealing, and not impossible to add authentication across all three (openid, bbauth/yahoo, google) to make it as easy as possible for people to try your webservice.</p>]]>
    </content>
    <published>2007-01-04T17:15:57Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.5239-comment:41772</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.5239" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php#c41772" />
    <title>Comment from joy on 2007-01-04</title>
    <author>
        <name>joy</name>
        <uri>http://cleverhack.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://cleverhack.com">
        <![CDATA[<p>I can think of a disincentive for providers to use an open sign on technology - what about the fact that businesses consider their membership information to be valuable to them? </p>

<p>For example, MSN is now offering advertisers the ability for advertisers to target towards specific demographics. Those demographics are proprietary to MSN. </p>

<p>In addition, I can think of other uses of membership information...advertising rate cards, list rentals and even behavioral targeting.</p>]]>
    </content>
    <published>2007-01-04T17:48:00Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.5239-comment:41773</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.5239" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php#c41773" />
    <title>Comment from Nigel Parker on 2007-01-04</title>
    <author>
        <name>Nigel Parker</name>
        <uri>http://blogs.msdn.com/nigel</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://blogs.msdn.com/nigel">
        <![CDATA[<p>Sirim wrote "What about Windows Cardspace and all the identity work from Kim Cameron? I have no idea how that got missed out from this writeup when talking about Microsoft and identity".</p>

<p>The great thing about CardSpace is that it is based on the WS * standard so it can be implemented cross platform. Different to passport there is no centralised identity third party that you need to trust to use the service. CardSpace works with the new High Assurance SSL certificates <a href="http://www.verisign.com/ssl/ssl-information-center/faq/high-assurance-ssl.html." rel="nofollow"><a href="http://www.verisign.com/ssl/ssl-information-center/faq/high-assurance-ssl.html." rel="nofollow">http://www.verisign.com/ssl/ssl-information-center/faq/high-assurance-ssl.html.</a></a></p>

<p>I have had a bit of experience working with CardSpace, infact I did a podcast on it here <a href="http://msdev.thepodcastnetwork.com/audio/tpn_msdev_20061110_009.mp3" rel="nofollow"><a href="http://msdev.thepodcastnetwork.com/audio/tpn_msdev_20061110_009.mp3" rel="nofollow">http://msdev.thepodcastnetwork.com/audio/tpn_msdev_20061110_009.mp3</a></a> If you are interested in the community site for CardSpace it is at <a href="http://cardspace.netfx3.com" rel="nofollow"><a href="http://cardspace.netfx3.com" rel="nofollow">http://cardspace.netfx3.com</a></a> also Kim's work can be found at <a href="http://identityblog.com." rel="nofollow"><a href="http://identityblog.com." rel="nofollow">http://identityblog.com.</a></a> The Windows Live ID and Passport team is developing a security token service (STS) that supports CardSpace for single sign on.</p>

<p>With the advent of Windows Vista and .NET 3.0, CardSpace makes secure certificates accessible to all consumers in an intuative and secure way. Support for CardSpace in other OS's and on mobile devices is on it's way.</p>]]>
    </content>
    <published>2007-01-04T19:17:10Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.5239-comment:41774</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.5239" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php#c41774" />
    <title>Comment from Emre Sokullu on 2007-01-04</title>
    <author>
        <name>Emre Sokullu</name>
        <uri>http://emresokullu.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://emresokullu.com">
        <![CDATA[<p>@Ed you're right Google also has some sort of open Google accounts. I've totally forgot them, they could really make into this article.</p>]]>
    </content>
    <published>2007-01-04T19:27:54Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.5239-comment:41775</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.5239" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php#c41775" />
    <title>Comment from Stoicho on 2007-01-05</title>
    <author>
        <name>Stoicho</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>I get the OpenID idea. It is good, if not great. But!</p>

<p>Let‚Äôs say you have an online application. You provide OpenID logging. How can you trust a 3rd party sees how frequent your users logged in, how many users your application has? I went through the privacy policy of MyOpenID, ClaimID or vIdentity - they dont cover any of these concernse.</p>

<p>I will eventually trust any of theses if they have put on their *first* page with *big* letters:</p>

<p>WE WILL NEVER EVER NEVER EVER GATHER ANY INFORMATION, REGARTHLESS HOW MANY, OR HOW FREQUENT YOUR APPLICATION USERS USED THEIR OPENID ACCOUNTS.</p>]]>
    </content>
    <published>2007-01-05T21:24:10Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.5239-comment:41776</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.5239" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php#c41776" />
    <title>Comment from Julian on 2007-01-08</title>
    <author>
        <name>Julian</name>
        <uri>http://blog.julianonsoftware.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://blog.julianonsoftware.com">
        <![CDATA[<p>Great post as usual Richard -- I think the more support out of the box popular packages for OpenID, the more likely it'll become established. I'm certainly sick of registering again and again, even if it provides some resilience and is fairly quick. I see that there's a Wordpress plug-in for OpenID: I think this sort of thing should be included out of the box definitely:</p>

<p><a href="http://blog.scatmania.org/archives/2005/08/06/openid-for-wordpress/" rel="nofollow"><a href="http://blog.scatmania.org/archives/2005/08/06/openid-for-wordpress/" rel="nofollow">http://blog.scatmania.org/archives/2005/08/06/openid-for-wordpress/</a></a></p>]]>
    </content>
    <published>2007-01-08T13:25:28Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.5239-comment:41777</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.5239" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php#c41777" />
    <title>Comment from Atomic1fire on 2007-01-12</title>
    <author>
        <name>Atomic1fire</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>Even if some provider does run the risk of being in control<br />
you still have the little guys that can use the same service<br />
unlike some little known net identity service against MSN<br />
they all use the same id through openid so even if ones widely used theres still alternatives using the same service so its all compatible in the end</p>]]>
    </content>
    <published>2007-01-13T00:05:09Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.5239-comment:41778</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.5239" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/openid_vs_bigco.php#c41778" />
    <title>Comment from George on 2007-01-28</title>
    <author>
        <name>George</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>So, OpenID is (very) basically a foreign cookie verification. Looks like I'm gonna build on top of this, however my web apps will allow for multiple open-ids per account. However:</p>

<p>"The current spec 1.1 will be deprecated in favor of the upcoming 2.0"</p>

<p>Deprecated? After a year or two in operation? I think newborn technologies should try to evolve without deprecation every other year...</p>

<p>Also, a nice OpendID feature would be to standardize to always have the "Enter your URL" box use the same HTML ID on each website - I think that's how browsers offer the auto-completion thingy - but I'm not sure.</p>]]>
    </content>
    <published>2007-01-28T16:51:32Z</published>
  </entry>

</feed>