<?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: OpenID and Phishing: Episode II</title>
	<atom:link href="http://www.links.org/?feed=rss2&#038;p=188" rel="self" type="application/rss+xml" />
	<link>http://www.links.org/?p=188</link>
	<description>Ben Laurie blathering</description>
	<lastBuildDate>Thu, 12 Apr 2012 15:49:36 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: The problem(s) with OpenID &#171; The Identity Corner</title>
		<link>http://www.links.org/?p=188&#038;cpage=1#comment-129394</link>
		<dc:creator>The problem(s) with OpenID &#171; The Identity Corner</dc:creator>
		<pubDate>Mon, 11 Feb 2008 00:31:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.links.org/?p=188#comment-129394</guid>
		<description>[...] spoofing and ID theft - we need severe crypto, locked down, secure ID systems.&#8221; Ben Laurie elaborates as follows: &#8220;The OpenID fanboys want OpenID to work on any old platform using only standard software, [...]</description>
		<content:encoded><![CDATA[<p>[...] spoofing and ID theft &#8211; we need severe crypto, locked down, secure ID systems.&#8221; Ben Laurie elaborates as follows: &#8220;The OpenID fanboys want OpenID to work on any old platform using only standard software, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2007-10-30 &#171; Spartakan</title>
		<link>http://www.links.org/?p=188&#038;cpage=1#comment-87452</link>
		<dc:creator>links for 2007-10-30 &#171; Spartakan</dc:creator>
		<pubDate>Tue, 30 Oct 2007 04:26:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.links.org/?p=188#comment-87452</guid>
		<description>[...] Links » OpenID and Phishing Ben Laurie&#8217;s criticisms of openIDs security model, and responses dealt with (tags: identity security blog 2007) [...]</description>
		<content:encoded><![CDATA[<p>[...] Links » OpenID and Phishing Ben Laurie&#8217;s criticisms of openIDs security model, and responses dealt with (tags: identity security blog 2007) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: OpenID sucks. &#171; Outside the Bubble&#8230;</title>
		<link>http://www.links.org/?p=188&#038;cpage=1#comment-83780</link>
		<dc:creator>OpenID sucks. &#171; Outside the Bubble&#8230;</dc:creator>
		<pubDate>Fri, 19 Oct 2007 19:15:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.links.org/?p=188#comment-83780</guid>
		<description>[...] OpenID and Phishing: Episode 2 [...]</description>
		<content:encoded><![CDATA[<p>[...] OpenID and Phishing: Episode 2 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Identity Corner &#187; The problem(s) with OpenID</title>
		<link>http://www.links.org/?p=188&#038;cpage=1#comment-68527</link>
		<dc:creator>The Identity Corner &#187; The problem(s) with OpenID</dc:creator>
		<pubDate>Wed, 22 Aug 2007 22:30:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.links.org/?p=188#comment-68527</guid>
		<description>[...] In sum, OpenID adds up to little more than simple password management with extra overhead and lots of security problems. As Marc Canter stresses: &#8220;if we’re to stop phishing, and spoofing and ID theft - we need severe crypto, locked down, secure ID systems.&#8221; Ben Laurie elaborates as follows: &#8220;The OpenID fanboys want OpenID to work on any old platform using only standard software, and so therefore are doomed to live in the world of broken authentication. This is fine if what you protect with your OpenID is worthless, but it seems clear that these types of protocol are going to be used to authenticate for things of value. […] This is the root of the problem: if you want to protect anything of value, you have to do better than existing Web solutions. You need better client-side software. […] the best general way to handle this problem is through zero-knowledge proofs.&#8221; (Note: this is exactly what Credentica’s technology does.) [...]</description>
		<content:encoded><![CDATA[<p>[...] In sum, OpenID adds up to little more than simple password management with extra overhead and lots of security problems. As Marc Canter stresses: &#8220;if we’re to stop phishing, and spoofing and ID theft &#8211; we need severe crypto, locked down, secure ID systems.&#8221; Ben Laurie elaborates as follows: &#8220;The OpenID fanboys want OpenID to work on any old platform using only standard software, and so therefore are doomed to live in the world of broken authentication. This is fine if what you protect with your OpenID is worthless, but it seems clear that these types of protocol are going to be used to authenticate for things of value. […] This is the root of the problem: if you want to protect anything of value, you have to do better than existing Web solutions. You need better client-side software. […] the best general way to handle this problem is through zero-knowledge proofs.&#8221; (Note: this is exactly what Credentica’s technology does.) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Barrett</title>
		<link>http://www.links.org/?p=188&#038;cpage=1#comment-16658</link>
		<dc:creator>Michael Barrett</dc:creator>
		<pubDate>Fri, 02 Mar 2007 17:30:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.links.org/?p=188#comment-16658</guid>
		<description>I am more or less convinced - and admittedly I am highly biased - that OpenID is unlikely to get into serious usage for anything commercially sensitive.  There are already a slew of protocols (SAML 2.0 / Liberty ID-FF, WS-*, Cardspace, Higgins, Shib, blah) that deal with most of the issues much more robustly.  

If the trust issues that you raise here are not addressed by OpenID, then it seems most unlikely that it will achieve significant &quot;real world&quot; deployment.</description>
		<content:encoded><![CDATA[<p>I am more or less convinced &#8211; and admittedly I am highly biased &#8211; that OpenID is unlikely to get into serious usage for anything commercially sensitive.  There are already a slew of protocols (SAML 2.0 / Liberty ID-FF, WS-*, Cardspace, Higgins, Shib, blah) that deal with most of the issues much more robustly.  </p>
<p>If the trust issues that you raise here are not addressed by OpenID, then it seems most unlikely that it will achieve significant &#8220;real world&#8221; deployment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kim Cameron&#8217;s Identity Weblog &#187; Can browser-based plugins solve the phishing problem?</title>
		<link>http://www.links.org/?p=188&#038;cpage=1#comment-13247</link>
		<dc:creator>Kim Cameron&#8217;s Identity Weblog &#187; Can browser-based plugins solve the phishing problem?</dc:creator>
		<pubDate>Mon, 12 Feb 2007 05:31:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.links.org/?p=188#comment-13247</guid>
		<description>[...] Dready&#8217;s right about the research.  But rather than calling it a &#8220;social problem&#8221; I&#8217;d call it a &#8220;social engineering attack&#8221;.  Further, there is a protocol problem.  The protocol is based on telling the RP where the OP is located - such that an evil site can automate a &#8220;man in the middle attack&#8221;.  Some other protocols, including the one used by CardSpace, do NOT have this problem.  That&#8217;s why combining CardSpace and OpenID is useful.  Numerous ideas to mitigate phishing attacks have been floating around the OpenID list and on the OpenID mini-blogsphere. Ben Laurie argues for a client-side solution:  Authentication on the web is broken, and has been for a long time. The OpenID fanboys want OpenID to work on any old platform using only standard software, and so therefore are doomed to live in the world of broken authentication. This is fine if what you protect with your OpenID is worthless, but it seems clear that these types of protocol are going to be used to authenticate for things of value. [...]</description>
		<content:encoded><![CDATA[<p>[...] Dready&#8217;s right about the research.  But rather than calling it a &#8220;social problem&#8221; I&#8217;d call it a &#8220;social engineering attack&#8221;.  Further, there is a protocol problem.  The protocol is based on telling the RP where the OP is located - such that an evil site can automate a &#8220;man in the middle attack&#8221;.  Some other protocols, including the one used by CardSpace, do NOT have this problem.  That&#8217;s why combining CardSpace and OpenID is useful.  Numerous ideas to mitigate phishing attacks have been floating around the OpenID list and on the OpenID mini-blogsphere. Ben Laurie argues for a client-side solution:  Authentication on the web is broken, and has been for a long time. The OpenID fanboys want OpenID to work on any old platform using only standard software, and so therefore are doomed to live in the world of broken authentication. This is fine if what you protect with your OpenID is worthless, but it seems clear that these types of protocol are going to be used to authenticate for things of value. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dready blog v2.0 &#187; Blog Archive &#187; Browser-based mitigation of phishing attacks</title>
		<link>http://www.links.org/?p=188&#038;cpage=1#comment-11248</link>
		<dc:creator>dready blog v2.0 &#187; Blog Archive &#187; Browser-based mitigation of phishing attacks</dc:creator>
		<pubDate>Sun, 21 Jan 2007 17:59:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.links.org/?p=188#comment-11248</guid>
		<description>[...] Numerous ideas to mitigate phishing attacks have been floating around the OpenID list and on the OpenID mini-blogsphere. Ben Laurie argues for a client-side solution:  Authentication on the web is broken, and has been for a long time. The OpenID fanboys want OpenID to work on any old platform using only standard software, and so therefore are doomed to live in the world of broken authentication. This is fine if what you protect with your OpenID is worthless, but it seems clear that these types of protocol are going to be used to authenticate for things of value. [...]</description>
		<content:encoded><![CDATA[<p>[...] Numerous ideas to mitigate phishing attacks have been floating around the OpenID list and on the OpenID mini-blogsphere. Ben Laurie argues for a client-side solution:  Authentication on the web is broken, and has been for a long time. The OpenID fanboys want OpenID to work on any old platform using only standard software, and so therefore are doomed to live in the world of broken authentication. This is fine if what you protect with your OpenID is worthless, but it seems clear that these types of protocol are going to be used to authenticate for things of value. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Krishna</title>
		<link>http://www.links.org/?p=188&#038;cpage=1#comment-11231</link>
		<dc:creator>Krishna</dc:creator>
		<pubDate>Sun, 21 Jan 2007 12:54:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.links.org/?p=188#comment-11231</guid>
		<description>How does adding zero-knowledge proofs to the spec address the phishing problem?</description>
		<content:encoded><![CDATA[<p>How does adding zero-knowledge proofs to the spec address the phishing problem?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kim Cameron&#8217;s Identity Weblog &#187; Ben Laurie explains the &#8220;Kittens&#8221; phishing attack.</title>
		<link>http://www.links.org/?p=188&#038;cpage=1#comment-11195</link>
		<dc:creator>Kim Cameron&#8217;s Identity Weblog &#187; Ben Laurie explains the &#8220;Kittens&#8221; phishing attack.</dc:creator>
		<pubDate>Sun, 21 Jan 2007 02:12:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.links.org/?p=188#comment-11195</guid>
		<description>[...] Like me, Ben was struck with how readily the system currently lends itself to automation of phishing attacks.  His second post on the subject is interesting. [...]</description>
		<content:encoded><![CDATA[<p>[...] Like me, Ben was struck with how readily the system currently lends itself to automation of phishing attacks.  His second post on the subject is interesting. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: identity 2.0 / Phishing w OpenID</title>
		<link>http://www.links.org/?p=188&#038;cpage=1#comment-11171</link>
		<dc:creator>identity 2.0 / Phishing w OpenID</dc:creator>
		<pubDate>Sat, 20 Jan 2007 23:10:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.links.org/?p=188#comment-11171</guid>
		<description>[...] Problem phishingu w OpenID jest bardzo poważny i nikt nie zamierza tego negować. Ben Laurie napisał na ten temat dwa ciekawe wpisy, w pierwszym z nich dość prowokacyjnie stwierdza, że OpenID jest rajem dla phisherów. I trudno odmówić mu niestety racji. [...]</description>
		<content:encoded><![CDATA[<p>[...] Problem phishingu w OpenID jest bardzo poważny i nikt nie zamierza tego negować. Ben Laurie napisał na ten temat dwa ciekawe wpisy, w pierwszym z nich dość prowokacyjnie stwierdza, że OpenID jest rajem dla phisherów. I trudno odmówić mu niestety racji. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

