<?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: Understanding the DNIe, Part I : Device Authentication</title>
	<atom:link href="http://www.limited-entropy.com/dnie-device-auth/feed" rel="self" type="application/rss+xml" />
	<link>http://www.limited-entropy.com/dnie-device-auth</link>
	<description>Not so random thoughts on security featured by Eloi Sanfèlix</description>
	<lastBuildDate>Mon, 30 Aug 2010 09:13:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Understanding the DNIe, Part III: Hashing and signing &#171; Limited Entropy Dot Com</title>
		<link>http://www.limited-entropy.com/dnie-device-auth/comment-page-1#comment-14131</link>
		<dc:creator>Understanding the DNIe, Part III: Hashing and signing &#171; Limited Entropy Dot Com</dc:creator>
		<pubDate>Tue, 27 Apr 2010 16:46:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.limited-entropy.com/?p=556#comment-14131</guid>
		<description>[...] I come with yet another post about the DNIe. In the previous posts, we have seen how the device authentication procedure works and how to use the resulting keys to perform secure messaging. Now it&#039;s time to see [...]</description>
		<content:encoded><![CDATA[<p>[...] I come with yet another post about the DNIe. In the previous posts, we have seen how the device authentication procedure works and how to use the resulting keys to perform secure messaging. Now it&#39;s time to see [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Understanding the DNIe, Part II : Secure Messaging &#171; Limited Entropy Dot Com</title>
		<link>http://www.limited-entropy.com/dnie-device-auth/comment-page-1#comment-13650</link>
		<dc:creator>Understanding the DNIe, Part II : Secure Messaging &#171; Limited Entropy Dot Com</dc:creator>
		<pubDate>Mon, 12 Apr 2010 00:56:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.limited-entropy.com/?p=556#comment-13650</guid>
		<description>[...] go a little further in our way to understand the way the DNIe works. In my previous post I talked about the device authentication procedure and today I&#039;ll talk about what happens next, how [...]</description>
		<content:encoded><![CDATA[<p>[...] go a little further in our way to understand the way the DNIe works. In my previous post I talked about the device authentication procedure and today I&#39;ll talk about what happens next, how [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Felipe</title>
		<link>http://www.limited-entropy.com/dnie-device-auth/comment-page-1#comment-13202</link>
		<dc:creator>Felipe</dc:creator>
		<pubDate>Sun, 21 Mar 2010 11:23:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.limited-entropy.com/?p=556#comment-13202</guid>
		<description>Thanks for the article.

I&#039;m trying to use DNIe for starting session (Gnome, KDE, ssh, ...) 
Any suggestion about how to do it? I&#039;ve found some documentation, but up to now, it has no worked.
I use opensuse 11.2 and Kubuntu 9.04.

  Thanks</description>
		<content:encoded><![CDATA[<p>Thanks for the article.</p>
<p>I&#8217;m trying to use DNIe for starting session (Gnome, KDE, ssh, &#8230;)<br />
Any suggestion about how to do it? I&#8217;ve found some documentation, but up to now, it has no worked.<br />
I use opensuse 11.2 and Kubuntu 9.04.</p>
<p>  Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Login with SmartCard - openSUSE Forums</title>
		<link>http://www.limited-entropy.com/dnie-device-auth/comment-page-1#comment-13192</link>
		<dc:creator>Login with SmartCard - openSUSE Forums</dc:creator>
		<pubDate>Sat, 20 Mar 2010 23:14:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.limited-entropy.com/?p=556#comment-13192</guid>
		<description>[...]  [...]</description>
		<content:encoded><![CDATA[<p>[...]  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KaR]V[aN</title>
		<link>http://www.limited-entropy.com/dnie-device-auth/comment-page-1#comment-12765</link>
		<dc:creator>KaR]V[aN</dc:creator>
		<pubDate>Sun, 07 Mar 2010 22:38:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.limited-entropy.com/?p=556#comment-12765</guid>
		<description>Seems to be pretty secure... I think.

Great article, can&#039;t wait for next one.</description>
		<content:encoded><![CDATA[<p>Seems to be pretty secure&#8230; I think.</p>
<p>Great article, can&#8217;t wait for next one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vierito5</title>
		<link>http://www.limited-entropy.com/dnie-device-auth/comment-page-1#comment-12704</link>
		<dc:creator>vierito5</dc:creator>
		<pubDate>Sat, 06 Mar 2010 00:35:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.limited-entropy.com/?p=556#comment-12704</guid>
		<description>Great post! I can&#039;t wait for further posts about DNIe and its implementation.

I hope this comment it&#039;s not caught again by Akismet&#039;s jaws</description>
		<content:encoded><![CDATA[<p>Great post! I can&#8217;t wait for further posts about DNIe and its implementation.</p>
<p>I hope this comment it&#8217;s not caught again by Akismet&#8217;s jaws</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eloi Sanfèlix</title>
		<link>http://www.limited-entropy.com/dnie-device-auth/comment-page-1#comment-12655</link>
		<dc:creator>Eloi Sanfèlix</dc:creator>
		<pubDate>Thu, 04 Mar 2010 18:24:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.limited-entropy.com/?p=556#comment-12655</guid>
		<description>@Alvaro yes, that&#039;s right. The IFD has its own 1024 bit RSA key pair, with a card verifiable certificate signed by the CA of the DNIe. 

AFAICT both linux and OS X versions of the drivers use the same certificate, which leads me to believe that ALL computers will use the same public/private key pair. 

So it&#039;s not very useful as an authentication mechanism actually...and I initially thought it would not be useful for protecting the privacy and integrity of the secure channel but now I think it actually is unless you hook the RNG of the driver and are able to discover the 32 byte random number the IFD picks. 

I&#039;d have to look more into it, but my current feeling is that eavesdropping a communication requires both knowing the private key and the random number sent by the IFD, while establishing a secure channel of your own only requires knowing the private key :roll:.

And yes, the IFD is the computer in this case... it&#039;s what the card sees &quot;on the other end&quot;, the logical entity that talks to the card using the iso7816 and the CWA 14980 protocols. 

Hence, it&#039;s the combination of reader+computer, since the reader implements the lower layers of the iso7816 stack (physical layer and link layer [T=0, T=1...] ) and the computer implements the upper layers.</description>
		<content:encoded><![CDATA[<p>@Alvaro yes, that&#8217;s right. The IFD has its own 1024 bit RSA key pair, with a card verifiable certificate signed by the CA of the DNIe. </p>
<p>AFAICT both linux and OS X versions of the drivers use the same certificate, which leads me to believe that ALL computers will use the same public/private key pair. </p>
<p>So it&#8217;s not very useful as an authentication mechanism actually&#8230;and I initially thought it would not be useful for protecting the privacy and integrity of the secure channel but now I think it actually is unless you hook the RNG of the driver and are able to discover the 32 byte random number the IFD picks. </p>
<p>I&#8217;d have to look more into it, but my current feeling is that eavesdropping a communication requires both knowing the private key and the random number sent by the IFD, while establishing a secure channel of your own only requires knowing the private key <img src='http://www.limited-entropy.com/wp-includes/images/smilies/icon_rolleyes.gif' alt=':roll:' class='wp-smiley' /> .</p>
<p>And yes, the IFD is the computer in this case&#8230; it&#8217;s what the card sees &#8220;on the other end&#8221;, the logical entity that talks to the card using the iso7816 and the CWA 14980 protocols. </p>
<p>Hence, it&#8217;s the combination of reader+computer, since the reader implements the lower layers of the iso7816 stack (physical layer and link layer [T=0, T=1...] ) and the computer implements the upper layers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alvaro</title>
		<link>http://www.limited-entropy.com/dnie-device-auth/comment-page-1#comment-12580</link>
		<dc:creator>Alvaro</dc:creator>
		<pubDate>Tue, 02 Mar 2010 09:47:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.limited-entropy.com/?p=556#comment-12580</guid>
		<description>So, if I understood it right: the IFD has his own public key?

And, another doubt: the IFD is the computer trying to access the card, or is it the reader device?</description>
		<content:encoded><![CDATA[<p>So, if I understood it right: the IFD has his own public key?</p>
<p>And, another doubt: the IFD is the computer trying to access the card, or is it the reader device?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
