<?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: This Will Be Interesting</title>
	<atom:link href="http://timworstall.com/2008/03/05/this-will-be-interesting/feed/" rel="self" type="application/rss+xml" />
	<link>http://timworstall.com/2008/03/05/this-will-be-interesting/</link>
	<description>It is all obvious or trivial except...</description>
	<lastBuildDate>Sat, 11 Feb 2012 18:45:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: The Remittance MAn</title>
		<link>http://timworstall.com/2008/03/05/this-will-be-interesting/comment-page-1/#comment-8624</link>
		<dc:creator>The Remittance MAn</dc:creator>
		<pubDate>Thu, 06 Mar 2008 16:53:09 +0000</pubDate>
		<guid isPermaLink="false">http://timworstall.com/2008/03/05/this-will-be-interesting/#comment-8624</guid>
		<description>RM didn&#039;t say he&#039;d like that level of security, he just noted that for the concept to work, that&#039;s what might be necessary. 

There is one thing I did forget to mention: Here at the mine it usually takes two days for a simple swipe card ID to be issued - that&#039;s the time it takes for the system to process some fairly basic data. We only have two thousand employees and they are a fairly stable workforce. I wonder how long a system needed to process many thousands more contractor employees some arriving to do a few days work some for longer would take to process a significantly higher amount of data.</description>
		<content:encoded><![CDATA[<p>RM didn&#8217;t say he&#8217;d like that level of security, he just noted that for the concept to work, that&#8217;s what might be necessary. </p>
<p>There is one thing I did forget to mention: Here at the mine it usually takes two days for a simple swipe card ID to be issued &#8211; that&#8217;s the time it takes for the system to process some fairly basic data. We only have two thousand employees and they are a fairly stable workforce. I wonder how long a system needed to process many thousands more contractor employees some arriving to do a few days work some for longer would take to process a significantly higher amount of data.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Gillies</title>
		<link>http://timworstall.com/2008/03/05/this-will-be-interesting/comment-page-1/#comment-8616</link>
		<dc:creator>David Gillies</dc:creator>
		<pubDate>Thu, 06 Mar 2008 14:24:52 +0000</pubDate>
		<guid isPermaLink="false">http://timworstall.com/2008/03/05/this-will-be-interesting/#comment-8616</guid>
		<description>I don&#039;t think, even if physical security were as stringent as RM would like, that a biometric scheme of this magnitude is practicable. It&#039;s in the nature of Bayesian statistics for low individual error rates and scarce incidence of the thing you are testing for to cause lopsided errors. The two error conditions we are worried about in a biometric system are false negatives and false positives. A false negative is the case when someone who should be granted access is denied it. A false positive is when someone who should be denied access is granted it. In the one case it means someone who should be allowed on-site to be detained while his bona-fides are being checked. In the other case it means Abu bin Nasty being allowed in, where he can get up to mischief.

Let&#039;s say 1 in 100,000 people attempting to gain access to the site is a terrorist. Let us assume that the a priori probability of error (both kinds) is 1%, so that 99 times out of a hundred if a person is in the database, he will match, and 1% of the time that he is not in the database he will also match. What is the probability that if someone matches, he is a terrorist?

Using Bayes&#039; theorem:

M means match i.e. access granted
probability of being a terrorist P(T) = 0.00001
probability of being a worker i.e. not being a terrorist =  P(W) = 99999/100000
probability of giving a false match P(M&#124;T) = 0.01
probability of giving a true match P(M&#124;W) = 0.99
probability of a match regardless of other information P(M) = P(M&#124;T)P(T) + P(M&#124;W)P(W) = 0.98999

probability that, given a match, the person is a terrorist P(T&#124;M) = ((P(M&#124;T)P(T))/P(M) = ~ 10^-7

So far so good. Only one in ten million times does a bad guy get in by accident (until you consider that if there are 100,000 users of this system over some period of time, this might not be adequate).

But, what is the probability that someone who is denied access is in fact a worker who should be allowed in?

D = no match i.e. denied
Again, P(T) = 10^-5
P(W) = 99999/100000
P(D&#124;T) = 0.99
P(D&#124;W) = 0.01
P(D) = P(D&#124;T)P(T) + P(D&#124;W)P(W) = 0.0100098

P(W&#124;D) = ((P(D&#124;W)P(W))/P(D) = 0.999011

i.e &lt;i&gt;in the case where access is denied&lt;/i&gt;, 99.9% of the time it will be denied to a legitimate user, and only 0.0989% to a terrorist.

The scope for hold-ups and bypassing of the system that this might entail can only be imagined.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think, even if physical security were as stringent as RM would like, that a biometric scheme of this magnitude is practicable. It&#8217;s in the nature of Bayesian statistics for low individual error rates and scarce incidence of the thing you are testing for to cause lopsided errors. The two error conditions we are worried about in a biometric system are false negatives and false positives. A false negative is the case when someone who should be granted access is denied it. A false positive is when someone who should be denied access is granted it. In the one case it means someone who should be allowed on-site to be detained while his bona-fides are being checked. In the other case it means Abu bin Nasty being allowed in, where he can get up to mischief.</p>
<p>Let&#8217;s say 1 in 100,000 people attempting to gain access to the site is a terrorist. Let us assume that the a priori probability of error (both kinds) is 1%, so that 99 times out of a hundred if a person is in the database, he will match, and 1% of the time that he is not in the database he will also match. What is the probability that if someone matches, he is a terrorist?</p>
<p>Using Bayes&#8217; theorem:</p>
<p>M means match i.e. access granted<br />
probability of being a terrorist P(T) = 0.00001<br />
probability of being a worker i.e. not being a terrorist =  P(W) = 99999/100000<br />
probability of giving a false match P(M|T) = 0.01<br />
probability of giving a true match P(M|W) = 0.99<br />
probability of a match regardless of other information P(M) = P(M|T)P(T) + P(M|W)P(W) = 0.98999</p>
<p>probability that, given a match, the person is a terrorist P(T|M) = ((P(M|T)P(T))/P(M) = ~ 10^-7</p>
<p>So far so good. Only one in ten million times does a bad guy get in by accident (until you consider that if there are 100,000 users of this system over some period of time, this might not be adequate).</p>
<p>But, what is the probability that someone who is denied access is in fact a worker who should be allowed in?</p>
<p>D = no match i.e. denied<br />
Again, P(T) = 10^-5<br />
P(W) = 99999/100000<br />
P(D|T) = 0.99<br />
P(D|W) = 0.01<br />
P(D) = P(D|T)P(T) + P(D|W)P(W) = 0.0100098</p>
<p>P(W|D) = ((P(D|W)P(W))/P(D) = 0.999011</p>
<p>i.e <i>in the case where access is denied</i>, 99.9% of the time it will be denied to a legitimate user, and only 0.0989% to a terrorist.</p>
<p>The scope for hold-ups and bypassing of the system that this might entail can only be imagined.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Remittance Man</title>
		<link>http://timworstall.com/2008/03/05/this-will-be-interesting/comment-page-1/#comment-8576</link>
		<dc:creator>The Remittance Man</dc:creator>
		<pubDate>Thu, 06 Mar 2008 06:21:33 +0000</pubDate>
		<guid isPermaLink="false">http://timworstall.com/2008/03/05/this-will-be-interesting/#comment-8576</guid>
		<description>I&#039;m somewhat more intrigued as to how they are going to enforce this. Taking the place where I work as an example; we have a large area to secure and there is a strong legal requirment to keep the perimeter secure and intruder proof (on account of the explosives, big kit etc).  yet we still find holes in the fence and occasionally find the odd civilian or his cows wandering ariound inside the fence.  Short of laying minefields or building Berlin Wall II there&#039;s not a lot we can do. We certainly can&#039;t make the place airtight.

Now consider the olympic site. Spread over a much larger area(s) with many more entrances and constant changes of perimeters, activities, people and kit. I can&#039;t even begin to comprehend the scale of the nightmare whoever will become responsible for implementing this is about to face.

And that&#039;s before one adds the world&#039;s greatest guarrantor of clusterf**kery, Her Majesty&#039;s Government.

The system is doomed. 

Fortunately news of its failings will leak out and it will be yet another nail in the coffin of the proposed National ID Database.</description>
		<content:encoded><![CDATA[<p>I&#8217;m somewhat more intrigued as to how they are going to enforce this. Taking the place where I work as an example; we have a large area to secure and there is a strong legal requirment to keep the perimeter secure and intruder proof (on account of the explosives, big kit etc).  yet we still find holes in the fence and occasionally find the odd civilian or his cows wandering ariound inside the fence.  Short of laying minefields or building Berlin Wall II there&#8217;s not a lot we can do. We certainly can&#8217;t make the place airtight.</p>
<p>Now consider the olympic site. Spread over a much larger area(s) with many more entrances and constant changes of perimeters, activities, people and kit. I can&#8217;t even begin to comprehend the scale of the nightmare whoever will become responsible for implementing this is about to face.</p>
<p>And that&#8217;s before one adds the world&#8217;s greatest guarrantor of clusterf**kery, Her Majesty&#8217;s Government.</p>
<p>The system is doomed. </p>
<p>Fortunately news of its failings will leak out and it will be yet another nail in the coffin of the proposed National ID Database.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dearieme</title>
		<link>http://timworstall.com/2008/03/05/this-will-be-interesting/comment-page-1/#comment-8567</link>
		<dc:creator>dearieme</dc:creator>
		<pubDate>Wed, 05 Mar 2008 18:51:35 +0000</pubDate>
		<guid isPermaLink="false">http://timworstall.com/2008/03/05/this-will-be-interesting/#comment-8567</guid>
		<description>They&#039;re building workers, for God&#039;s sake.  Just photograph their bum cleavage.</description>
		<content:encoded><![CDATA[<p>They&#8217;re building workers, for God&#8217;s sake.  Just photograph their bum cleavage.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kay Tie</title>
		<link>http://timworstall.com/2008/03/05/this-will-be-interesting/comment-page-1/#comment-8554</link>
		<dc:creator>Kay Tie</dc:creator>
		<pubDate>Wed, 05 Mar 2008 13:31:56 +0000</pubDate>
		<guid isPermaLink="false">http://timworstall.com/2008/03/05/this-will-be-interesting/#comment-8554</guid>
		<description>Wikipedia should be dinged for having a URL with an apostrophe in it. At least we should be grateful that it&#039;s not a grocer&#039;s apostrophe.</description>
		<content:encoded><![CDATA[<p>Wikipedia should be dinged for having a URL with an apostrophe in it. At least we should be grateful that it&#8217;s not a grocer&#8217;s apostrophe.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kay Tie</title>
		<link>http://timworstall.com/2008/03/05/this-will-be-interesting/comment-page-1/#comment-8553</link>
		<dc:creator>Kay Tie</dc:creator>
		<pubDate>Wed, 05 Mar 2008 13:30:29 +0000</pubDate>
		<guid isPermaLink="false">http://timworstall.com/2008/03/05/this-will-be-interesting/#comment-8553</guid>
		<description>&quot;With reference to Kay Tie’s concerns about DNA, the worrying aspect for me is that DNA identification is completely out of the competence of the ordinary person.&quot;

Yes, it&#039;s true. It&#039;s sometimes outside the competence of the prosecution and defence. In fact, it&#039;s so common to misunderstand the meaning of DNA matches that there&#039;s a term for it: the Prosecutor&#039;s Fallacy.

http://en.wikipedia.org/wiki/Prosecutor&#039;s_fallacy</description>
		<content:encoded><![CDATA[<p>&#8220;With reference to Kay Tie’s concerns about DNA, the worrying aspect for me is that DNA identification is completely out of the competence of the ordinary person.&#8221;</p>
<p>Yes, it&#8217;s true. It&#8217;s sometimes outside the competence of the prosecution and defence. In fact, it&#8217;s so common to misunderstand the meaning of DNA matches that there&#8217;s a term for it: the Prosecutor&#8217;s Fallacy.</p>
<p><a href="http://en.wikipedia.org/wiki/Prosecutor&#039;s_fallacy" rel="nofollow">http://en.wikipedia.org/wiki/Prosecutor&#039;s_fallacy</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pj</title>
		<link>http://timworstall.com/2008/03/05/this-will-be-interesting/comment-page-1/#comment-8549</link>
		<dc:creator>pj</dc:creator>
		<pubDate>Wed, 05 Mar 2008 12:31:33 +0000</pubDate>
		<guid isPermaLink="false">http://timworstall.com/2008/03/05/this-will-be-interesting/#comment-8549</guid>
		<description>With reference to Kay Tie&#039;s concerns about DNA, the  worrying aspect for me is that DNA identification is completely out of the competence of the ordinary person.
With finger print evidence, its quite possible for a member of a jury to make an independent assessment of the validity of the evidence. Does the print of suspect &#039;A&#039; look similar to the print on murder weapon &#039;X&#039;? The materials &amp; the techniques used are easily comprehended &amp; could even be reproduced in court given a stamp pad &amp; a piece of paper.
With DNA the evidence can only be understood by a lab technician. It could just as easily prove that a bird crapped in both places. So what a jury has to decide is not the reliability of the evidence but the reliability of those providing the evidence.</description>
		<content:encoded><![CDATA[<p>With reference to Kay Tie&#8217;s concerns about DNA, the  worrying aspect for me is that DNA identification is completely out of the competence of the ordinary person.<br />
With finger print evidence, its quite possible for a member of a jury to make an independent assessment of the validity of the evidence. Does the print of suspect &#8216;A&#8217; look similar to the print on murder weapon &#8216;X&#8217;? The materials &amp; the techniques used are easily comprehended &amp; could even be reproduced in court given a stamp pad &amp; a piece of paper.<br />
With DNA the evidence can only be understood by a lab technician. It could just as easily prove that a bird crapped in both places. So what a jury has to decide is not the reliability of the evidence but the reliability of those providing the evidence.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pj</title>
		<link>http://timworstall.com/2008/03/05/this-will-be-interesting/comment-page-1/#comment-8545</link>
		<dc:creator>pj</dc:creator>
		<pubDate>Wed, 05 Mar 2008 12:09:35 +0000</pubDate>
		<guid isPermaLink="false">http://timworstall.com/2008/03/05/this-will-be-interesting/#comment-8545</guid>
		<description>It would be of great interest to know whether the workers being scanned are on piece rate or day rate. 
If they&#039;re being paid by the job there will be a great incentive to either get the system to work or bypass it. The incentive will be supplied by a load of hulking contractors in big boots standing around on their own time whilst security cowers in its hut quivering in terror.
Conversely, if they&#039;re paid day rate, they&#039;ll be 100,000 minds working on the problem of crashing the system &#039;cause there&#039;s nothing  better than standing around reading the paper whilst you&#039;re being paid to do so.</description>
		<content:encoded><![CDATA[<p>It would be of great interest to know whether the workers being scanned are on piece rate or day rate.<br />
If they&#8217;re being paid by the job there will be a great incentive to either get the system to work or bypass it. The incentive will be supplied by a load of hulking contractors in big boots standing around on their own time whilst security cowers in its hut quivering in terror.<br />
Conversely, if they&#8217;re paid day rate, they&#8217;ll be 100,000 minds working on the problem of crashing the system &#8217;cause there&#8217;s nothing  better than standing around reading the paper whilst you&#8217;re being paid to do so.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kay Tie</title>
		<link>http://timworstall.com/2008/03/05/this-will-be-interesting/comment-page-1/#comment-8534</link>
		<dc:creator>Kay Tie</dc:creator>
		<pubDate>Wed, 05 Mar 2008 10:23:18 +0000</pubDate>
		<guid isPermaLink="false">http://timworstall.com/2008/03/05/this-will-be-interesting/#comment-8534</guid>
		<description>&quot;Image matching is tricky. You have to deal with the image not being an exact match, not placed in the same location. And in the case of this database, you’ve got to match it against potentially 100,000 records?&quot;

I assume palm prints are more accurate than fingerprints, but nevertheless, I bet it&#039;s not great. The chances of false match go up exponentially with database size.

It&#039;s all daft, really. What they need is not identification, but verification: carry an RFID token that makes the claim to an ID, and use palm prints to verify against the claimed ID (stored on the RFID with a suitable digital signature, if you like). That&#039;s easy because there&#039;s no issue with false matches (it&#039;s a simple yes/no determination).</description>
		<content:encoded><![CDATA[<p>&#8220;Image matching is tricky. You have to deal with the image not being an exact match, not placed in the same location. And in the case of this database, you’ve got to match it against potentially 100,000 records?&#8221;</p>
<p>I assume palm prints are more accurate than fingerprints, but nevertheless, I bet it&#8217;s not great. The chances of false match go up exponentially with database size.</p>
<p>It&#8217;s all daft, really. What they need is not identification, but verification: carry an RFID token that makes the claim to an ID, and use palm prints to verify against the claimed ID (stored on the RFID with a suitable digital signature, if you like). That&#8217;s easy because there&#8217;s no issue with false matches (it&#8217;s a simple yes/no determination).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kay Tie</title>
		<link>http://timworstall.com/2008/03/05/this-will-be-interesting/comment-page-1/#comment-8533</link>
		<dc:creator>Kay Tie</dc:creator>
		<pubDate>Wed, 05 Mar 2008 10:19:01 +0000</pubDate>
		<guid isPermaLink="false">http://timworstall.com/2008/03/05/this-will-be-interesting/#comment-8533</guid>
		<description>&quot; I wonder what assurances, and concerns as per the DNA database, there will be about these prints being added to the police records?&quot;

I&#039;m much less worried about it than DNA. The issues aren&#039;t much different to fingerprints, and the police have been keeping those since the 19th century. The problem I have with DNA is that it is easily subject to accidental and deliberate contamination, and that DNA potentially gives away all kinds of information the State shouldn&#039;t have access to.</description>
		<content:encoded><![CDATA[<p>&#8221; I wonder what assurances, and concerns as per the DNA database, there will be about these prints being added to the police records?&#8221;</p>
<p>I&#8217;m much less worried about it than DNA. The issues aren&#8217;t much different to fingerprints, and the police have been keeping those since the 19th century. The problem I have with DNA is that it is easily subject to accidental and deliberate contamination, and that DNA potentially gives away all kinds of information the State shouldn&#8217;t have access to.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Almond</title>
		<link>http://timworstall.com/2008/03/05/this-will-be-interesting/comment-page-1/#comment-8532</link>
		<dc:creator>Tim Almond</dc:creator>
		<pubDate>Wed, 05 Mar 2008 10:10:41 +0000</pubDate>
		<guid isPermaLink="false">http://timworstall.com/2008/03/05/this-will-be-interesting/#comment-8532</guid>
		<description>Has anyone done this before?

I&#039;ve had a read around and the police are working with handprint matching system, but the key thing there is that it doesn&#039;t have to be done too quickly. With something like ID systems, you want to be getting people through within a few seconds.

Image matching is tricky. You have to deal with the image not being an exact match, not placed in the same location. And in the case of this database, you&#039;ve got to match it against potentially 100,000 records?</description>
		<content:encoded><![CDATA[<p>Has anyone done this before?</p>
<p>I&#8217;ve had a read around and the police are working with handprint matching system, but the key thing there is that it doesn&#8217;t have to be done too quickly. With something like ID systems, you want to be getting people through within a few seconds.</p>
<p>Image matching is tricky. You have to deal with the image not being an exact match, not placed in the same location. And in the case of this database, you&#8217;ve got to match it against potentially 100,000 records?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ORAC</title>
		<link>http://timworstall.com/2008/03/05/this-will-be-interesting/comment-page-1/#comment-8531</link>
		<dc:creator>ORAC</dc:creator>
		<pubDate>Wed, 05 Mar 2008 10:08:55 +0000</pubDate>
		<guid isPermaLink="false">http://timworstall.com/2008/03/05/this-will-be-interesting/#comment-8531</guid>
		<description>I see the police have had a national palm print database for  2 years. I wonder what assurances, and concerns as per the DNA database, there will be about these prints being added to the police records?

http://www.silicon.com/publicsector/0,3800010403,39157511,00.htm</description>
		<content:encoded><![CDATA[<p>I see the police have had a national palm print database for  2 years. I wonder what assurances, and concerns as per the DNA database, there will be about these prints being added to the police records?</p>
<p><a href="http://www.silicon.com/publicsector/0,3800010403,39157511,00.htm" rel="nofollow">http://www.silicon.com/publicsector/0,3800010403,39157511,00.htm</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kay Tie</title>
		<link>http://timworstall.com/2008/03/05/this-will-be-interesting/comment-page-1/#comment-8524</link>
		<dc:creator>Kay Tie</dc:creator>
		<pubDate>Wed, 05 Mar 2008 09:32:10 +0000</pubDate>
		<guid isPermaLink="false">http://timworstall.com/2008/03/05/this-will-be-interesting/#comment-8524</guid>
		<description>&quot;I suspect that it will be an expensive disaster&quot;

Builders often don&#039;t have fingerprints (they wear off because of the handing of bricks etc.) and so palm prints are being proposed. But it will still be a disaster because it combines Government and IT.

Even if it works, it won&#039;t prove the ID card system will work: that uses fingerprints.</description>
		<content:encoded><![CDATA[<p>&#8220;I suspect that it will be an expensive disaster&#8221;</p>
<p>Builders often don&#8217;t have fingerprints (they wear off because of the handing of bricks etc.) and so palm prints are being proposed. But it will still be a disaster because it combines Government and IT.</p>
<p>Even if it works, it won&#8217;t prove the ID card system will work: that uses fingerprints.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced
Object Caching 390/394 objects using disk: basic

Served from: timworstall.com @ 2012-02-12 11:03:26 -->
