<?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: Ka-Ping Yee, Jeff Nelson, Rob Franco, Diana Smetters: Phishing: How will the scourge really be killed? (Panel)</title>
	<atom:link href="http://usablesecurity.com/2006/07/13/ka-ping-yee-jeff-nelson-rob-franco-diana-smetters-phishing-how-will-the-scourge-really-be-killed-panel/feed/" rel="self" type="application/rss+xml" />
	<link>http://usablesecurity.com/2006/07/13/ka-ping-yee-jeff-nelson-rob-franco-diana-smetters-phishing-how-will-the-scourge-really-be-killed-panel/</link>
	<description>Every system has a user.</description>
	<pubDate>Wed, 07 Jan 2009 11:45:48 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>By: Mez</title>
		<link>http://usablesecurity.com/2006/07/13/ka-ping-yee-jeff-nelson-rob-franco-diana-smetters-phishing-how-will-the-scourge-really-be-killed-panel/#comment-5779</link>
		<dc:creator>Mez</dc:creator>
		<pubDate>Fri, 14 Jul 2006 13:58:04 +0000</pubDate>
		<guid isPermaLink="false">http://usablesecurity.com/2006/07/13/ka-ping-yee-jeff-nelson-rob-franco-diana-smetters-phishing-how-will-the-scourge-really-be-killed-panel/#comment-5779</guid>
		<description>The nice thing about incomplete solutions that reduce the problem to first time visits is that they substantially cut down on the scope for attack. Maybe enough to make them unprofitable enough to drive them into the corner that all scams of such sort have been in for a while.</description>
		<content:encoded><![CDATA[<p>The nice thing about incomplete solutions that reduce the problem to first time visits is that they substantially cut down on the scope for attack. Maybe enough to make them unprofitable enough to drive them into the corner that all scams of such sort have been in for a while.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://usablesecurity.com/2006/07/13/ka-ping-yee-jeff-nelson-rob-franco-diana-smetters-phishing-how-will-the-scourge-really-be-killed-panel/#comment-5776</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Fri, 14 Jul 2006 13:01:43 +0000</pubDate>
		<guid isPermaLink="false">http://usablesecurity.com/2006/07/13/ka-ping-yee-jeff-nelson-rob-franco-diana-smetters-phishing-how-will-the-scourge-really-be-killed-panel/#comment-5776</guid>
		<description>I give my money to Ping.

I think, in the short-medium term, the only viable solutions are ones based on confirming to users that the site they are currently at is the site they registered with earlier. Solutions like cookies and Passpet are in this category. Solutions based on centralized authorized or revised encryption methods require more time and effort and money than can be delivered in the short term.

This is an incomplete solution, however, because it assumes that the site was legitimate during the first visit. There are also other risks, but the approach is feasible in the short term and probably usable by a large portion of the Internet population.</description>
		<content:encoded><![CDATA[<p>I give my money to Ping.</p>
<p>I think, in the short-medium term, the only viable solutions are ones based on confirming to users that the site they are currently at is the site they registered with earlier. Solutions like cookies and Passpet are in this category. Solutions based on centralized authorized or revised encryption methods require more time and effort and money than can be delivered in the short term.</p>
<p>This is an incomplete solution, however, because it assumes that the site was legitimate during the first visit. There are also other risks, but the approach is feasible in the short term and probably usable by a large portion of the Internet population.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Diana Smetters</title>
		<link>http://usablesecurity.com/2006/07/13/ka-ping-yee-jeff-nelson-rob-franco-diana-smetters-phishing-how-will-the-scourge-really-be-killed-panel/#comment-5774</link>
		<dc:creator>Diana Smetters</dc:creator>
		<pubDate>Fri, 14 Jul 2006 11:53:22 +0000</pubDate>
		<guid isPermaLink="false">http://usablesecurity.com/2006/07/13/ka-ping-yee-jeff-nelson-rob-franco-diana-smetters-phishing-how-will-the-scourge-really-be-killed-panel/#comment-5774</guid>
		<description>This is definitely one of the hardest parts of the problem to solve effectively. My best theories at the moment come down to things like: maximize the simplicity of the common things (logging in from the same machine you've logged in before, using a token) and make the riskier/more infrequent things harder (e.g. replacing a token, if you have one, or recovering your credentials from backup). The trick for the latter can come down to trusted path -- how do they authenticate replacement of credit cards today? They send them to your physical address. Especially if one makes it harder for an attacker to change that without you detecting it, it may not matter who convinces the credit card company to do it. (And that's only the simplest option.)

 I agree that tokens (or other sorts of helper devices) are not the universal easy answer to everything, and that we need to take advantage of simple things humans can do when we can. But I will argue that what people can do on their own is limited, and vulnerable to attack, and we need to find better technological (or other) means to help protect that limited and vulnerable resource. Right now we've got the equivalent of a "financial biometric" -- passwords, SSN, credit card number, mother's maiden name, etc -- that is also difficult to revoke or change, and can act as a key to get access, money, etc once stolen, but that is possible to trivially type into a computer or read out over the phone. I think we can be cleverer than that. 

I think passpet is one good example of how to begin to be cleverer than that, in an easy and short-term-deployable way -- I have a password for a site that I don't know, that I need to get through a tool that will try to refuse to give it away to the wrong person even when I want to.  As I said in my talk, we need to start by raising the bar wherever we can, I just find it personally preferable to do that with an eye on where we really want to get to in the end, even if it takes a while.</description>
		<content:encoded><![CDATA[<p>This is definitely one of the hardest parts of the problem to solve effectively. My best theories at the moment come down to things like: maximize the simplicity of the common things (logging in from the same machine you&#8217;ve logged in before, using a token) and make the riskier/more infrequent things harder (e.g. replacing a token, if you have one, or recovering your credentials from backup). The trick for the latter can come down to trusted path &#8212; how do they authenticate replacement of credit cards today? They send them to your physical address. Especially if one makes it harder for an attacker to change that without you detecting it, it may not matter who convinces the credit card company to do it. (And that&#8217;s only the simplest option.)</p>
<p> I agree that tokens (or other sorts of helper devices) are not the universal easy answer to everything, and that we need to take advantage of simple things humans can do when we can. But I will argue that what people can do on their own is limited, and vulnerable to attack, and we need to find better technological (or other) means to help protect that limited and vulnerable resource. Right now we&#8217;ve got the equivalent of a &#8220;financial biometric&#8221; &#8212; passwords, SSN, credit card number, mother&#8217;s maiden name, etc &#8212; that is also difficult to revoke or change, and can act as a key to get access, money, etc once stolen, but that is possible to trivially type into a computer or read out over the phone. I think we can be cleverer than that. </p>
<p>I think passpet is one good example of how to begin to be cleverer than that, in an easy and short-term-deployable way &#8212; I have a password for a site that I don&#8217;t know, that I need to get through a tool that will try to refuse to give it away to the wrong person even when I want to.  As I said in my talk, we need to start by raising the bar wherever we can, I just find it personally preferable to do that with an eye on where we really want to get to in the end, even if it takes a while.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mez</title>
		<link>http://usablesecurity.com/2006/07/13/ka-ping-yee-jeff-nelson-rob-franco-diana-smetters-phishing-how-will-the-scourge-really-be-killed-panel/#comment-5772</link>
		<dc:creator>Mez</dc:creator>
		<pubDate>Fri, 14 Jul 2006 10:11:46 +0000</pubDate>
		<guid isPermaLink="false">http://usablesecurity.com/2006/07/13/ka-ping-yee-jeff-nelson-rob-franco-diana-smetters-phishing-how-will-the-scourge-really-be-killed-panel/#comment-5772</guid>
		<description>OK Ping, so where does your (funny) money go to then? With limited resources, what do you choose to target?</description>
		<content:encoded><![CDATA[<p>OK Ping, so where does your (funny) money go to then? With limited resources, what do you choose to target?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ping</title>
		<link>http://usablesecurity.com/2006/07/13/ka-ping-yee-jeff-nelson-rob-franco-diana-smetters-phishing-how-will-the-scourge-really-be-killed-panel/#comment-5768</link>
		<dc:creator>Ping</dc:creator>
		<pubDate>Fri, 14 Jul 2006 03:36:38 +0000</pubDate>
		<guid isPermaLink="false">http://usablesecurity.com/2006/07/13/ka-ping-yee-jeff-nelson-rob-franco-diana-smetters-phishing-how-will-the-scourge-really-be-killed-panel/#comment-5768</guid>
		<description>I'm not convinced.

Let's try to follow what you and Diana suggest to its logical conclusion.  If we want credentials that don't lose their value when a secret leaks or is given away, what does that mean?  It seems to me the only alternative would be physical tokens.  So your credit card becomes a cryptographic token with an embedded key.  Fine.  Now what do you do if you lose your wallet?

Probably, you call the bank to report a stolen card and get a replacement.  Okay, now how does the bank know they can trust your call?  Do they ask you your address?  Your account number?  Your birthdate?  Your SSN?

But this personal information was supposed to have no value that could be lost by revealing it.  So how do you recover from failure?  It would seem that there's no way to fix the problem on the phone.  So now you have to show up in person.  And in person, what can you give them to prove your identity but perhaps some other piece of ID — which will also have to be a cryptographic token?  And what if you don't have your ID because it was in your stolen wallet?

The point of my story is to show that authentication has to bottom out somewhere.  Stripped of all your possessions, your only sources of identity are your mind and your body.  Today we use the mind: the final recourse is your memory, your knowledge of yourself.  Some are proposing that we switch to using the body instead (biometrics), which is a troublesome idea (in part because you can't replace body parts after a biometric is compromised).

I don't think it's possible to build a system that bottoms out in hardware tokens because tokens cost money, can be lost, and can be stolen.  Not everyone has the ability to obtain a token.  But everybody has a mind and has the ability to remember information about themselves.  It's impossible to get away from the fact that this information is valuable.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not convinced.</p>
<p>Let&#8217;s try to follow what you and Diana suggest to its logical conclusion.  If we want credentials that don&#8217;t lose their value when a secret leaks or is given away, what does that mean?  It seems to me the only alternative would be physical tokens.  So your credit card becomes a cryptographic token with an embedded key.  Fine.  Now what do you do if you lose your wallet?</p>
<p>Probably, you call the bank to report a stolen card and get a replacement.  Okay, now how does the bank know they can trust your call?  Do they ask you your address?  Your account number?  Your birthdate?  Your SSN?</p>
<p>But this personal information was supposed to have no value that could be lost by revealing it.  So how do you recover from failure?  It would seem that there&#8217;s no way to fix the problem on the phone.  So now you have to show up in person.  And in person, what can you give them to prove your identity but perhaps some other piece of ID — which will also have to be a cryptographic token?  And what if you don&#8217;t have your ID because it was in your stolen wallet?</p>
<p>The point of my story is to show that authentication has to bottom out somewhere.  Stripped of all your possessions, your only sources of identity are your mind and your body.  Today we use the mind: the final recourse is your memory, your knowledge of yourself.  Some are proposing that we switch to using the body instead (biometrics), which is a troublesome idea (in part because you can&#8217;t replace body parts after a biometric is compromised).</p>
<p>I don&#8217;t think it&#8217;s possible to build a system that bottoms out in hardware tokens because tokens cost money, can be lost, and can be stolen.  Not everyone has the ability to obtain a token.  But everybody has a mind and has the ability to remember information about themselves.  It&#8217;s impossible to get away from the fact that this information is valuable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Nelson</title>
		<link>http://usablesecurity.com/2006/07/13/ka-ping-yee-jeff-nelson-rob-franco-diana-smetters-phishing-how-will-the-scourge-really-be-killed-panel/#comment-5767</link>
		<dc:creator>Jeff Nelson</dc:creator>
		<pubDate>Fri, 14 Jul 2006 02:04:40 +0000</pubDate>
		<guid isPermaLink="false">http://usablesecurity.com/2006/07/13/ka-ping-yee-jeff-nelson-rob-franco-diana-smetters-phishing-how-will-the-scourge-really-be-killed-panel/#comment-5767</guid>
		<description>Diana Smetters gave a surprisingly plausible argument that phishing is not the problem.  Instead, we need to re-engineer the credentials so that the values of SSN, credit card number, and passwords are not lost by revealing them.  This could be accomplished through IBE, PKI or ZKP techniques, albeit replacing the credit card infrastructure is not going to happen over night.  

If we were choosing a winner for the panel, she smacked us around like a rented mule.  So my million would go to start a credit card company based on PKI.</description>
		<content:encoded><![CDATA[<p>Diana Smetters gave a surprisingly plausible argument that phishing is not the problem.  Instead, we need to re-engineer the credentials so that the values of SSN, credit card number, and passwords are not lost by revealing them.  This could be accomplished through IBE, PKI or ZKP techniques, albeit replacing the credit card infrastructure is not going to happen over night.  </p>
<p>If we were choosing a winner for the panel, she smacked us around like a rented mule.  So my million would go to start a credit card company based on PKI.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mez</title>
		<link>http://usablesecurity.com/2006/07/13/ka-ping-yee-jeff-nelson-rob-franco-diana-smetters-phishing-how-will-the-scourge-really-be-killed-panel/#comment-5765</link>
		<dc:creator>Mez</dc:creator>
		<pubDate>Fri, 14 Jul 2006 01:39:31 +0000</pubDate>
		<guid isPermaLink="false">http://usablesecurity.com/2006/07/13/ka-ping-yee-jeff-nelson-rob-franco-diana-smetters-phishing-how-will-the-scourge-really-be-killed-panel/#comment-5765</guid>
		<description>My personal thanks again to the panelists for doing such a great job and putting yourselves out there to make the discussion lively. 

The question I didn't get a chance to ask because there were so many others - if you had $1millionUS to spend on the phishing problem, and could not spend it on yourself or your colleagues, what would you spend it on?</description>
		<content:encoded><![CDATA[<p>My personal thanks again to the panelists for doing such a great job and putting yourselves out there to make the discussion lively. </p>
<p>The question I didn&#8217;t get a chance to ask because there were so many others - if you had $1millionUS to spend on the phishing problem, and could not spend it on yourself or your colleagues, what would you spend it on?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
