<?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: RFID Security and Stability</title>
	<atom:link href="http://www.news.software.coop/rfid-security-and-stability/20/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.news.software.coop/rfid-security-and-stability/20/</link>
	<description>What software.coop is doing and contemplating</description>
	<lastBuildDate>Thu, 09 Feb 2012 16:10:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: MJ Ray</title>
		<link>http://www.news.software.coop/rfid-security-and-stability/20/#comment-246</link>
		<dc:creator>MJ Ray</dc:creator>
		<pubDate>Mon, 18 Aug 2008 19:27:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.news.software.coop/?p=20#comment-246</guid>
		<description>Someone sent me this PDF of a Defcon presentation about fare card cracking http://tinyurl.com/63sbxm</description>
		<content:encoded><![CDATA[<p>Someone sent me this PDF of a Defcon presentation about fare card cracking <a href="http://tinyurl.com/63sbxm" rel="nofollow">http://tinyurl.com/63sbxm</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MJ Ray</title>
		<link>http://www.news.software.coop/rfid-security-and-stability/20/#comment-245</link>
		<dc:creator>MJ Ray</dc:creator>
		<pubDate>Tue, 12 Aug 2008 10:18:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.news.software.coop/?p=20#comment-245</guid>
		<description>Thanks for that JT!  It gives me a bit more info, but also confirms what I suspected about NXP being a bit secretive.</description>
		<content:encoded><![CDATA[<p>Thanks for that JT!  It gives me a bit more info, but also confirms what I suspected about NXP being a bit secretive.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Taylor</title>
		<link>http://www.news.software.coop/rfid-security-and-stability/20/#comment-244</link>
		<dc:creator>James Taylor</dc:creator>
		<pubDate>Thu, 07 Aug 2008 11:39:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.news.software.coop/?p=20#comment-244</guid>
		<description>I&#039;ld like to append http://www.computerworld.com/action/article.do?command=viewArticleBasic&amp;articleId=9069558 is a relativly good article on how/what the crack actually is.</description>
		<content:encoded><![CDATA[<p>I&#8217;ld like to append <a href="http://www.computerworld.com/action/article.do?command=viewArticleBasic&#038;articleId=9069558" rel="nofollow">http://www.computerworld.com/action/article.do?command=viewArticleBasic&#038;articleId=9069558</a> is a relativly good article on how/what the crack actually is.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Taylor</title>
		<link>http://www.news.software.coop/rfid-security-and-stability/20/#comment-243</link>
		<dc:creator>James Taylor</dc:creator>
		<pubDate>Thu, 07 Aug 2008 09:30:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.news.software.coop/?p=20#comment-243</guid>
		<description>Lo Sleffy.
  The Mifare crack is&#039;nt as bad as the media is raving about. What has happend is that they have managed to crack the basic cryptography in the Mifare chip - which means you might be able to read the data on the Mifare cards.
  Most implementations of systems using Mifare however use both a server component as well as the on-tag component - where Mifare is designed to have the value stored on the card, in the Oyster system, this is true, but they also store the value on the Server.
  When you are using offline nodes, it decrements the value until you run through an &quot;online&quot; node, where the server gets linked. If you use a cloned card, then the system will detect whenever you go through an &quot;online&quot; node - and in Oyster, most of the nodes are online iirc.
  The Mifare cracking dosn&#039;t make mifare solutions insecure - hell, a lot of solutions using mifare tags actually have their data readable with publically known keys.
  Whats made matters worse is that NXP has always been very secretive about how their Mifare cryptography works - I believe this is what stopped them getting their Mifare card accepted as NFC Type A(?) compatible, and also now, its caused this media backlash against them.

Best Regards
JT</description>
		<content:encoded><![CDATA[<p>Lo Sleffy.<br />
  The Mifare crack is&#8217;nt as bad as the media is raving about. What has happend is that they have managed to crack the basic cryptography in the Mifare chip &#8211; which means you might be able to read the data on the Mifare cards.<br />
  Most implementations of systems using Mifare however use both a server component as well as the on-tag component &#8211; where Mifare is designed to have the value stored on the card, in the Oyster system, this is true, but they also store the value on the Server.<br />
  When you are using offline nodes, it decrements the value until you run through an &#8220;online&#8221; node, where the server gets linked. If you use a cloned card, then the system will detect whenever you go through an &#8220;online&#8221; node &#8211; and in Oyster, most of the nodes are online iirc.<br />
  The Mifare cracking dosn&#8217;t make mifare solutions insecure &#8211; hell, a lot of solutions using mifare tags actually have their data readable with publically known keys.<br />
  Whats made matters worse is that NXP has always been very secretive about how their Mifare cryptography works &#8211; I believe this is what stopped them getting their Mifare card accepted as NFC Type A(?) compatible, and also now, its caused this media backlash against them.</p>
<p>Best Regards<br />
JT</p>
]]></content:encoded>
	</item>
</channel>
</rss>

