<?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: Atmels säkerhetsminne CryptoMemory</title>
	<atom:link href="http://strombergson.com/kryptoblog/2007/10/02/atmels-cryptomemory/feed/" rel="self" type="application/rss+xml" />
	<link>http://strombergson.com/kryptoblog/2007/10/02/atmels-cryptomemory/</link>
	<description>Kryptografi och IT-säkerhet på svenska</description>
	<pubDate>Thu, 08 Jan 2009 18:54:35 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Kryptoblog &#187; Blog Archive &#187; Bakdörr in Atmels CryptoMemory</title>
		<link>http://strombergson.com/kryptoblog/2007/10/02/atmels-cryptomemory/#comment-19750</link>
		<dc:creator>Kryptoblog &#187; Blog Archive &#187; Bakdörr in Atmels CryptoMemory</dc:creator>
		<pubDate>Wed, 13 Feb 2008 21:39:24 +0000</pubDate>
		<guid isPermaLink="false">http://strombergson.com/kryptoblog/2007/10/02/atmels-cryptomemory/#comment-19750</guid>
		<description>[...] CryptoMemory är ett litet minne med autenticiering och säkerhetsmekanismer avsedda att skydda innehållet i minnet. Tyvärr har det varit lite skralt med informationen om hur säkerhetsmekanismerna egentligen [...]</description>
		<content:encoded><![CDATA[<p>[...] CryptoMemory är ett litet minne med autenticiering och säkerhetsmekanismer avsedda att skydda innehållet i minnet. Tyvärr har det varit lite skralt med informationen om hur säkerhetsmekanismerna egentligen [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joachim</title>
		<link>http://strombergson.com/kryptoblog/2007/10/02/atmels-cryptomemory/#comment-19748</link>
		<dc:creator>Joachim</dc:creator>
		<pubDate>Wed, 13 Feb 2008 21:13:51 +0000</pubDate>
		<guid isPermaLink="false">http://strombergson.com/kryptoblog/2007/10/02/atmels-cryptomemory/#comment-19748</guid>
		<description>Aloha!

Actually it is very much in line and spot on! I'll post about it directly.
Big thanks for posting the heads up!
</description>
		<content:encoded><![CDATA[<p>Aloha!</p>
<p>Actually it is very much in line and spot on! I&#8217;ll post about it directly.<br />
Big thanks for posting the heads up!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Flylogic</title>
		<link>http://strombergson.com/kryptoblog/2007/10/02/atmels-cryptomemory/#comment-19745</link>
		<dc:creator>Flylogic</dc:creator>
		<pubDate>Wed, 13 Feb 2008 20:14:48 +0000</pubDate>
		<guid isPermaLink="false">http://strombergson.com/kryptoblog/2007/10/02/atmels-cryptomemory/#comment-19745</guid>
		<description>If this post is out of line, please excuse.

We have just posted about a backdoor found in Atmel CryptoMemory parts AT88SC153 and AT88SC1608!!!

http://www.flylogic.net/blog/?p=25</description>
		<content:encoded><![CDATA[<p>If this post is out of line, please excuse.</p>
<p>We have just posted about a backdoor found in Atmel CryptoMemory parts AT88SC153 and AT88SC1608!!!</p>
<p><a href="http://www.flylogic.net/blog/?p=25" rel="nofollow">http://www.flylogic.net/blog/?p=25</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Flylogic</title>
		<link>http://strombergson.com/kryptoblog/2007/10/02/atmels-cryptomemory/#comment-19005</link>
		<dc:creator>Flylogic</dc:creator>
		<pubDate>Fri, 01 Feb 2008 04:45:40 +0000</pubDate>
		<guid isPermaLink="false">http://strombergson.com/kryptoblog/2007/10/02/atmels-cryptomemory/#comment-19005</guid>
		<description>Yes I will Joachim!  Once it's over (Feb 21st).  The title is, "Security Failures In Secure Devices".  I talk about smartcard IC's, CryptoMemory, Keeloq, PolySi fuses, some MCU's that offer USB used in dongles, and then a dongle I haven't talked about yet on website ;).

Thanks!
Chris</description>
		<content:encoded><![CDATA[<p>Yes I will Joachim!  Once it&#8217;s over (Feb 21st).  The title is, &#8220;Security Failures In Secure Devices&#8221;.  I talk about smartcard IC&#8217;s, CryptoMemory, Keeloq, PolySi fuses, some MCU&#8217;s that offer USB used in dongles, and then a dongle I haven&#8217;t talked about yet on website ;).</p>
<p>Thanks!<br />
Chris</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joachim</title>
		<link>http://strombergson.com/kryptoblog/2007/10/02/atmels-cryptomemory/#comment-18989</link>
		<dc:creator>Joachim</dc:creator>
		<pubDate>Thu, 31 Jan 2008 19:22:15 +0000</pubDate>
		<guid isPermaLink="false">http://strombergson.com/kryptoblog/2007/10/02/atmels-cryptomemory/#comment-18989</guid>
		<description>Aloha!

Chris, will you be publishing the presentation from Blackhat after the event. If you do I would love to post an entry with a link to it. You have a great site btw!</description>
		<content:encoded><![CDATA[<p>Aloha!</p>
<p>Chris, will you be publishing the presentation from Blackhat after the event. If you do I would love to post an entry with a link to it. You have a great site btw!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Flylogic</title>
		<link>http://strombergson.com/kryptoblog/2007/10/02/atmels-cryptomemory/#comment-18965</link>
		<dc:creator>Flylogic</dc:creator>
		<pubDate>Thu, 31 Jan 2008 02:37:57 +0000</pubDate>
		<guid isPermaLink="false">http://strombergson.com/kryptoblog/2007/10/02/atmels-cryptomemory/#comment-18965</guid>
		<description>Hi,

I (owner of Flylogic) Chris Tarnovsky will be talking at Blackhat DC 2008.  I will discuss the weakness of the CryptoMemory such as abuse of address fetch to read out Write7 password (master password) and ability to reset the "fuses" with UV light (but watch out for booby trap fuses).

Databus attacks are easy to do with 64 samples on the bus you know the write7 password.  All contents of CryptoMemory are stored in the clear (no type of encryption at all inside the memory).

Databus on 350nm and 500nm is easy to touch with a needle ;-).

We will write up on I think AT88SC102 very soon.  It seems "Lucy's Laundramat" is using this smartcards in Los Angeles heheheheheheheh.

Keep in touch!</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I (owner of Flylogic) Chris Tarnovsky will be talking at Blackhat DC 2008.  I will discuss the weakness of the CryptoMemory such as abuse of address fetch to read out Write7 password (master password) and ability to reset the &#8220;fuses&#8221; with UV light (but watch out for booby trap fuses).</p>
<p>Databus attacks are easy to do with 64 samples on the bus you know the write7 password.  All contents of CryptoMemory are stored in the clear (no type of encryption at all inside the memory).</p>
<p>Databus on 350nm and 500nm is easy to touch with a needle ;-).</p>
<p>We will write up on I think AT88SC102 very soon.  It seems &#8220;Lucy&#8217;s Laundramat&#8221; is using this smartcards in Los Angeles heheheheheheheh.</p>
<p>Keep in touch!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joachim</title>
		<link>http://strombergson.com/kryptoblog/2007/10/02/atmels-cryptomemory/#comment-18792</link>
		<dc:creator>Joachim</dc:creator>
		<pubDate>Sat, 26 Jan 2008 07:48:06 +0000</pubDate>
		<guid isPermaLink="false">http://strombergson.com/kryptoblog/2007/10/02/atmels-cryptomemory/#comment-18792</guid>
		<description>Aloha!

FlyLogic:
Welcome to Kryptoblog, your comment is probably the first item here not in Swedish. But you seem capable to decipher the Swedish Chef-language quite well. ;-)

Thanks for the info, very interesting information! Would you be able to elaborate on your analysis Atmels CryptoMemory chips?  I don't find any blogpost about it. Was there any protection mechanisms beside filler layers? In your estimate, how hard would it be to read out any data from the chips?

BTW: Thanks for a great blog. As an ASIC+security guy I find it real treat to read!</description>
		<content:encoded><![CDATA[<p>Aloha!</p>
<p>FlyLogic:<br />
Welcome to Kryptoblog, your comment is probably the first item here not in Swedish. But you seem capable to decipher the Swedish Chef-language quite well. <img src='http://strombergson.com/kryptoblog/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>Thanks for the info, very interesting information! Would you be able to elaborate on your analysis Atmels CryptoMemory chips?  I don&#8217;t find any blogpost about it. Was there any protection mechanisms beside filler layers? In your estimate, how hard would it be to read out any data from the chips?</p>
<p>BTW: Thanks for a great blog. As an ASIC+security guy I find it real treat to read!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Flylogic</title>
		<link>http://strombergson.com/kryptoblog/2007/10/02/atmels-cryptomemory/#comment-18779</link>
		<dc:creator>Flylogic</dc:creator>
		<pubDate>Fri, 25 Jan 2008 23:09:19 +0000</pubDate>
		<guid isPermaLink="false">http://strombergson.com/kryptoblog/2007/10/02/atmels-cryptomemory/#comment-18779</guid>
		<description>We have analyzed all of the Atmel CryptoMemories.  They were very easilly compromised.

Greets from San Diego, California!</description>
		<content:encoded><![CDATA[<p>We have analyzed all of the Atmel CryptoMemories.  They were very easilly compromised.</p>
<p>Greets from San Diego, California!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kryptoblog &#187; Blog Archive &#187; Flylogic en spännande blog</title>
		<link>http://strombergson.com/kryptoblog/2007/10/02/atmels-cryptomemory/#comment-16512</link>
		<dc:creator>Kryptoblog &#187; Blog Archive &#187; Flylogic en spännande blog</dc:creator>
		<pubDate>Thu, 22 Nov 2007 09:02:24 +0000</pubDate>
		<guid isPermaLink="false">http://strombergson.com/kryptoblog/2007/10/02/atmels-cryptomemory/#comment-16512</guid>
		<description>[...] annan krets Flylogic attackerat är Atmels CryptoMemory som jag tidigare bloggat om. Här är en bild på sådana chip plockade från sin vanliga miljö för bättre [...]</description>
		<content:encoded><![CDATA[<p>[...] annan krets Flylogic attackerat är Atmels CryptoMemory som jag tidigare bloggat om. Här är en bild på sådana chip plockade från sin vanliga miljö för bättre [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
