<?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: A big problem with OpenID: phishing</title>
	<atom:link href="http://blog.blinker.net/2009/01/09/a-big-problem-with-openid-phishing/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.blinker.net/2009/01/09/a-big-problem-with-openid-phishing/</link>
	<description>Computer Science, Mathematics, Games</description>
	<lastBuildDate>Mon, 14 Jun 2010 17:39:26 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Andreas</title>
		<link>http://blog.blinker.net/2009/01/09/a-big-problem-with-openid-phishing/comment-page-1/#comment-234</link>
		<dc:creator>Andreas</dc:creator>
		<pubDate>Wed, 14 Jan 2009 08:55:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.blinker.net/?p=20#comment-234</guid>
		<description>Displaying a login page on mvbank.com that looks like mybank.com, just like the phishing attack you&#039;d expect on the OpenID provider.

If you don&#039;t trust HTTPS, then maybe HTTPS should change or be replaced for something better. I don&#039;t see what OpenID can do here.

However, there are some ideas to implement the OpenID provider into the browser. I am not sure how this will work out technically, but it sounds like a solution to your problem.</description>
		<content:encoded><![CDATA[<p>Displaying a login page on mvbank.com that looks like mybank.com, just like the phishing attack you&#8217;d expect on the OpenID provider.</p>
<p>If you don&#8217;t trust HTTPS, then maybe HTTPS should change or be replaced for something better. I don&#8217;t see what OpenID can do here.</p>
<p>However, there are some ideas to implement the OpenID provider into the browser. I am not sure how this will work out technically, but it sounds like a solution to your problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Björn</title>
		<link>http://blog.blinker.net/2009/01/09/a-big-problem-with-openid-phishing/comment-page-1/#comment-228</link>
		<dc:creator>Björn</dc:creator>
		<pubDate>Sun, 11 Jan 2009 22:22:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.blinker.net/?p=20#comment-228</guid>
		<description>HTTPS: no it only verifies that it is the site it pretends to be. mvbank.com could have a valid certificate and still pretend to be mybank.com. Also, since https so often is implemented incorrectly, users are already trained to ignore the warnings. Furthermore, my impression is that many browsers are deployed with dodgy root certificates.

What kind of phishing attacks for conventional login methods do you mean?</description>
		<content:encoded><![CDATA[<p>HTTPS: no it only verifies that it is the site it pretends to be. mvbank.com could have a valid certificate and still pretend to be mybank.com. Also, since https so often is implemented incorrectly, users are already trained to ignore the warnings. Furthermore, my impression is that many browsers are deployed with dodgy root certificates.</p>
<p>What kind of phishing attacks for conventional login methods do you mean?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andreas</title>
		<link>http://blog.blinker.net/2009/01/09/a-big-problem-with-openid-phishing/comment-page-1/#comment-227</link>
		<dc:creator>Andreas</dc:creator>
		<pubDate>Sun, 11 Jan 2009 17:04:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.blinker.net/?p=20#comment-227</guid>
		<description>What&#039;s the problem with HTTPS? It should do exactly what you want: Make sure that you&#039;re talking to the right guy.

Besides: Conventional logins are all vulnerable to phishing, as we know. At least OpenID doesn&#039;t do anything worse. To take it further, it enables the use of phishing proof authentication methods (e.g. public/private key, chipcard) for all OpenID enabled sites.</description>
		<content:encoded><![CDATA[<p>What&#8217;s the problem with HTTPS? It should do exactly what you want: Make sure that you&#8217;re talking to the right guy.</p>
<p>Besides: Conventional logins are all vulnerable to phishing, as we know. At least OpenID doesn&#8217;t do anything worse. To take it further, it enables the use of phishing proof authentication methods (e.g. public/private key, chipcard) for all OpenID enabled sites.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil Jordan</title>
		<link>http://blog.blinker.net/2009/01/09/a-big-problem-with-openid-phishing/comment-page-1/#comment-224</link>
		<dc:creator>Phil Jordan</dc:creator>
		<pubDate>Fri, 09 Jan 2009 14:01:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.blinker.net/?p=20#comment-224</guid>
		<description>Yes, I&#039;ve noticed this too. However, like you said, it&#039;s less of an issue if you&#039;re already logged into your OpenID provider. I know it&#039;s not fully compliant, but the Google login makes this work: it just asks you if you want to log in to [blah] using your Google account.

I&#039;d start getting suspicious if it asked me for my user/pwd. Even if it did, my browser (Opera) would display the &quot;magic wand&quot; highlighting signifying that the browser already knows the credentials for that site. I&#039;d be VERY worried if it didn&#039;t show that.

I more strongly suspect that OpenID in its current form won&#039;t ever go mainstream, so we probably won&#039;t even see OpenID phishing attacks.</description>
		<content:encoded><![CDATA[<p>Yes, I&#8217;ve noticed this too. However, like you said, it&#8217;s less of an issue if you&#8217;re already logged into your OpenID provider. I know it&#8217;s not fully compliant, but the Google login makes this work: it just asks you if you want to log in to [blah] using your Google account.</p>
<p>I&#8217;d start getting suspicious if it asked me for my user/pwd. Even if it did, my browser (Opera) would display the &#8220;magic wand&#8221; highlighting signifying that the browser already knows the credentials for that site. I&#8217;d be VERY worried if it didn&#8217;t show that.</p>
<p>I more strongly suspect that OpenID in its current form won&#8217;t ever go mainstream, so we probably won&#8217;t even see OpenID phishing attacks.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
