<?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"
	>
<channel>
	<title>Comments on: Possible OpenID exploit?</title>
	<atom:link href="http://blog.cristianobetta.com/2007/03/26/possible-openid-exploit/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.cristianobetta.com/2007/03/26/possible-openid-exploit/</link>
	<description></description>
	<pubDate>Sun, 12 Oct 2008 05:17:23 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: alistair_uk</title>
		<link>http://blog.cristianobetta.com/2007/03/26/possible-openid-exploit/#comment-58</link>
		<dc:creator>alistair_uk</dc:creator>
		<pubDate>Wed, 28 Mar 2007 18:44:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cristianobetta.com/2007/03/26/possible-openid-exploit/#comment-58</guid>
		<description>This will not actually work unless you can redirect both the client and web server machines to the malicious OpenID server.

If memory serve me corectly OpenID can function in two ways.

1) The best is when the web server contacts the OpenID server and that agree on a secret to encrypt there communication by. Although the communication is via the client without the secret (that only the web server and OpenID server knows) you can not get the evil OpenID server to pretend to be the good one.

2) The other solution is where the details are passed between the OpenID and web servers via the client unencrypted. When this happens the web server should ask the OpenID server directly if what it received from the client is true.

You might have noticed that in both these scenarios the web server contacts the OpenID server in a way that bypasses the client completely so the server can not be spoofed.

...so in summary it is not actually problem at all, provided the person implementing the web site does not take any stupid short cuts and miss out part of the communication to save some coding time. With library available for most platforms there really is not need to take these shortcuts.</description>
		<content:encoded><![CDATA[<p>This will not actually work unless you can redirect both the client and web server machines to the malicious OpenID server.</p>
<p>If memory serve me corectly OpenID can function in two ways.</p>
<p>1) The best is when the web server contacts the OpenID server and that agree on a secret to encrypt there communication by. Although the communication is via the client without the secret (that only the web server and OpenID server knows) you can not get the evil OpenID server to pretend to be the good one.</p>
<p>2) The other solution is where the details are passed between the OpenID and web servers via the client unencrypted. When this happens the web server should ask the OpenID server directly if what it received from the client is true.</p>
<p>You might have noticed that in both these scenarios the web server contacts the OpenID server in a way that bypasses the client completely so the server can not be spoofed.</p>
<p>&#8230;so in summary it is not actually problem at all, provided the person implementing the web site does not take any stupid short cuts and miss out part of the communication to save some coding time. With library available for most platforms there really is not need to take these shortcuts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cristiano Gerard Betta</title>
		<link>http://blog.cristianobetta.com/2007/03/26/possible-openid-exploit/#comment-57</link>
		<dc:creator>Cristiano Gerard Betta</dc:creator>
		<pubDate>Tue, 27 Mar 2007 01:23:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cristianobetta.com/2007/03/26/possible-openid-exploit/#comment-57</guid>
		<description>Ok, I gave my theory a quick run by making a fake entry that routes alper.nl to localhost. Somehow though I never see the browser linking to that page but directly to Alper's true provider http://myopenid.com. I suspect that the OpenID protocol get's this first step at the server side.

After this I tried to make a fake entry to the myopenid site, but that didn't really help because another redirect is not possible. The solution I think is to run a "free" server that gives a valid response anytime, and then link the dns entry in the hosts file for myopenid to that server.

This is more work and will have to try that later.</description>
		<content:encoded><![CDATA[<p>Ok, I gave my theory a quick run by making a fake entry that routes alper.nl to localhost. Somehow though I never see the browser linking to that page but directly to Alper&#8217;s true provider <a href="http://myopenid.com" rel="nofollow">http://myopenid.com</a>. I suspect that the OpenID protocol get&#8217;s this first step at the server side.</p>
<p>After this I tried to make a fake entry to the myopenid site, but that didn&#8217;t really help because another redirect is not possible. The solution I think is to run a &#8220;free&#8221; server that gives a valid response anytime, and then link the dns entry in the hosts file for myopenid to that server.</p>
<p>This is more work and will have to try that later.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cristiano Gerard Betta</title>
		<link>http://blog.cristianobetta.com/2007/03/26/possible-openid-exploit/#comment-56</link>
		<dc:creator>Cristiano Gerard Betta</dc:creator>
		<pubDate>Tue, 27 Mar 2007 00:39:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cristianobetta.com/2007/03/26/possible-openid-exploit/#comment-56</guid>
		<description>I think I will try it in a couple of weeks. Wednesday I leave for the Netherlands, so I have to try it either tommorow or when I get back.</description>
		<content:encoded><![CDATA[<p>I think I will try it in a couple of weeks. Wednesday I leave for the Netherlands, so I have to try it either tommorow or when I get back.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan W</title>
		<link>http://blog.cristianobetta.com/2007/03/26/possible-openid-exploit/#comment-55</link>
		<dc:creator>Dan W</dc:creator>
		<pubDate>Mon, 26 Mar 2007 19:10:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cristianobetta.com/2007/03/26/possible-openid-exploit/#comment-55</guid>
		<description>If you can't find an answer give the exploit a try to see</description>
		<content:encoded><![CDATA[<p>If you can&#8217;t find an answer give the exploit a try to see</p>
]]></content:encoded>
	</item>
</channel>
</rss>
