<?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: Evaluating statistical attacks on personal knowledge questions</title>
	<atom:link href="http://www.lightbluetouchpaper.org/2010/03/04/evaluating-statistical-attacks-on-personal-knowledge-questions/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lightbluetouchpaper.org/2010/03/04/evaluating-statistical-attacks-on-personal-knowledge-questions/</link>
	<description>Security Research, Computer Laboratory, University of Cambridge</description>
	<lastBuildDate>Fri, 27 Aug 2010 15:36:41 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Harold</title>
		<link>http://www.lightbluetouchpaper.org/2010/03/04/evaluating-statistical-attacks-on-personal-knowledge-questions/comment-page-1/#comment-56182</link>
		<dc:creator>Harold</dc:creator>
		<pubDate>Sun, 18 Apr 2010 22:01:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/?p=1879#comment-56182</guid>
		<description>Permit me to suggest a model for &quot;mere mortals,&quot; to invent a reasonably secure password which, I believe, will confound hackers AND be easy to remember:

Pick a favorite tune and the last 4 digits of your mother&#039;s phone number.  i.e.  My Country Tis Of Thee and Mom&#039;s # 7856

The password uses the first letter of each word and adds Mom&#039;s number, BUT hold the shift key when typing the numbers.  The password becomes:

MCTOT&amp;*%^</description>
		<content:encoded><![CDATA[<p>Permit me to suggest a model for &#8220;mere mortals,&#8221; to invent a reasonably secure password which, I believe, will confound hackers AND be easy to remember:</p>
<p>Pick a favorite tune and the last 4 digits of your mother&#8217;s phone number.  i.e.  My Country Tis Of Thee and Mom&#8217;s # 7856</p>
<p>The password uses the first letter of each word and adds Mom&#8217;s number, BUT hold the shift key when typing the numbers.  The password becomes:</p>
<p>MCTOT&amp;*%^</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: T Chan</title>
		<link>http://www.lightbluetouchpaper.org/2010/03/04/evaluating-statistical-attacks-on-personal-knowledge-questions/comment-page-1/#comment-53569</link>
		<dc:creator>T Chan</dc:creator>
		<pubDate>Mon, 29 Mar 2010 18:37:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/?p=1879#comment-53569</guid>
		<description>I recently reset the password for two of my Apple accounts (I think both date to before they did SSO; I also have records of a third account which I can&#039;t log in to). It&#039;s a bit surprising when it says &quot;Your account has been locked for security reasons.&quot; but you can still unlock it with an insecurity question.

If I care about reproducing an insecurity question answer should my password storage mechanism fail, the question is something like &lt;i&gt;MAC(k,&quot;FooWebsiteQuestion1&quot;)&lt;/i&gt; and the answer is the MAC (I usually paste the shell command as the question so I get the right hex/base64/truncated/etc answer). It&#039;s not that secure, but I&#039;m reasonably sure that all existing copies of &lt;i&gt;k&lt;/i&gt; are under my control.

If I don&#039;t care that much, I use a slightly different method:
• If I need to give an answer over the phone, use a few random words with something like &lt;code&gt;python -c &#039;import random,math;l=list(set(map(str.lower,open(&quot;/usr/share/dict/words&quot;,&quot;rb&quot;).read().split())));print &quot;%r, %f bits&quot;%(random.SystemRandom().choice(l),math.log(len(l),2))&#039;&lt;/code&gt;
• If not, I generate it the same way I generate passwords: &lt;code&gt;dd if=/dev/random count=1 &#124; openssl sha1 -binary &#124; openssl base64 &#124; sed -e&#039;s/.==*//&#039; &#124; tr /+ -_&lt;/code&gt; (the &lt;code&gt;sed&lt;/code&gt; removes the characters without 6 bits of entropy).
If I get to pick the question, my latest choice is &quot;random1&quot; and &quot;random2&quot;.</description>
		<content:encoded><![CDATA[<p>I recently reset the password for two of my Apple accounts (I think both date to before they did SSO; I also have records of a third account which I can&#8217;t log in to). It&#8217;s a bit surprising when it says &#8220;Your account has been locked for security reasons.&#8221; but you can still unlock it with an insecurity question.</p>
<p>If I care about reproducing an insecurity question answer should my password storage mechanism fail, the question is something like <i>MAC(k,&#8221;FooWebsiteQuestion1&#8243;)</i> and the answer is the MAC (I usually paste the shell command as the question so I get the right hex/base64/truncated/etc answer). It&#8217;s not that secure, but I&#8217;m reasonably sure that all existing copies of <i>k</i> are under my control.</p>
<p>If I don&#8217;t care that much, I use a slightly different method:<br />
• If I need to give an answer over the phone, use a few random words with something like <code>python -c 'import random,math;l=list(set(map(str.lower,open("/usr/share/dict/words","rb").read().split())));print "%r, %f bits"%(random.SystemRandom().choice(l),math.log(len(l),2))'</code><br />
• If not, I generate it the same way I generate passwords: <code>dd if=/dev/random count=1 | openssl sha1 -binary | openssl base64 | sed -e's/.==*//' | tr /+ -_</code> (the <code>sed</code> removes the characters without 6 bits of entropy).<br />
If I get to pick the question, my latest choice is &#8220;random1&#8243; and &#8220;random2&#8243;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Malibu Stacey</title>
		<link>http://www.lightbluetouchpaper.org/2010/03/04/evaluating-statistical-attacks-on-personal-knowledge-questions/comment-page-1/#comment-52486</link>
		<dc:creator>Malibu Stacey</dc:creator>
		<pubDate>Thu, 18 Mar 2010 11:41:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/?p=1879#comment-52486</guid>
		<description>Daniel you&#039;re missing the point.
If some unscrupulous person is attacking a wide range of accounts to get at $100 in each account, the statistics say they will get approximately 1 success for every 84 account attempts. For rounding sake say they try 840 accounts, that&#039;s 10 success = $1000. Keep increasing by powers of 10 &amp; then think about how much time it would take to try all those accounts given even a relatively low power laptop &amp; a coffee shop WiFi connection.
Also if you&#039;ve only got $100 in your account right now, once they&#039;ve gained access to your account whats to stop the unscrupulous type looking at your history, seeing when your salary or other regular payments arrive in your account &amp; waiting until then to empty it?</description>
		<content:encoded><![CDATA[<p>Daniel you&#8217;re missing the point.<br />
If some unscrupulous person is attacking a wide range of accounts to get at $100 in each account, the statistics say they will get approximately 1 success for every 84 account attempts. For rounding sake say they try 840 accounts, that&#8217;s 10 success = $1000. Keep increasing by powers of 10 &amp; then think about how much time it would take to try all those accounts given even a relatively low power laptop &amp; a coffee shop WiFi connection.<br />
Also if you&#8217;ve only got $100 in your account right now, once they&#8217;ve gained access to your account whats to stop the unscrupulous type looking at your history, seeing when your salary or other regular payments arrive in your account &amp; waiting until then to empty it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel</title>
		<link>http://www.lightbluetouchpaper.org/2010/03/04/evaluating-statistical-attacks-on-personal-knowledge-questions/comment-page-1/#comment-52252</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Wed, 17 Mar 2010 02:25:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/?p=1879#comment-52252</guid>
		<description>While I realize this is an academic site I do wonder just how much of a real problem this weak security actually represents. The example of celebrities is not persuasive as an attacker has a strong incentive to devote time and resources to the problem. But if you told me out of the blue that someone had a 1/84 chance of stealing my account data I&#039;d take it in a flash. I think those odds are wonderful! I can&#039;t imagine any attacker spending that amount of time to get the $100 in my bank account. 

And that&#039;s a real critical point. Names might be &quot;good enough&quot; security. Unless there is a real and honest evaluation of the cost of the attacking the account compared to the benefit accruing to the hacker, this research remains non-compelling.</description>
		<content:encoded><![CDATA[<p>While I realize this is an academic site I do wonder just how much of a real problem this weak security actually represents. The example of celebrities is not persuasive as an attacker has a strong incentive to devote time and resources to the problem. But if you told me out of the blue that someone had a 1/84 chance of stealing my account data I&#8217;d take it in a flash. I think those odds are wonderful! I can&#8217;t imagine any attacker spending that amount of time to get the $100 in my bank account. </p>
<p>And that&#8217;s a real critical point. Names might be &#8220;good enough&#8221; security. Unless there is a real and honest evaluation of the cost of the attacking the account compared to the benefit accruing to the hacker, this research remains non-compelling.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Watson</title>
		<link>http://www.lightbluetouchpaper.org/2010/03/04/evaluating-statistical-attacks-on-personal-knowledge-questions/comment-page-1/#comment-51521</link>
		<dc:creator>Andrew Watson</dc:creator>
		<pubDate>Thu, 11 Mar 2010 12:04:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/?p=1879#comment-51521</guid>
		<description>Slightly OT, but I did enjoy Lucy Porter&#039;s subversive take on this:

http://www.youtube.com/watch?v=q3ALAjwuO1M</description>
		<content:encoded><![CDATA[<p>Slightly OT, but I did enjoy Lucy Porter&#8217;s subversive take on this:</p>
<p><a href="http://www.youtube.com/watch?v=q3ALAjwuO1M" rel="nofollow">http://www.youtube.com/watch?v=q3ALAjwuO1M</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clive Robinson</title>
		<link>http://www.lightbluetouchpaper.org/2010/03/04/evaluating-statistical-attacks-on-personal-knowledge-questions/comment-page-1/#comment-51247</link>
		<dc:creator>Clive Robinson</dc:creator>
		<pubDate>Wed, 10 Mar 2010 10:11:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/?p=1879#comment-51247</guid>
		<description>@ Joseph Bonneau,

Sorry I&#039;m a little late replying I&#039;ve had my time tied up a bit at this end.

The main problem I see with all authentication systems is not in &quot;finding&quot; alternatives but in &quot;replacing&quot; existing systems.

Forty years ago we knew that passwords where a bad idea, yet here they still are alive and causing problems major problems.

The only improvment in passwords has been asking users to use complex password scheams that fail for various reasons to do with &quot;human failings&quot;.

[And yes I&#039;m a &quot;sinner&quot; I&#039;ve a couple of online accounts I cannot get into because I cannot remember my &quot;clever&quot; passwords and answers. Now if I&#039;d put in the real name of my first pet...]

Worse of all the alternatives that are practical sugestions in most cases they will all fail to human weakness (we forget/break/lose/have stolen/etc things and move on without full consideration).

So unfortunatly we have these systems not just because they are simple to build, but because they do work with falable humans (except for that reset password button that emails to an email account you nolonger have as you&#039;ve moved on to a new employer/ISP/etc).

The obvious solution is of course the easy &quot;universal unique identifier used as an authentication token&quot;, but then... That has a whole host of issues it&#039;s self not least of which are &quot;who pays&quot; and an individuals &quot;roles in life&quot; that realy should be seperate otherwise the anonymity that is required for our current societies to function is broken...

So if we cannot &quot;replace&quot; such pasword etc systems the best we can do is &quot;augment&quot; them. 

Which then brings up, 

&quot;how do you augment without effectivly replacing&quot;...

Hence my sugestion of two or more questions.

Which you quite correctly show does have it&#039;s failings (those pesky humans again ;)

It is without doubt a very very hard problem simply because of &quot;human failings&quot;.

And I for one am most definatly not in favour of the &quot;Government Soloutions&quot; of National ID&#039;s etc because in the long term their use to society is detrimental to the extream.</description>
		<content:encoded><![CDATA[<p>@ Joseph Bonneau,</p>
<p>Sorry I&#8217;m a little late replying I&#8217;ve had my time tied up a bit at this end.</p>
<p>The main problem I see with all authentication systems is not in &#8220;finding&#8221; alternatives but in &#8220;replacing&#8221; existing systems.</p>
<p>Forty years ago we knew that passwords where a bad idea, yet here they still are alive and causing problems major problems.</p>
<p>The only improvment in passwords has been asking users to use complex password scheams that fail for various reasons to do with &#8220;human failings&#8221;.</p>
<p>[And yes I'm a "sinner" I've a couple of online accounts I cannot get into because I cannot remember my "clever" passwords and answers. Now if I'd put in the real name of my first pet...]</p>
<p>Worse of all the alternatives that are practical sugestions in most cases they will all fail to human weakness (we forget/break/lose/have stolen/etc things and move on without full consideration).</p>
<p>So unfortunatly we have these systems not just because they are simple to build, but because they do work with falable humans (except for that reset password button that emails to an email account you nolonger have as you&#8217;ve moved on to a new employer/ISP/etc).</p>
<p>The obvious solution is of course the easy &#8220;universal unique identifier used as an authentication token&#8221;, but then&#8230; That has a whole host of issues it&#8217;s self not least of which are &#8220;who pays&#8221; and an individuals &#8220;roles in life&#8221; that realy should be seperate otherwise the anonymity that is required for our current societies to function is broken&#8230;</p>
<p>So if we cannot &#8220;replace&#8221; such pasword etc systems the best we can do is &#8220;augment&#8221; them. </p>
<p>Which then brings up, </p>
<p>&#8220;how do you augment without effectivly replacing&#8221;&#8230;</p>
<p>Hence my sugestion of two or more questions.</p>
<p>Which you quite correctly show does have it&#8217;s failings (those pesky humans again <img src='http://www.lightbluetouchpaper.org/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>It is without doubt a very very hard problem simply because of &#8220;human failings&#8221;.</p>
<p>And I for one am most definatly not in favour of the &#8220;Government Soloutions&#8221; of National ID&#8217;s etc because in the long term their use to society is detrimental to the extream.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lawrence</title>
		<link>http://www.lightbluetouchpaper.org/2010/03/04/evaluating-statistical-attacks-on-personal-knowledge-questions/comment-page-1/#comment-50630</link>
		<dc:creator>Lawrence</dc:creator>
		<pubDate>Fri, 05 Mar 2010 18:38:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/?p=1879#comment-50630</guid>
		<description>The weakness of that scheme is not surprising. When faced with that type of system I use a workaround to avoid the security risk. Essentially, I use a randomly generated answer that is totally unguessable. So, that will make a trawling attack fail on my accounts. More importantly, since you must supply an answer, any other way of answering decreases the security of the account. That type of measure is a security weakness tolerated for economic reasons, we may not be able to refuse using it but at least it is possible to avoid it&#039;s inherent risk.</description>
		<content:encoded><![CDATA[<p>The weakness of that scheme is not surprising. When faced with that type of system I use a workaround to avoid the security risk. Essentially, I use a randomly generated answer that is totally unguessable. So, that will make a trawling attack fail on my accounts. More importantly, since you must supply an answer, any other way of answering decreases the security of the account. That type of measure is a security weakness tolerated for economic reasons, we may not be able to refuse using it but at least it is possible to avoid it&#8217;s inherent risk.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joseph Bonneau</title>
		<link>http://www.lightbluetouchpaper.org/2010/03/04/evaluating-statistical-attacks-on-personal-knowledge-questions/comment-page-1/#comment-50549</link>
		<dc:creator>Joseph Bonneau</dc:creator>
		<pubDate>Thu, 04 Mar 2010 17:29:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/?p=1879#comment-50549</guid>
		<description>@Clive

Very good comments. I agree that requiring more than one question is a nice improvement, though I&#039;ve rarely seen this done. One problem is that it can be hard to come up with a large number of questions (since many don&#039;t apply to some individuals), and users pick terrible questions when left to their own devices. An interesting idea is to pick dozens of yes/no questions like &quot;do you like country music?&quot;: http://www.ravenwhite.com/files/quantifying.pdf

Even in our paper we recommend some simple fixes if we can&#039;t change the current system-the answer distribution can be proactively shaped by the server by probabilistically rejecting the most common responses.

I&#039;m not sure the security increase is quite exponential though. Certain attacks (research and social engineering) don&#039;t get much harder to pull off for multiple questions than for one. Also, people&#039;s likelihood to forget the answer to one of the questions will go up exponentially.

There are a boatload of other problems as well: privacy of giving these answers away, and the fact that it&#039;s very hard to give different answers to different sites. Personally I think the whole personal knowledge approach is always going to be problematic. I&#039;d prefer vouching-based authentication (http://portal.acm.org/citation.cfm?doid=1180405.1180427) or using alternate channels like text message.

Someday maybe we&#039;ll combine all three, and add a few more in. It depends on how serious people care about webmail security, but the trend is that it&#039;s getting more and more important and protecting it with just one basic question seems like a relic of the early days of the internet.</description>
		<content:encoded><![CDATA[<p>@Clive</p>
<p>Very good comments. I agree that requiring more than one question is a nice improvement, though I&#8217;ve rarely seen this done. One problem is that it can be hard to come up with a large number of questions (since many don&#8217;t apply to some individuals), and users pick terrible questions when left to their own devices. An interesting idea is to pick dozens of yes/no questions like &#8220;do you like country music?&#8221;: <a href="http://www.ravenwhite.com/files/quantifying.pdf" rel="nofollow">http://www.ravenwhite.com/files/quantifying.pdf</a></p>
<p>Even in our paper we recommend some simple fixes if we can&#8217;t change the current system-the answer distribution can be proactively shaped by the server by probabilistically rejecting the most common responses.</p>
<p>I&#8217;m not sure the security increase is quite exponential though. Certain attacks (research and social engineering) don&#8217;t get much harder to pull off for multiple questions than for one. Also, people&#8217;s likelihood to forget the answer to one of the questions will go up exponentially.</p>
<p>There are a boatload of other problems as well: privacy of giving these answers away, and the fact that it&#8217;s very hard to give different answers to different sites. Personally I think the whole personal knowledge approach is always going to be problematic. I&#8217;d prefer vouching-based authentication (<a href="http://portal.acm.org/citation.cfm?doid=1180405.1180427" rel="nofollow">http://portal.acm.org/citation.cfm?doid=1180405.1180427</a>) or using alternate channels like text message.</p>
<p>Someday maybe we&#8217;ll combine all three, and add a few more in. It depends on how serious people care about webmail security, but the trend is that it&#8217;s getting more and more important and protecting it with just one basic question seems like a relic of the early days of the internet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clive Robinson</title>
		<link>http://www.lightbluetouchpaper.org/2010/03/04/evaluating-statistical-attacks-on-personal-knowledge-questions/comment-page-1/#comment-50534</link>
		<dc:creator>Clive Robinson</dc:creator>
		<pubDate>Thu, 04 Mar 2010 12:22:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/?p=1879#comment-50534</guid>
		<description>The reason that such questions have had traction is fairly easy to answer ;)

&quot;The failings of humans in general&quot;

We lose things easily including our memories and we also have difficulty remembering anything except by association.

And it is this that in all likely hood gives rise to Zipf (linear on log log axis) behaviour.

However the real question after &quot;proving the and quantifying common knowledge&quot; (ie it&#039;s a broken system only more broken than we guessed) is what do we do about it...

And the answer I suspect will be bassed on &quot;live with it&quot; or &quot;work with it&quot;.

Currently we are talking about one security question giving 2^8 bits of security, however what about 2 independent questions where both questions have to be answered before any indication of correctness or incorectness is given.

I would guess that most humans could stretch to 4 questions.

The question then arises what happens to the &quot;trawl technique&quot; and is there a more optimal attack on such a system.

The reason I say this is that it is a generaly held opinion (amongst security related practitioners) that a National ID is bad because although it can be seen as a strong authenticator (of it&#039;s self) it is a single point of attack (1 bad apple human) and proof of ID is better established with a wide range of weak authenticators.

That is the law of diminishing returns can work in your favor. 

This is most often seen in safety systems. For instance the effectivness of a seat belt increases linearly but at exponentialy increasing cost. Likewise the effectivness of an airbag increases linearly with exponentialy increasing cost. However you can beat the cost rise by putting an adiquate seatbelt and adiquate airbag effectivly in parellel and end up with a higher effectivness for less cost. Likewise adding sipps, crumple zones etc etc.

You can thus effectivly engineer a high safety value at a cost minima which is not possible any other way.

You see similar occuring with with high availability systems built with low reliability COTS systems worked in multiple redundancy to get availability figures up.

Any where you have a linear improvment for exponential cost increase on a single item is ripe for getting this sort of treatment, and these &quot;security questions&quot; are a prime example of where it might be brought to bare.

The downside of course is still humans who insist on putting their whole lives in the public record. But then there is &quot;no helping some people&quot; they will always &quot;shoot themselves in the foot&quot; even with an unloaded gun...</description>
		<content:encoded><![CDATA[<p>The reason that such questions have had traction is fairly easy to answer <img src='http://www.lightbluetouchpaper.org/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>&#8220;The failings of humans in general&#8221;</p>
<p>We lose things easily including our memories and we also have difficulty remembering anything except by association.</p>
<p>And it is this that in all likely hood gives rise to Zipf (linear on log log axis) behaviour.</p>
<p>However the real question after &#8220;proving the and quantifying common knowledge&#8221; (ie it&#8217;s a broken system only more broken than we guessed) is what do we do about it&#8230;</p>
<p>And the answer I suspect will be bassed on &#8220;live with it&#8221; or &#8220;work with it&#8221;.</p>
<p>Currently we are talking about one security question giving 2^8 bits of security, however what about 2 independent questions where both questions have to be answered before any indication of correctness or incorectness is given.</p>
<p>I would guess that most humans could stretch to 4 questions.</p>
<p>The question then arises what happens to the &#8220;trawl technique&#8221; and is there a more optimal attack on such a system.</p>
<p>The reason I say this is that it is a generaly held opinion (amongst security related practitioners) that a National ID is bad because although it can be seen as a strong authenticator (of it&#8217;s self) it is a single point of attack (1 bad apple human) and proof of ID is better established with a wide range of weak authenticators.</p>
<p>That is the law of diminishing returns can work in your favor. </p>
<p>This is most often seen in safety systems. For instance the effectivness of a seat belt increases linearly but at exponentialy increasing cost. Likewise the effectivness of an airbag increases linearly with exponentialy increasing cost. However you can beat the cost rise by putting an adiquate seatbelt and adiquate airbag effectivly in parellel and end up with a higher effectivness for less cost. Likewise adding sipps, crumple zones etc etc.</p>
<p>You can thus effectivly engineer a high safety value at a cost minima which is not possible any other way.</p>
<p>You see similar occuring with with high availability systems built with low reliability COTS systems worked in multiple redundancy to get availability figures up.</p>
<p>Any where you have a linear improvment for exponential cost increase on a single item is ripe for getting this sort of treatment, and these &#8220;security questions&#8221; are a prime example of where it might be brought to bare.</p>
<p>The downside of course is still humans who insist on putting their whole lives in the public record. But then there is &#8220;no helping some people&#8221; they will always &#8220;shoot themselves in the foot&#8221; even with an unloaded gun&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Allison Nighswander</title>
		<link>http://www.lightbluetouchpaper.org/2010/03/04/evaluating-statistical-attacks-on-personal-knowledge-questions/comment-page-1/#comment-50508</link>
		<dc:creator>Allison Nighswander</dc:creator>
		<pubDate>Thu, 04 Mar 2010 04:37:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/?p=1879#comment-50508</guid>
		<description>I have been saying that security questions are not secure because of how easy it would be to figure out the answers, especially when it sometimes is a matter of public record and anyone can look it up. As a tip, I generally produce a &#039;random&#039; set of characters as the answers so it&#039;s not easily guessable.</description>
		<content:encoded><![CDATA[<p>I have been saying that security questions are not secure because of how easy it would be to figure out the answers, especially when it sometimes is a matter of public record and anyone can look it up. As a tip, I generally produce a &#8216;random&#8217; set of characters as the answers so it&#8217;s not easily guessable.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
