<?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: Secure OpenID matters to Microsoft</title>
	<atom:link href="http://scott.blomqui.st/2008/06/secure-openid-matters-to-microsoft/feed/" rel="self" type="application/rss+xml" />
	<link>http://scott.blomqui.st/2008/06/secure-openid-matters-to-microsoft/</link>
	<description>My online identity sandbox</description>
	<lastBuildDate>Tue, 12 Jan 2010 18:17:35 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: IdentityBlog - Digital Identity, Privacy, and the Internet's Missing Identity Layer</title>
		<link>http://scott.blomqui.st/2008/06/secure-openid-matters-to-microsoft/comment-page-1/#comment-73</link>
		<dc:creator>IdentityBlog - Digital Identity, Privacy, and the Internet's Missing Identity Layer</dc:creator>
		<pubDate>Tue, 24 Jun 2008 01:32:49 +0000</pubDate>
		<guid isPermaLink="false">http://scott.blomqui.st/2008/06/secure-openid-matters-to-microsoft/#comment-73</guid>
		<description>[...] been to blog about this when the feature goes live later in the week. But there&#8217;s been some online discussion already, and I&#8217;m sitting here at the horse show in waiting mode anyway, so it seems like now [...]</description>
		<content:encoded><![CDATA[<p>[...] been to blog about this when the feature goes live later in the week. But there&#8217;s been some online discussion already, and I&#8217;m sitting here at the horse show in waiting mode anyway, so it seems like now [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Klint Borozan</title>
		<link>http://scott.blomqui.st/2008/06/secure-openid-matters-to-microsoft/comment-page-1/#comment-71</link>
		<dc:creator>Klint Borozan</dc:creator>
		<pubDate>Thu, 19 Jun 2008 23:44:22 +0000</pubDate>
		<guid isPermaLink="false">http://scott.blomqui.st/2008/06/secure-openid-matters-to-microsoft/#comment-71</guid>
		<description>My challenge with this is it continues to propogate the token notion of purchasing another device you need to carry,,,,in addition to the token you have for work, etrade, paypal, fidelity, the bank, etc.  
JanRain announced a secure two factor authentication for OpenID, named CallVerifID, that uses the cell phone as a proxy for the token or the stub mentioned in the blog, and uses an out of channel authentication voice call to make it safe. Billions of phones out there alread. So, as deployment of phone based out of channel authentication proliferates for OpenID, you could use it for everything, and eliminate the little hardware gremlin from the picture.  My parents are 70 and try to keep up with security at my urging, but will mix up tokens and stubs.  But when using CallVerifID, they can follow the instructions while receiving the phone call, and remember how to use it next time.  In the case of the healthcare vertical, Doctors are the same.  They demand simplicity and things that make sense or they rebel and wont use it and demand change.  In the case of the call, once they are on the line, the doctor can press a number to even be routed someplace else, ie nursing station to check on patients as they are logged in....infinite flexibility and simplicity.  Ohio Health just implemented another version of the same and had a token burning party for 4k tokens.  The &quot;Smart Guys&quot; at Microsoft need to work with JanRain as a secure OP for Healthvault and let them bake off.  If for no other reason than just the cost and aggravation associated with managing, supporting, and selling the stub.</description>
		<content:encoded><![CDATA[<p>My challenge with this is it continues to propogate the token notion of purchasing another device you need to carry,,,,in addition to the token you have for work, etrade, paypal, fidelity, the bank, etc.<br />
JanRain announced a secure two factor authentication for OpenID, named CallVerifID, that uses the cell phone as a proxy for the token or the stub mentioned in the blog, and uses an out of channel authentication voice call to make it safe. Billions of phones out there alread. So, as deployment of phone based out of channel authentication proliferates for OpenID, you could use it for everything, and eliminate the little hardware gremlin from the picture.  My parents are 70 and try to keep up with security at my urging, but will mix up tokens and stubs.  But when using CallVerifID, they can follow the instructions while receiving the phone call, and remember how to use it next time.  In the case of the healthcare vertical, Doctors are the same.  They demand simplicity and things that make sense or they rebel and wont use it and demand change.  In the case of the call, once they are on the line, the doctor can press a number to even be routed someplace else, ie nursing station to check on patients as they are logged in&#8230;.infinite flexibility and simplicity.  Ohio Health just implemented another version of the same and had a token burning party for 4k tokens.  The &#8220;Smart Guys&#8221; at Microsoft need to work with JanRain as a secure OP for Healthvault and let them bake off.  If for no other reason than just the cost and aggravation associated with managing, supporting, and selling the stub.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Osborn</title>
		<link>http://scott.blomqui.st/2008/06/secure-openid-matters-to-microsoft/comment-page-1/#comment-70</link>
		<dc:creator>Steven Osborn</dc:creator>
		<pubDate>Thu, 19 Jun 2008 12:55:43 +0000</pubDate>
		<guid isPermaLink="false">http://scott.blomqui.st/2008/06/secure-openid-matters-to-microsoft/#comment-70</guid>
		<description>So they &#039;support&#039; OpenID as long as you choose to store your identity with the provider of their choice? Lame. I would think health care portals would be more immune to stupid stunts just to be buzzword compliant. 

OpenID was created to solve a set of problems that it cannot do until companies start trusting end users to be capable of managing their own identity.  When companies roll out OpenID like this it just makes me sad. They either don&#039;t get it or don&#039;t care and just want to be cool and slap an OpenID logo on their site.</description>
		<content:encoded><![CDATA[<p>So they &#8217;support&#8217; OpenID as long as you choose to store your identity with the provider of their choice? Lame. I would think health care portals would be more immune to stupid stunts just to be buzzword compliant. </p>
<p>OpenID was created to solve a set of problems that it cannot do until companies start trusting end users to be capable of managing their own identity.  When companies roll out OpenID like this it just makes me sad. They either don&#8217;t get it or don&#8217;t care and just want to be cool and slap an OpenID logo on their site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony B.</title>
		<link>http://scott.blomqui.st/2008/06/secure-openid-matters-to-microsoft/comment-page-1/#comment-69</link>
		<dc:creator>Tony B.</dc:creator>
		<pubDate>Thu, 19 Jun 2008 03:56:21 +0000</pubDate>
		<guid isPermaLink="false">http://scott.blomqui.st/2008/06/secure-openid-matters-to-microsoft/#comment-69</guid>
		<description>Is TrustBearer anything like ilok.com?</description>
		<content:encoded><![CDATA[<p>Is TrustBearer anything like ilok.com?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
