<?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: Open Source Identity Management: eID Cards&#8217; Spec Finally disclosed!</title>
	<atom:link href="http://robertogaloppini.net/2008/05/16/open-source-identity-management-eid-cards-spec-finally-disclosed/feed/" rel="self" type="application/rss+xml" />
	<link>http://robertogaloppini.net/2008/05/16/open-source-identity-management-eid-cards-spec-finally-disclosed/</link>
	<description>“equally critical of proprietary and open source myths, advocating software choice beyond marketing and romanticism”</description>
	<pubDate>Fri, 12 Mar 2010 16:24:38 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Roberto Galoppini</title>
		<link>http://robertogaloppini.net/2008/05/16/open-source-identity-management-eid-cards-spec-finally-disclosed/comment-page-1/#comment-662118</link>
		<dc:creator>Roberto Galoppini</dc:creator>
		<pubDate>Tue, 01 Dec 2009 11:45:05 +0000</pubDate>
		<guid isPermaLink="false">http://robertogaloppini.net/2008/05/16/open-source-identity-management-eid-cards-spec-finally-disclosed/#comment-662118</guid>
		<description>I don't know an "out-of-the-box" open source replacement for that, sorry.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know an &#8220;out-of-the-box&#8221; open source replacement for that, sorry.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Saurabh</title>
		<link>http://robertogaloppini.net/2008/05/16/open-source-identity-management-eid-cards-spec-finally-disclosed/comment-page-1/#comment-662102</link>
		<dc:creator>Saurabh</dc:creator>
		<pubDate>Mon, 30 Nov 2009 12:43:44 +0000</pubDate>
		<guid isPermaLink="false">http://robertogaloppini.net/2008/05/16/open-source-identity-management-eid-cards-spec-finally-disclosed/#comment-662102</guid>
		<description>Hi Roberto, 

We are trying to Replace MS Identity Lifecycle Management for an Organization of 8000 employees, is there any solution you suggest ?</description>
		<content:encoded><![CDATA[<p>Hi Roberto, </p>
<p>We are trying to Replace MS Identity Lifecycle Management for an Organization of 8000 employees, is there any solution you suggest ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roberto Resoli</title>
		<link>http://robertogaloppini.net/2008/05/16/open-source-identity-management-eid-cards-spec-finally-disclosed/comment-page-1/#comment-410763</link>
		<dc:creator>Roberto Resoli</dc:creator>
		<pubDate>Tue, 27 May 2008 15:00:08 +0000</pubDate>
		<guid isPermaLink="false">http://robertogaloppini.net/2008/05/16/open-source-identity-management-eid-cards-spec-finally-disclosed/#comment-410763</guid>
		<description>The CIE filesystem is a great new for everybody, like me and Bud, interested in open source as a way to lower the barrier between citizens and eGovernment. It seems that  a lot of already done work is being unlocked (Bud, Emanuele, who else? :-) ). 
CNS and CIE are indeed different beasts, but they MUST[1] be interoperable. 
The main difference, apart form external appearance, is that CIE does not have a Digital Signature service on board, even if the last rules (November 2007, the same that stated the filesystem disclosure) 
specifically indicate this possibity.

CNS is not the best practice around, from the Open Source point of view. 
It is currently not possible to support it, because some operations (Digital Signature in particular) are protected using  symmetric cryptography 
("Secure Messaging") whose secret keys are embedded in the card, and then in the opaque, proprietary software that deals with it.

The need of protection (but not its implementation) is mandated by an EU regulation about Electronic Signature[2], which sets the level of security (CWA 14169 -&gt; Common Criteria, EAL4+) for "Secure Signature
Creation Devices" (SSCD). Technically, a "Trusted Path" and "Trusted Channel" must be estabilished between SSCD and SCA (Signature Creation Application).
The actual running  implementation is such that CNS cards coming from different manufacturer (and even different batches of cards from the same manufacturer!) are not interoperable (even if all the specifications
involved are the same, the secret key is not!).

The corrently under study European Citizen Card proposes a different approach; in related technical (CWA 14890, chapter 8) a protocol involving asymmetric cryptography is outlined, in which the key for Secure Messaging is generated on the fly, more or less in an SSL/TLS fashion. 
May be this could be the next step on the way of a really open and interoperable eID infrastructure.

If someone wants to go deep in the subject, i prepared a package[3] collecting several of the regulations quoted here, along with a presentation I made for the last Italian Free Software Conference.

[1] &lt;a href="http://www.cnipa.gov.it/site/it-IT/Attivit%C3%A0/Certificatori_accreditati/Carta_Nazionale_dei_Servizi/" title="CNS - CNIPA" rel="nofollow"&gt;CNS on CNIPA web site&lt;/a&gt; (in italian).

"La completa corrispondenza informatica tra CNS e CIE assicurerà 
l’interoperabilità tra le due carte e la continuità di servizi 
all’utente che passi della Carta Nazionale dei Servizi 
alla Carta d’Identità Elettronica"

that is:

"The complete informatic match between CNS and CIE will assure
interoperability between the two cards and continuity of service
to the user moving from CNS to CIE."

[2]"COMMISSION DECISION of 14 July 2003
on the publication of reference numbers of generally recognised standards for electronic signature
products in accordance with Directive 1999/93/EC of the European Parliament and of the Council" 

&lt;a href="http://www.interlex.it/testi/pdf/dec030714.pdf" title="Commission Decision" rel="nofollow"&gt;PDF on Interlex web site&lt;/a&gt; (in English) 

[3] &lt;a href="http://www.confsl.org/images/files/workshops/workshop_sc-egov-floss.zip" title="SmartCards, eGov, Free Sw" rel="nofollow"&gt;zipped package&lt;/a&gt; from the "SmartCards, eGovernment and Free Software" workshop on the &lt;a href="http://www.confsl.org" rel="nofollow"&gt;ConfSL08 website&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>The CIE filesystem is a great new for everybody, like me and Bud, interested in open source as a way to lower the barrier between citizens and eGovernment. It seems that  a lot of already done work is being unlocked (Bud, Emanuele, who else? <img src='http://robertogaloppini.net/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> ).<br />
CNS and CIE are indeed different beasts, but they MUST[1] be interoperable.<br />
The main difference, apart form external appearance, is that CIE does not have a Digital Signature service on board, even if the last rules (November 2007, the same that stated the filesystem disclosure)<br />
specifically indicate this possibity.</p>
<p>CNS is not the best practice around, from the Open Source point of view.<br />
It is currently not possible to support it, because some operations (Digital Signature in particular) are protected using  symmetric cryptography<br />
(&#8221;Secure Messaging&#8221;) whose secret keys are embedded in the card, and then in the opaque, proprietary software that deals with it.</p>
<p>The need of protection (but not its implementation) is mandated by an EU regulation about Electronic Signature[2], which sets the level of security (CWA 14169 -&gt; Common Criteria, EAL4+) for &#8220;Secure Signature<br />
Creation Devices&#8221; (SSCD). Technically, a &#8220;Trusted Path&#8221; and &#8220;Trusted Channel&#8221; must be estabilished between SSCD and SCA (Signature Creation Application).<br />
The actual running  implementation is such that CNS cards coming from different manufacturer (and even different batches of cards from the same manufacturer!) are not interoperable (even if all the specifications<br />
involved are the same, the secret key is not!).</p>
<p>The corrently under study European Citizen Card proposes a different approach; in related technical (CWA 14890, chapter <img src='http://robertogaloppini.net/wp-includes/images/smilies/icon_cool.gif' alt='8)' class='wp-smiley' /> a protocol involving asymmetric cryptography is outlined, in which the key for Secure Messaging is generated on the fly, more or less in an SSL/TLS fashion.<br />
May be this could be the next step on the way of a really open and interoperable eID infrastructure.</p>
<p>If someone wants to go deep in the subject, i prepared a package[3] collecting several of the regulations quoted here, along with a presentation I made for the last Italian Free Software Conference.</p>
<p>[1] <a href="http://www.cnipa.gov.it/site/it-IT/Attivit%C3%A0/Certificatori_accreditati/Carta_Nazionale_dei_Servizi/" title="CNS - CNIPA" rel="nofollow">CNS on CNIPA web site</a> (in italian).</p>
<p>&#8220;La completa corrispondenza informatica tra CNS e CIE assicurerà<br />
l’interoperabilità tra le due carte e la continuità di servizi<br />
all’utente che passi della Carta Nazionale dei Servizi<br />
alla Carta d’Identità Elettronica&#8221;</p>
<p>that is:</p>
<p>&#8220;The complete informatic match between CNS and CIE will assure<br />
interoperability between the two cards and continuity of service<br />
to the user moving from CNS to CIE.&#8221;</p>
<p>[2]&#8220;COMMISSION DECISION of 14 July 2003<br />
on the publication of reference numbers of generally recognised standards for electronic signature<br />
products in accordance with Directive 1999/93/EC of the European Parliament and of the Council&#8221; </p>
<p><a href="http://www.interlex.it/testi/pdf/dec030714.pdf" title="Commission Decision" rel="nofollow">PDF on Interlex web site</a> (in English) </p>
<p>[3] <a href="http://www.confsl.org/images/files/workshops/workshop_sc-egov-floss.zip" title="SmartCards, eGov, Free Sw" rel="nofollow">zipped package</a> from the &#8220;SmartCards, eGovernment and Free Software&#8221; workshop on the <a href="http://www.confsl.org" rel="nofollow">ConfSL08 website</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bud P. Bruegger</title>
		<link>http://robertogaloppini.net/2008/05/16/open-source-identity-management-eid-cards-spec-finally-disclosed/comment-page-1/#comment-410593</link>
		<dc:creator>Bud P. Bruegger</dc:creator>
		<pubDate>Tue, 27 May 2008 10:24:22 +0000</pubDate>
		<guid isPermaLink="false">http://robertogaloppini.net/2008/05/16/open-source-identity-management-eid-cards-spec-finally-disclosed/#comment-410593</guid>
		<description>About two years ago, I wrote OpenSC support for CIE and had also submitted it to the Ministry in order for them  to publish it on their open source repository (I had an NDA, never received the spec, and it was never published).  Haven't had time to port it to the latest version and for legal reasons, couldn't publish it (and the same for my python library to access CIE, pyCIE), but Roberto Resoli (Comune di Trento) has started to work with my old code.  But let's just work together to create a single PKCS#11 for CIE and CNS (the current CIE ARE different from CNS in some respect..).  Some people officially involved with CNS are also interested in this work.  Let's join and produce a single well-tested solution.

-b</description>
		<content:encoded><![CDATA[<p>About two years ago, I wrote OpenSC support for CIE and had also submitted it to the Ministry in order for them  to publish it on their open source repository (I had an NDA, never received the spec, and it was never published).  Haven&#8217;t had time to port it to the latest version and for legal reasons, couldn&#8217;t publish it (and the same for my python library to access CIE, pyCIE), but Roberto Resoli (Comune di Trento) has started to work with my old code.  But let&#8217;s just work together to create a single PKCS#11 for CIE and CNS (the current CIE ARE different from CNS in some respect..).  Some people officially involved with CNS are also interested in this work.  Let&#8217;s join and produce a single well-tested solution.</p>
<p>-b</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emanuele Pucciarelli</title>
		<link>http://robertogaloppini.net/2008/05/16/open-source-identity-management-eid-cards-spec-finally-disclosed/comment-page-1/#comment-410439</link>
		<dc:creator>Emanuele Pucciarelli</dc:creator>
		<pubDate>Tue, 27 May 2008 07:47:40 +0000</pubDate>
		<guid isPermaLink="false">http://robertogaloppini.net/2008/05/16/open-source-identity-management-eid-cards-spec-finally-disclosed/#comment-410439</guid>
		<description>I hadn't read your take before doing this, but it turns out to be correct. There is a &lt;a href="https://www.opensc-project.org/opensc/ticket/177" rel="nofollow"&gt;patch&lt;/a&gt; adding support for CNS/CIE, and I hope it gets into trunk soon, so that the next release of OpenSC features support as well.</description>
		<content:encoded><![CDATA[<p>I hadn&#8217;t read your take before doing this, but it turns out to be correct. There is a <a href="https://www.opensc-project.org/opensc/ticket/177" rel="nofollow">patch</a> adding support for CNS/CIE, and I hope it gets into trunk soon, so that the next release of OpenSC features support as well.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
