<?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: More on OpenID</title>
	<atom:link href="http://cuinnovators.com/blog/more-on-openid/feed/" rel="self" type="application/rss+xml" />
	<link>http://cuinnovators.com/blog/more-on-openid/</link>
	<description>At CU Innovators, we help credit unions, CUSO&#039;s, and service providers create meaningful products and services for their members and clients.</description>
	<lastBuildDate>Mon, 14 Mar 2011 17:53:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: James</title>
		<link>http://cuinnovators.com/blog/more-on-openid/comment-page-1/#comment-562</link>
		<dc:creator>James</dc:creator>
		<pubDate>Thu, 18 Sep 2008 16:58:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cuemployee.com/?p=282#comment-562</guid>
		<description>Hi, I found your blog on this new directory of WordPress Blogs at blackhatbootcamp.com/listofwordpressblogs.  I dont know how your blog came up, must have been a typo, i duno.  Anyways, I just clicked it and here I am.  Your blog looks good.  Have a nice day.  James.</description>
		<content:encoded><![CDATA[<p>Hi, I found your blog on this new directory of WordPress Blogs at blackhatbootcamp.com/listofwordpressblogs.  I dont know how your blog came up, must have been a typo, i duno.  Anyways, I just clicked it and here I am.  Your blog looks good.  Have a nice day.  James.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Guillaume</title>
		<link>http://cuinnovators.com/blog/more-on-openid/comment-page-1/#comment-561</link>
		<dc:creator>Guillaume</dc:creator>
		<pubDate>Mon, 08 Sep 2008 21:10:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cuemployee.com/?p=282#comment-561</guid>
		<description>I meant &quot;they are NOT the only ones that have an opportunity to do so&quot; in my previous comment.</description>
		<content:encoded><![CDATA[<p>I meant &#8220;they are NOT the only ones that have an opportunity to do so&#8221; in my previous comment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Guillaume</title>
		<link>http://cuinnovators.com/blog/more-on-openid/comment-page-1/#comment-560</link>
		<dc:creator>Guillaume</dc:creator>
		<pubDate>Mon, 08 Sep 2008 21:08:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cuemployee.com/?p=282#comment-560</guid>
		<description>While I think that providing OpenIDs is a good opportunity for FIs [1] (if they don&#039;t wait to long), they are the only ones that have an opportunity to do so. As a result, I don&#039;t think that the solution to the problem you are mentioning will be via secure bank-specific TLD.

The simplest first step is for Web sites supporting OpenID to maintain a list of OpenID providers they trust, possibly with varying degree of trust.

Note that it&#039;s not because I know for sure that you are a CU or a bank that I will trust you as an OpenID provider. I will trust you because you will provide me with information about your security that I feel the OpenIDs you issues can be trusted. Part of this can be addressed with OpenID policy extensions [2], but more likely this trust between OpenID consumers and providers will be the result of a contractual agreements involving disclosure of security procedures an related insurance arrangements.

The problem of trust lies with the consumer: (1) will a consumer feel safer login to their CU/Bank ID with their Google ID, or (2) will they feel safer login to Google via their CU/Bank ID. My guess is (2).

[1] http://lebleu.org/blog/2008/05/21/should-banks-bank-on-openid/
[2] http://openid.net/specs/openid-provider-authentication-policy-extension-1_0-01.html</description>
		<content:encoded><![CDATA[<p>While I think that providing OpenIDs is a good opportunity for FIs [1] (if they don&#8217;t wait to long), they are the only ones that have an opportunity to do so. As a result, I don&#8217;t think that the solution to the problem you are mentioning will be via secure bank-specific <acronym title="Top Level Domain">TLD</acronym>.</p>
<p>The simplest first step is for Web sites supporting OpenID to maintain a list of OpenID providers they trust, possibly with varying degree of trust.</p>
<p>Note that it&#8217;s not because I know for sure that you are a <acronym title="Credit Union">CU</acronym> or a bank that I will trust you as an OpenID provider. I will trust you because you will provide me with information about your security that I feel the OpenIDs you issues can be trusted. Part of this can be addressed with OpenID policy extensions [2], but more likely this trust between OpenID consumers and providers will be the result of a contractual agreements involving disclosure of security procedures an related insurance arrangements.</p>
<p>The problem of trust lies with the consumer: (1) will a consumer feel safer login to their <acronym title="Credit Union">CU</acronym>/Bank ID with their Google ID, or (2) will they feel safer login to Google via their <acronym title="Credit Union">CU</acronym>/Bank ID. My guess is (2).</p>
<p>[1] <a href="http://lebleu.org/blog/2008/05/21/should-banks-bank-on-openid/" rel="nofollow">http://lebleu.org/blog/2008/05/21/should-banks-bank-on-openid/</a><br />
[2] <a href="http://openid.net/specs/openid-provider-authentication-policy-extension-1_0-01.html" rel="nofollow">http://openid.net/specs/openid-provider-authentication-policy-extension-1_0-01.html</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: enhanced
Content Delivery Network via Rackspace Cloud Files: N/A

Served from: cuinnovators.com @ 2012-02-10 05:36:28 -->
