<?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: Chip-And-PIN Hack Is So Scary Because It Surprised No One</title>
	<atom:link href="http://storefrontbacktalk.com/securityfraud/chip-and-pin-hack-is-so-scary-because-it-surprised-no-one/feed/" rel="self" type="application/rss+xml" />
	<link>http://storefrontbacktalk.com/securityfraud/chip-and-pin-hack-is-so-scary-because-it-surprised-no-one/</link>
	<description>Techniques, Tools and Tirades about Retail Technology and E-Commerce</description>
	<lastBuildDate>Sun, 20 May 2012 01:49:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Howard</title>
		<link>http://storefrontbacktalk.com/securityfraud/chip-and-pin-hack-is-so-scary-because-it-surprised-no-one/comment-page-1/#comment-67279</link>
		<dc:creator>Howard</dc:creator>
		<pubDate>Tue, 23 Feb 2010 16:59:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.storefrontbacktalk.com/?p=4818#comment-67279</guid>
		<description>This hack has been available for over 8 years now. I doubt this should be a surprise to anyone.</description>
		<content:encoded><![CDATA[<p>This hack has been available for over 8 years now. I doubt this should be a surprise to anyone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Sommers</title>
		<link>http://storefrontbacktalk.com/securityfraud/chip-and-pin-hack-is-so-scary-because-it-surprised-no-one/comment-page-1/#comment-67278</link>
		<dc:creator>Steve Sommers</dc:creator>
		<pubDate>Tue, 23 Feb 2010 16:50:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.storefrontbacktalk.com/?p=4818#comment-67278</guid>
		<description>Was it undiscovered? And are we sure there are variations already in the wild? There have been many customer complaints of fraudulent activity with EMV and most were simply swept under the carpet and attributed to a failure of the cardholder without much investigation. Recently the EU shifted some of the burden of proof back to the banks and this was done prior to this Cambridge report. If the system is so secure, why the shift?</description>
		<content:encoded><![CDATA[<p>Was it undiscovered? And are we sure there are variations already in the wild? There have been many customer complaints of fraudulent activity with EMV and most were simply swept under the carpet and attributed to a failure of the cardholder without much investigation. Recently the EU shifted some of the burden of proof back to the banks and this was done prior to this Cambridge report. If the system is so secure, why the shift?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Dorf</title>
		<link>http://storefrontbacktalk.com/securityfraud/chip-and-pin-hack-is-so-scary-because-it-surprised-no-one/comment-page-1/#comment-67249</link>
		<dc:creator>David Dorf</dc:creator>
		<pubDate>Tue, 23 Feb 2010 03:12:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.storefrontbacktalk.com/?p=4818#comment-67249</guid>
		<description>Long ago I used to write code for smart card terminals, including those that accepted EMV cards.  Even with the imperfections, the chip-based systems are much more secure than mag-stripe.  The fact that this particular hole went undiscovered for at least six years is actually pretty impressive.  Although I don&#039;t know the specifics, I&#039;m willing to bet this particular issue can be resolved in the terminal code without having to reissue all the cards.  

This is a great example of the importance of ethical hacking.  Hats off to the Cambridge team.</description>
		<content:encoded><![CDATA[<p>Long ago I used to write code for smart card terminals, including those that accepted EMV cards.  Even with the imperfections, the chip-based systems are much more secure than mag-stripe.  The fact that this particular hole went undiscovered for at least six years is actually pretty impressive.  Although I don&#8217;t know the specifics, I&#8217;m willing to bet this particular issue can be resolved in the terminal code without having to reissue all the cards.  </p>
<p>This is a great example of the importance of ethical hacking.  Hats off to the Cambridge team.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A reader</title>
		<link>http://storefrontbacktalk.com/securityfraud/chip-and-pin-hack-is-so-scary-because-it-surprised-no-one/comment-page-1/#comment-67016</link>
		<dc:creator>A reader</dc:creator>
		<pubDate>Fri, 19 Feb 2010 02:40:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.storefrontbacktalk.com/?p=4818#comment-67016</guid>
		<description>Mr. Bittner,

How do you equate the failure of a developed-in-secret, 14-year-old cryptographic protocol with the adoption of object oriented programming, the recognition of design patterns, or the maturity of software engineering as a discipline?  You are comparing oranges to a philosopher&#039;s left elbow -- the argument doesn&#039;t even parse.

There were no software failures here, no code crashes being exploited nor buffer overrun attacks smashing stacks.  This was a failure in the design and creation of a *protocol* that fell prey to being spoofed.  No objects failed, because no objects were transmitted.  This is 100% protocol design failure; and it can be blamed on the secretive nature of the original design process and the immature cryptographic skills of the original protocol designers.  (Here&#039;s a hint for all you budding cryptographers:  the best cryptographers know they aren&#039;t good enough by themselves.  They always seek outside validation of their designs.  Always.)

The chips inside the smart cards don&#039;t even have the memory or the horsepower to support object oriented programming techniques.  There aren&#039;t dynamic memory allocations.  These are tiny 8-bit chips with about 1K of RAM, and the applications hand coded in assembler (or possibly C.)  

I&#039;m sorry if you are uncomfortable with modern design techniques, object oriented languages, test-driven development, design patterns, or if you think programming should still be functional now because it was functional back when you first learned it.  If you are interested in that kind of bare-metal programming, might I suggest embedded systems design?  It&#039;s all about writing code for these tiny standalone processors, where every byte still matters and every cycle still counts.  You even get style points for writing in assembler. :-)</description>
		<content:encoded><![CDATA[<p>Mr. Bittner,</p>
<p>How do you equate the failure of a developed-in-secret, 14-year-old cryptographic protocol with the adoption of object oriented programming, the recognition of design patterns, or the maturity of software engineering as a discipline?  You are comparing oranges to a philosopher&#8217;s left elbow &#8212; the argument doesn&#8217;t even parse.</p>
<p>There were no software failures here, no code crashes being exploited nor buffer overrun attacks smashing stacks.  This was a failure in the design and creation of a *protocol* that fell prey to being spoofed.  No objects failed, because no objects were transmitted.  This is 100% protocol design failure; and it can be blamed on the secretive nature of the original design process and the immature cryptographic skills of the original protocol designers.  (Here&#8217;s a hint for all you budding cryptographers:  the best cryptographers know they aren&#8217;t good enough by themselves.  They always seek outside validation of their designs.  Always.)</p>
<p>The chips inside the smart cards don&#8217;t even have the memory or the horsepower to support object oriented programming techniques.  There aren&#8217;t dynamic memory allocations.  These are tiny 8-bit chips with about 1K of RAM, and the applications hand coded in assembler (or possibly C.)  </p>
<p>I&#8217;m sorry if you are uncomfortable with modern design techniques, object oriented languages, test-driven development, design patterns, or if you think programming should still be functional now because it was functional back when you first learned it.  If you are interested in that kind of bare-metal programming, might I suggest embedded systems design?  It&#8217;s all about writing code for these tiny standalone processors, where every byte still matters and every cycle still counts.  You even get style points for writing in assembler. :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: R Dallaire</title>
		<link>http://storefrontbacktalk.com/securityfraud/chip-and-pin-hack-is-so-scary-because-it-surprised-no-one/comment-page-1/#comment-66931</link>
		<dc:creator>R Dallaire</dc:creator>
		<pubDate>Thu, 18 Feb 2010 16:15:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.storefrontbacktalk.com/?p=4818#comment-66931</guid>
		<description>Sure, you may hide all the cables but the setup will be obvious if you are wearing a T-Shirt. ;)

EMV has to fix this.  I don&#039;t know if the same issue has been raised in Canada.</description>
		<content:encoded><![CDATA[<p>Sure, you may hide all the cables but the setup will be obvious if you are wearing a T-Shirt. ;)</p>
<p>EMV has to fix this.  I don&#8217;t know if the same issue has been raised in Canada.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: R Dallaire</title>
		<link>http://storefrontbacktalk.com/securityfraud/chip-and-pin-hack-is-so-scary-because-it-surprised-no-one/comment-page-1/#comment-66926</link>
		<dc:creator>R Dallaire</dc:creator>
		<pubDate>Thu, 18 Feb 2010 16:08:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.storefrontbacktalk.com/?p=4818#comment-66926</guid>
		<description>I worked on EMV project in Canada.  EMV is better than plain MSR card.  No doubt. This is not marketing &quot;gimmick&quot;. 

The Cambridge/BBC video shows a guy using a Netbook PC and an EMV &quot;test card&quot; hooked on a stolen EMV card. Sure, you may hide all the cables</description>
		<content:encoded><![CDATA[<p>I worked on EMV project in Canada.  EMV is better than plain MSR card.  No doubt. This is not marketing &#8220;gimmick&#8221;. </p>
<p>The Cambridge/BBC video shows a guy using a Netbook PC and an EMV &#8220;test card&#8221; hooked on a stolen EMV card. Sure, you may hide all the cables</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bill bittner</title>
		<link>http://storefrontbacktalk.com/securityfraud/chip-and-pin-hack-is-so-scary-because-it-surprised-no-one/comment-page-1/#comment-66889</link>
		<dc:creator>bill bittner</dc:creator>
		<pubDate>Thu, 18 Feb 2010 14:11:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.storefrontbacktalk.com/?p=4818#comment-66889</guid>
		<description>This hack demonstrates a much larger vulnerability that goes way beyond payment authorization.  As software design has moved to “object oriented” designs that encapsulate data and processes along with the whole concept of “stateless objects” the “man in the middle” or wedge attack becomes much easier.  This could really happen in any situation.  Just as we are hearing more about cyber attacks from overseas, we are using software design techniques that make our systems more vulnerable.  Better get a kerosene lamp.</description>
		<content:encoded><![CDATA[<p>This hack demonstrates a much larger vulnerability that goes way beyond payment authorization.  As software design has moved to “object oriented” designs that encapsulate data and processes along with the whole concept of “stateless objects” the “man in the middle” or wedge attack becomes much easier.  This could really happen in any situation.  Just as we are hearing more about cyber attacks from overseas, we are using software design techniques that make our systems more vulnerable.  Better get a kerosene lamp.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

