<?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: Phishing and OpenID: Bookmarks to the Rescue?</title>
	<atom:link href="http://usablesecurity.com/2007/01/20/phishing-and-openid/feed/" rel="self" type="application/rss+xml" />
	<link>http://usablesecurity.com/2007/01/20/phishing-and-openid/</link>
	<description>Every system has a user.</description>
	<pubDate>Thu, 24 Jul 2008 02:06:06 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>By: Daniel Chien</title>
		<link>http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-65010</link>
		<dc:creator>Daniel Chien</dc:creator>
		<pubDate>Mon, 09 Jul 2007 06:08:53 +0000</pubDate>
		<guid isPermaLink="false">http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-65010</guid>
		<description>I have a simple way to detect phishing website by checking the IP address of the phishing website.  On the Internet, everyone has an IP address.  You can not fake your IP address due to IP two-way routing. Phishing website must use an IP address and can not be same as legitimate financial institution IP address.  By comparing the IP address, we can know this is a phishing website or not.</description>
		<content:encoded><![CDATA[<p>I have a simple way to detect phishing website by checking the IP address of the phishing website.  On the Internet, everyone has an IP address.  You can not fake your IP address due to IP two-way routing. Phishing website must use an IP address and can not be same as legitimate financial institution IP address.  By comparing the IP address, we can know this is a phishing website or not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: randomwalker</title>
		<link>http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-49236</link>
		<dc:creator>randomwalker</dc:creator>
		<pubDate>Thu, 03 May 2007 06:23:27 +0000</pubDate>
		<guid isPermaLink="false">http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-49236</guid>
		<description>If I have to retry the transaction (comment posting or whatever) at the original site, then I'm simply not going to use it. Sorry.

Further, I might realize that I have to login only after I write my comment. There's a chance that the data will be lost when I try to get back there. If this happens, the user will VERY QUICKLY learn not to use your service EVER AGAIN.</description>
		<content:encoded><![CDATA[<p>If I have to retry the transaction (comment posting or whatever) at the original site, then I&#8217;m simply not going to use it. Sorry.</p>
<p>Further, I might realize that I have to login only after I write my comment. There&#8217;s a chance that the data will be lost when I try to get back there. If this happens, the user will VERY QUICKLY learn not to use your service EVER AGAIN.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Security Roundtable &#187; Blog Archive &#187; The Security Roundtable for February 2007 - OpenID</title>
		<link>http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-36371</link>
		<dc:creator>The Security Roundtable &#187; Blog Archive &#187; The Security Roundtable for February 2007 - OpenID</dc:creator>
		<pubDate>Thu, 15 Mar 2007 19:56:09 +0000</pubDate>
		<guid isPermaLink="false">http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-36371</guid>
		<description>[...] Another idea (and MITM attack): http://usablesecurity.com/2007/01/20/phishing-and-openid/ [...]</description>
		<content:encoded><![CDATA[<p>[...] Another idea (and MITM attack): <a href="http://usablesecurity.com/2007/01/20/phishing-and-openid/" rel="nofollow">http://usablesecurity.com/2007/01/20/phishing-and-openid/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Confluence: PlatformSecurity</title>
		<link>http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-32793</link>
		<dc:creator>Confluence: PlatformSecurity</dc:creator>
		<pubDate>Wed, 28 Feb 2007 22:22:15 +0000</pubDate>
		<guid isPermaLink="false">http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-32793</guid>
		<description>&lt;strong&gt;OpenID...&lt;/strong&gt;

OpenID  This page has not been filled in yet.   Notes from Sunil (email):  And of course, UCAP can prevent it through it's Defense is depth approach (Security Skin, EV SSL, Reputation Service, Stronger Username/password).......</description>
		<content:encoded><![CDATA[<p><strong>OpenID&#8230;</strong></p>
<p>OpenID  This page has not been filled in yet.   Notes from Sunil (email):  And of course, UCAP can prevent it through it&#8217;s Defense is depth approach (Security Skin, EV SSL, Reputation Service, Stronger Username/password)&#8230;&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard M. Conlan</title>
		<link>http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-32695</link>
		<dc:creator>Richard M. Conlan</dc:creator>
		<pubDate>Wed, 28 Feb 2007 08:42:37 +0000</pubDate>
		<guid isPermaLink="false">http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-32695</guid>
		<description>Some interesting blog entries on OpenID with comments on phishing and other issues:

&lt;a href="http://www.tbray.org/ongoing/When/200x/2007/02/24/OpenID" rel="nofollow"&gt;ongoing&lt;/a&gt;

&lt;a href="http://slesinsky.org/brian/code/should_we_support_openid.html" rel="nofollow"&gt;Should We Support OpenID?&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Some interesting blog entries on OpenID with comments on phishing and other issues:</p>
<p><a href="http://www.tbray.org/ongoing/When/200x/2007/02/24/OpenID" rel="nofollow">ongoing</a></p>
<p><a href="http://slesinsky.org/brian/code/should_we_support_openid.html" rel="nofollow">Should We Support OpenID?</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dubroy.com/blog &#187; Warming up to OpenID</title>
		<link>http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-32439</link>
		<dc:creator>Dubroy.com/blog &#187; Warming up to OpenID</dc:creator>
		<pubDate>Mon, 26 Feb 2007 18:20:35 +0000</pubDate>
		<guid isPermaLink="false">http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-32439</guid>
		<description>[...] It&#8217;s not all rosy though. Many people have pointed out that the OpenID process is very susceptible to phishing attacks; but that&#8217;s a problem we&#8217;re going to have to solve somehow anyways, and I think the proposed solutions are pretty decent.   Technorati Tags: authentication, openid, security, single sign on, usability [...]</description>
		<content:encoded><![CDATA[<p>[...] It&#8217;s not all rosy though. Many people have pointed out that the OpenID process is very susceptible to phishing attacks; but that&#8217;s a problem we&#8217;re going to have to solve somehow anyways, and I think the proposed solutions are pretty decent.   Technorati Tags: authentication, openid, security, single sign on, usability [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ping</title>
		<link>http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-31252</link>
		<dc:creator>Ping</dc:creator>
		<pubDate>Wed, 21 Feb 2007 04:45:02 +0000</pubDate>
		<guid isPermaLink="false">http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-31252</guid>
		<description>If you always go directly to your OpenID provider to enter your password, then there's no problem.  The problem is the case where the relying party redirects you to your OpenID provider's login form.</description>
		<content:encoded><![CDATA[<p>If you always go directly to your OpenID provider to enter your password, then there&#8217;s no problem.  The problem is the case where the relying party redirects you to your OpenID provider&#8217;s login form.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Cross</title>
		<link>http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-29763</link>
		<dc:creator>Mark Cross</dc:creator>
		<pubDate>Tue, 13 Feb 2007 13:35:19 +0000</pubDate>
		<guid isPermaLink="false">http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-29763</guid>
		<description>Dear Ping,

I don't quite follow your walk through:

Go to my OpenID provider &#38; "log in" with OpenID URL &#38; Password.
Visit a site I’ve never seen before. 
Enter my OpenID name and click “Log in”. 
See the challenge page for my OpenID provider. 
Return back to the newly added site.

If you were prompted for a password - something did go astray.

Yours puzzled,

Mark</description>
		<content:encoded><![CDATA[<p>Dear Ping,</p>
<p>I don&#8217;t quite follow your walk through:</p>
<p>Go to my OpenID provider &amp; &#8220;log in&#8221; with OpenID URL &amp; Password.<br />
Visit a site I’ve never seen before.<br />
Enter my OpenID name and click “Log in”.<br />
See the challenge page for my OpenID provider.<br />
Return back to the newly added site.</p>
<p>If you were prompted for a password - something did go astray.</p>
<p>Yours puzzled,</p>
<p>Mark</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Benlog &#187; BeamAuth: Two-Factor Web Authentication with a Bookmark.</title>
		<link>http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-28397</link>
		<dc:creator>Benlog &#187; BeamAuth: Two-Factor Web Authentication with a Bookmark.</dc:creator>
		<pubDate>Tue, 06 Feb 2007 19:47:48 +0000</pubDate>
		<guid isPermaLink="false">http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-28397</guid>
		<description>[...] In recent days, Simon Willinson and then Ka-Ping Yee proposed having Alice use a bookmark to reach her OpenID server, rather than rely on the web site to redirect appropriately. This is interesting, and one of the OpenID implementors, JanRain, thinks so too. [...]</description>
		<content:encoded><![CDATA[<p>[...] In recent days, Simon Willinson and then Ka-Ping Yee proposed having Alice use a bookmark to reach her OpenID server, rather than rely on the web site to redirect appropriately. This is interesting, and one of the OpenID implementors, JanRain, thinks so too. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kragen Sitaker</title>
		<link>http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-26826</link>
		<dc:creator>Kragen Sitaker</dc:creator>
		<pubDate>Mon, 29 Jan 2007 03:37:27 +0000</pubDate>
		<guid isPermaLink="false">http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-26826</guid>
		<description>Looks like Simon went and implemented this as part of his &lt;a href="http://idproxy.net/about/phishing/" rel="nofollow"&gt;idproxy&lt;/a&gt; service.</description>
		<content:encoded><![CDATA[<p>Looks like Simon went and implemented this as part of his <a href="http://idproxy.net/about/phishing/" rel="nofollow">idproxy</a> service.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Cox</title>
		<link>http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-25726</link>
		<dc:creator>Andrew Cox</dc:creator>
		<pubDate>Tue, 23 Jan 2007 08:25:40 +0000</pubDate>
		<guid isPermaLink="false">http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-25726</guid>
		<description></description>
		<content:encoded><![CDATA[<br />
]]></content:encoded>
	</item>
	<item>
		<title>By: Don Park</title>
		<link>http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-25649</link>
		<dc:creator>Don Park</dc:creator>
		<pubDate>Mon, 22 Jan 2007 22:16:30 +0000</pubDate>
		<guid isPermaLink="false">http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-25649</guid>
		<description>Ping, I like the way you think. Admitedly, this is one of the password-less ideas I had but it's neat to find others thinking along the same line. Oh, I liked your Passpet idea also. :-)</description>
		<content:encoded><![CDATA[<p>Ping, I like the way you think. Admitedly, this is one of the password-less ideas I had but it&#8217;s neat to find others thinking along the same line. Oh, I liked your Passpet idea also. :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ping</title>
		<link>http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-25525</link>
		<dc:creator>Ping</dc:creator>
		<pubDate>Mon, 22 Jan 2007 06:25:01 +0000</pubDate>
		<guid isPermaLink="false">http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-25525</guid>
		<description>I don't think you're misunderstanding it.  The procedure I had in mind was to first use the bookmark to log in, and then retry the original transaction.  With a little care in the UI, the provider might be able to make this less confusing.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think you&#8217;re misunderstanding it.  The procedure I had in mind was to first use the bookmark to log in, and then retry the original transaction.  With a little care in the UI, the provider might be able to make this less confusing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ping</title>
		<link>http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-25524</link>
		<dc:creator>Ping</dc:creator>
		<pubDate>Mon, 22 Jan 2007 06:23:32 +0000</pubDate>
		<guid isPermaLink="false">http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-25524</guid>
		<description>Yes, you can embed the secret in the URL.  Then you're essentially using the URL like a &lt;a href="http://en.wikipedia.org/wiki/Capability_(computers)" rel="nofollow"&gt;capability&lt;/a&gt;.  In general, this is a great idea, though it may take some catching up from software to properly treat URLs as capabilities (they need to be treated as secrets, and there's the issue of logging in from a different computer than the one you normally use).</description>
		<content:encoded><![CDATA[<p>Yes, you can embed the secret in the URL.  Then you&#8217;re essentially using the URL like a <a href="http://en.wikipedia.org/wiki/Capability_(computers)" rel="nofollow">capability</a>.  In general, this is a great idea, though it may take some catching up from software to properly treat URLs as capabilities (they need to be treated as secrets, and there&#8217;s the issue of logging in from a different computer than the one you normally use).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ping</title>
		<link>http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-25523</link>
		<dc:creator>Ping</dc:creator>
		<pubDate>Mon, 22 Jan 2007 06:13:36 +0000</pubDate>
		<guid isPermaLink="false">http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-25523</guid>
		<description>Providers could do that, if they wanted.  But I don't expect the personalized-image scheme to work, because it's susceptible to a man-in-the-middle attack.

If I want to phish your password, I'll go to the provider and attempt to log in as you.  The provider will show me your image and title.  Then I present that image and title to you when persuading you to give me your password.</description>
		<content:encoded><![CDATA[<p>Providers could do that, if they wanted.  But I don&#8217;t expect the personalized-image scheme to work, because it&#8217;s susceptible to a man-in-the-middle attack.</p>
<p>If I want to phish your password, I&#8217;ll go to the provider and attempt to log in as you.  The provider will show me your image and title.  Then I present that image and title to you when persuading you to give me your password.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Hammond</title>
		<link>http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-25484</link>
		<dc:creator>David Hammond</dc:creator>
		<pubDate>Sun, 21 Jan 2007 23:34:40 +0000</pubDate>
		<guid isPermaLink="false">http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-25484</guid>
		<description>OpenID providers could do something I've seen bank websites do: When you sign up for an account, it asks you to pick an image from a small collection they provide, and then to give a title to that image. Whenever you go to the page to type in your password, the image and title you selected should appear above the login form. Users are told to never type their password on a page unless they see that image and title. This is much easier than asking users to bookmark things, and it's very safe.</description>
		<content:encoded><![CDATA[<p>OpenID providers could do something I&#8217;ve seen bank websites do: When you sign up for an account, it asks you to pick an image from a small collection they provide, and then to give a title to that image. Whenever you go to the page to type in your password, the image and title you selected should appear above the login form. Users are told to never type their password on a page unless they see that image and title. This is much easier than asking users to bookmark things, and it&#8217;s very safe.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Blog by Kveton &#187; OpenID 2.0 and Phishing</title>
		<link>http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-25467</link>
		<dc:creator>Blog by Kveton &#187; OpenID 2.0 and Phishing</dc:creator>
		<pubDate>Sun, 21 Jan 2007 21:51:47 +0000</pubDate>
		<guid isPermaLink="false">http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-25467</guid>
		<description>[...] OpenID 2.0 and Phishing    January 21st, 2007 &#124; Category: OpenID, JanRain, Identity, Phishing   There has been a bunch of discussion about OpenID 2.0 and how the latest draft does not address phishing at all. [...]</description>
		<content:encoded><![CDATA[<p>[...] OpenID 2.0 and Phishing    January 21st, 2007 | Category: OpenID, JanRain, Identity, Phishing   There has been a bunch of discussion about OpenID 2.0 and how the latest draft does not address phishing at all. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alessandro "jekil" Tanasi blog</title>
		<link>http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-25455</link>
		<dc:creator>Alessandro "jekil" Tanasi blog</dc:creator>
		<pubDate>Sun, 21 Jan 2007 20:23:09 +0000</pubDate>
		<guid isPermaLink="false">http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-25455</guid>
		<description>&lt;strong&gt;Week's Links...&lt;/strong&gt;

Social Engineering: A Means To Violate A Computer SystemAn Introduction to Information System Risk ManagementInvestigations Involving the Internet and Computer Networks List of frequently seen TCP and UDP ports and what they meanReview: Six Rootkit Det...</description>
		<content:encoded><![CDATA[<p><strong>Week&#8217;s Links&#8230;</strong></p>
<p>Social Engineering: A Means To Violate A Computer SystemAn Introduction to Information System Risk ManagementInvestigations Involving the Internet and Computer Networks List of frequently seen TCP and UDP ports and what they meanReview: Six Rootkit Det&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Sayre&#8217;s Mozilla Blog &#187; Blog Archive &#187; Phishing and OpenID</title>
		<link>http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-25432</link>
		<dc:creator>Rob Sayre&#8217;s Mozilla Blog &#187; Blog Archive &#187; Phishing and OpenID</dc:creator>
		<pubDate>Sun, 21 Jan 2007 19:06:36 +0000</pubDate>
		<guid isPermaLink="false">http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-25432</guid>
		<description>[...] Ka-Ping Yee: &#8220;OpenID, as currently used for single sign-on, facilitates phishing.&#8220; [...]</description>
		<content:encoded><![CDATA[<p>[...] Ka-Ping Yee: &#8220;OpenID, as currently used for single sign-on, facilitates phishing.&#8220; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stuart Langridge</title>
		<link>http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-25415</link>
		<dc:creator>Stuart Langridge</dc:creator>
		<pubDate>Sun, 21 Jan 2007 16:42:40 +0000</pubDate>
		<guid isPermaLink="false">http://usablesecurity.com/2007/01/20/phishing-and-openid/#comment-25415</guid>
		<description>Agreed that we're better confused than phished, of course. However, we ought to strive to make things actually work, no?</description>
		<content:encoded><![CDATA[<p>Agreed that we&#8217;re better confused than phished, of course. However, we ought to strive to make things actually work, no?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
