<?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: Nikon Image Authentication System: Compromised</title>
	<atom:link href="http://blog.crackpassword.com/2011/04/nikon-image-authentication-system-compromised/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.crackpassword.com/2011/04/nikon-image-authentication-system-compromised/</link>
	<description>«...This blog is about &#60;a href=&#34;/?s=password+recovery&#34;&#62;cracking passwords&#60;/a&#62;, &#60;a href=&#34;/?s=forensic&#34;&#62;forensics solutions&#60;/a&#62;,&#60;br&#62;&#60;a href=&#34;/?s=security&#34;&#62;computer and network security&#60;/a&#62;, &#60;a href=&#34;/?s=system+recovery&#34;&#62;system recovery&#60;/a&#62; and other things...»</description>
	<lastBuildDate>Fri, 26 Apr 2013 14:47:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: cybernion</title>
		<link>http://blog.crackpassword.com/2011/04/nikon-image-authentication-system-compromised/comment-page-1/#comment-23293</link>
		<dc:creator>cybernion</dc:creator>
		<pubDate>Mon, 23 May 2011 23:52:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.crackpassword.com/?p=1595#comment-23293</guid>
		<description><![CDATA[I would like to know how the key was extracted.  Perhaps it was using side-channel analysis.  In that case, there are (patented) countermeasures that are known to provide a very strong resistance.  If it was a protocol error the fix may be even easier.

It sounds as if Nikon was using the same private key in all their cameras... a fundamental mistake.  The approach mentioned by MaHuJa (May22) using unique certified keys would be much better.  Tamper evidence is also a good suggestion, though not a perfect solution, because what do you do when a camera is legitimately lost or destroyed? 

While perfect security is impossible, practical security is doable.  It seems like these camera companies need to hire some good outside consultants to help them do it right.]]></description>
		<content:encoded><![CDATA[<p>I would like to know how the key was extracted.  Perhaps it was using side-channel analysis.  In that case, there are (patented) countermeasures that are known to provide a very strong resistance.  If it was a protocol error the fix may be even easier.</p>
<p>It sounds as if Nikon was using the same private key in all their cameras&#8230; a fundamental mistake.  The approach mentioned by MaHuJa (May22) using unique certified keys would be much better.  Tamper evidence is also a good suggestion, though not a perfect solution, because what do you do when a camera is legitimately lost or destroyed? </p>
<p>While perfect security is impossible, practical security is doable.  It seems like these camera companies need to hire some good outside consultants to help them do it right.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MaHuJa</title>
		<link>http://blog.crackpassword.com/2011/04/nikon-image-authentication-system-compromised/comment-page-1/#comment-23287</link>
		<dc:creator>MaHuJa</dc:creator>
		<pubDate>Sun, 22 May 2011 18:52:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.crackpassword.com/?p=1595#comment-23287</guid>
		<description><![CDATA[&gt;I think Elcomsoft is too strict and too harsh versus the digicam vendors.

If I risk going to jail based on falsified evidence, backed by their claims, then no. 

If we then go by your statement of difficulty, the correct response is not to do it at all.

However,
If each produced camera has its own key (whose certificate is signed by a master cert of theirs) and the key can&#039;t be extracted without leaving detectable traces on the camera, then we&#039;re starting to get somewhere. The camera itself would have to be submitted as part of the evidence. Also, the verifiers would have to say which camera s/n it was taken with, and add a disclaimer &quot;unless that camera has been tampered with&quot;. Which makes it near worthless if you can&#039;t have access to the original camera. Or one can tamper with it undetectably.]]></description>
		<content:encoded><![CDATA[<p>&gt;I think Elcomsoft is too strict and too harsh versus the digicam vendors.</p>
<p>If I risk going to jail based on falsified evidence, backed by their claims, then no. </p>
<p>If we then go by your statement of difficulty, the correct response is not to do it at all.</p>
<p>However,<br />
If each produced camera has its own key (whose certificate is signed by a master cert of theirs) and the key can&#8217;t be extracted without leaving detectable traces on the camera, then we&#8217;re starting to get somewhere. The camera itself would have to be submitted as part of the evidence. Also, the verifiers would have to say which camera s/n it was taken with, and add a disclaimer &#8220;unless that camera has been tampered with&#8221;. Which makes it near worthless if you can&#8217;t have access to the original camera. Or one can tamper with it undetectably.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: daniel</title>
		<link>http://blog.crackpassword.com/2011/04/nikon-image-authentication-system-compromised/comment-page-1/#comment-23132</link>
		<dc:creator>daniel</dc:creator>
		<pubDate>Fri, 29 Apr 2011 16:57:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.crackpassword.com/?p=1595#comment-23132</guid>
		<description><![CDATA[Truth is out there at elcomsoft. :)

 By the way please make new benchmarks with new gpus from nvidia and amd(590&amp;6990)
 for password recovery tools.

 Warmly regards]]></description>
		<content:encoded><![CDATA[<p>Truth is out there at elcomsoft. <img src='http://blog.crackpassword.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p> By the way please make new benchmarks with new gpus from nvidia and amd(590&amp;6990)<br />
 for password recovery tools.</p>
<p> Warmly regards</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kosullivan</title>
		<link>http://blog.crackpassword.com/2011/04/nikon-image-authentication-system-compromised/comment-page-1/#comment-23130</link>
		<dc:creator>kosullivan</dc:creator>
		<pubDate>Fri, 29 Apr 2011 08:46:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.crackpassword.com/?p=1595#comment-23130</guid>
		<description><![CDATA[Nice work!

This is what you get for implementing your own crypto. My suggestion to both Nikon and Canon is to include an ISO-7816 ID-000 port in their cameras (more commonly known as the SIM slot in mobile phones) and support one of the well-defined standards for public key operations on smartcards (PKCS#11 for example).

This means they have far less pressure to build a robust cryptographic system as it is built-in to the many, many compliant and certified smartcards out there in the market. Instead they can concentrate on the much simpler problem of using the crypto functions properly.

The major added benefit is that customers with strict security requirements (i.e. law enforcement) don&#039;t have to trust the crypto engines/key storage mechanisms developed by their camera supplier. They can put their own (trusted) smart-cards in the camera as simply as swapping a SIM in a mobile phone. For customers that don&#039;t want this, they can simply trust the default smartcards supplied with the camera.

Cheers,
Ko]]></description>
		<content:encoded><![CDATA[<p>Nice work!</p>
<p>This is what you get for implementing your own crypto. My suggestion to both Nikon and Canon is to include an ISO-7816 ID-000 port in their cameras (more commonly known as the SIM slot in mobile phones) and support one of the well-defined standards for public key operations on smartcards (PKCS#11 for example).</p>
<p>This means they have far less pressure to build a robust cryptographic system as it is built-in to the many, many compliant and certified smartcards out there in the market. Instead they can concentrate on the much simpler problem of using the crypto functions properly.</p>
<p>The major added benefit is that customers with strict security requirements (i.e. law enforcement) don&#8217;t have to trust the crypto engines/key storage mechanisms developed by their camera supplier. They can put their own (trusted) smart-cards in the camera as simply as swapping a SIM in a mobile phone. For customers that don&#8217;t want this, they can simply trust the default smartcards supplied with the camera.</p>
<p>Cheers,<br />
Ko</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kosullivan</title>
		<link>http://blog.crackpassword.com/2011/04/nikon-image-authentication-system-compromised/comment-page-1/#comment-23129</link>
		<dc:creator>kosullivan</dc:creator>
		<pubDate>Fri, 29 Apr 2011 08:37:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.crackpassword.com/?p=1595#comment-23129</guid>
		<description><![CDATA[This is what you get for implementing your own crypto. My suggestion to both Nikon and Canon is to include an ISO-7816 ID-000 port in their cameras (more commonly known as a SIM slot in mobile phones) and support one of the well-defined standards for public key operations on smartcards (PKCS#11 for example).

This means that Nikon/Canon have far less pressure to build a robust cryptographic system as it is built-in to the many, many compliant and certified smartcards out there in the market. Instead they can concentrate on the much simpler problem of implementing the crypto according to the standard.

The major added benefit is that customers with strict security requirements (i.e. law enforcement) don&#039;t have to trust the crypto engines/key storage mechanisms developed by Nikon/Canon. They can put their own (trusted) smart-cards in the camera as simply as swapping a SIM in a mobile phone.

For customers that don&#039;t want this, they can simply trust the default smartcards supplied by Canon/Nikon.

Customers, put pressure on them!
Cheers,
Ko]]></description>
		<content:encoded><![CDATA[<p>This is what you get for implementing your own crypto. My suggestion to both Nikon and Canon is to include an ISO-7816 ID-000 port in their cameras (more commonly known as a SIM slot in mobile phones) and support one of the well-defined standards for public key operations on smartcards (PKCS#11 for example).</p>
<p>This means that Nikon/Canon have far less pressure to build a robust cryptographic system as it is built-in to the many, many compliant and certified smartcards out there in the market. Instead they can concentrate on the much simpler problem of implementing the crypto according to the standard.</p>
<p>The major added benefit is that customers with strict security requirements (i.e. law enforcement) don&#8217;t have to trust the crypto engines/key storage mechanisms developed by Nikon/Canon. They can put their own (trusted) smart-cards in the camera as simply as swapping a SIM in a mobile phone.</p>
<p>For customers that don&#8217;t want this, they can simply trust the default smartcards supplied by Canon/Nikon.</p>
<p>Customers, put pressure on them!<br />
Cheers,<br />
Ko</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tamas Feher</title>
		<link>http://blog.crackpassword.com/2011/04/nikon-image-authentication-system-compromised/comment-page-1/#comment-23127</link>
		<dc:creator>Tamas Feher</dc:creator>
		<pubDate>Fri, 29 Apr 2011 06:12:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.crackpassword.com/?p=1595#comment-23127</guid>
		<description><![CDATA[Hello, I think Elcomsoft is too strict and too harsh versus the digicam vendors.

It is not possible to design a secure device at all, if the private key is stored in the device. An adversary advanced enough will have superb lab gear, including a scanning tunneling electron microscope and can sort through the integrated circuits atom by atom, if necessary. The key will be retrieved eventually.

Even if that does not work, the attacker could monitor power consumption or other side channel signals to deduce the keys. It is not reasonable to except a commercial digital camera to have TEMPEST features en par with a KH-11 spy satellite!

I think photo authenticity should be provided by special digicams, which also shoot a 135mm common film frame, in addition to the higher quality CCD/CMOS digital image. Chemical based roll film megative contains an almost infinite amount of information, so experts could you use it determine or exclude fakery.

Kind regards, Tamas.]]></description>
		<content:encoded><![CDATA[<p>Hello, I think Elcomsoft is too strict and too harsh versus the digicam vendors.</p>
<p>It is not possible to design a secure device at all, if the private key is stored in the device. An adversary advanced enough will have superb lab gear, including a scanning tunneling electron microscope and can sort through the integrated circuits atom by atom, if necessary. The key will be retrieved eventually.</p>
<p>Even if that does not work, the attacker could monitor power consumption or other side channel signals to deduce the keys. It is not reasonable to except a commercial digital camera to have TEMPEST features en par with a KH-11 spy satellite!</p>
<p>I think photo authenticity should be provided by special digicams, which also shoot a 135mm common film frame, in addition to the higher quality CCD/CMOS digital image. Chemical based roll film megative contains an almost infinite amount of information, so experts could you use it determine or exclude fakery.</p>
<p>Kind regards, Tamas.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gareth Coleman</title>
		<link>http://blog.crackpassword.com/2011/04/nikon-image-authentication-system-compromised/comment-page-1/#comment-23121</link>
		<dc:creator>Gareth Coleman</dc:creator>
		<pubDate>Thu, 28 Apr 2011 10:42:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.crackpassword.com/?p=1595#comment-23121</guid>
		<description><![CDATA[Great work guys, keep it up.

BTW I saw on Canon site a small advisory for owners to contact them, see here: http://www.canon-europe.com/Support/Consumer_Products/products/cameras/Accessories_Battery_Grips_etc/OSK-E3.aspx?type=important&amp;faqtcmuri=tcm:13-812833

So I think you should update your pages on the canon and nikon issues to state that Canon has made a low-profile appeal to owners to contact them for more information about the vulnerability.

They continue to sell the thing with promises of security though, despite you proving it doesn&#039;t.

Kind regards

Gareth]]></description>
		<content:encoded><![CDATA[<p>Great work guys, keep it up.</p>
<p>BTW I saw on Canon site a small advisory for owners to contact them, see here: <a href="http://www.canon-europe.com/Support/Consumer_Products/products/cameras/Accessories_Battery_Grips_etc/OSK-E3.aspx?type=important&#038;faqtcmuri=tcm:13-812833" rel="nofollow">http://www.canon-europe.com/Support/Consumer_Products/products/cameras/Accessories_Battery_Grips_etc/OSK-E3.aspx?type=important&#038;faqtcmuri=tcm:13-812833</a></p>
<p>So I think you should update your pages on the canon and nikon issues to state that Canon has made a low-profile appeal to owners to contact them for more information about the vulnerability.</p>
<p>They continue to sell the thing with promises of security though, despite you proving it doesn&#8217;t.</p>
<p>Kind regards</p>
<p>Gareth</p>
]]></content:encoded>
	</item>
</channel>
</rss>
