<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
	<title type="html"><![CDATA[libnfc developers community — A dynamic NFC tag does it exist?]]></title>
	<link rel="self" href="http://www.libnfc.org/community/feed/atom/topic/651/" />
	<updated>2012-04-29T21:35:24Z</updated>
	<generator>PunBB</generator>
	<id>http://www.libnfc.org/community/topic/651/a-dynamic-nfc-tag-does-it-exist/</id>
		<entry>
			<title type="html"><![CDATA[Re: A dynamic NFC tag does it exist?]]></title>
			<link rel="alternate" href="http://www.libnfc.org/community/post/3221/#p3221" />
			<content type="html"><![CDATA[<div class="quotebox"><cite>yobibe wrote:</cite><blockquote><p>I didn&#039;t say it wasn&#039;t possible for you to emulate a tag4, I said you&#039;ve also to think also on how to send data to the smart tag.<br />One way can be to &quot;write&quot; some content into the NDEF file (see NDEF update in the tag4 spec) and &quot;read&quot; back that same NDEF file.<br />Up to the Java applet to interpret those APDUs to interface with your challenge/response protocol.</p><p>Now about implementing SNEP on a Javacard...<br />SNEP works on top of LLCP while Javacard communication is APDU-based, I don&#039;t know LLCP enough but I think it&#039;s quite incompatible.</p><p>So first option is still your best bet.</p></blockquote></div><p>Sheat, I forgot Javacard were based on APDU!</p><p>NDEF was a way to work while following the NFC Forum specs. But, in fact, it seems to be far more complicated that using the old way: a good old APDU with arguments.</p><p>That is: sending an specially forged APDU that means: take this argument as a challenge and prepare an answer with the response about which I&#039;ll ask for in a few milliseconds.<br />Ok, that&#039;s proprietary but no more that something that could modify a NDEF.</p><p>What do you think?</p><p>db</p><p><em>Edit: APDU as the only communication mode was true for earlier and actual classic edition of Javacard. That&#039;s not true anymore for Javacard Connected Edition that appeared with Javacard 3.0. The connected Edition which is more like J2ME (the Java version for mobile equipment) can talk HTTP and&nbsp; HTTPS and, therefore, TCP/IP.<br />There could be something to dig in there. <br />Problem 1: there seems there&#039;s no commercial product compliant with JC3 CEdition at this time.<br />Problem 2: according to the stack figured in the specs, ISO/IEC 14443 is used only with APDU.</em></p>]]></content>
			<author>
				<name><![CDATA[Gaduc]]></name>
				<uri>http://www.libnfc.org/community/user/3062/</uri>
			</author>
			<updated>2012-04-29T21:35:24Z</updated>
			<id>http://www.libnfc.org/community/post/3221/#p3221</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: A dynamic NFC tag does it exist?]]></title>
			<link rel="alternate" href="http://www.libnfc.org/community/post/3220/#p3220" />
			<content type="html"><![CDATA[<p>I didn&#039;t say it wasn&#039;t possible for you to emulate a tag4, I said you&#039;ve also to think also on how to send data to the smart tag.<br />One way can be to &quot;write&quot; some content into the NDEF file (see NDEF update in the tag4 spec) and &quot;read&quot; back that same NDEF file.<br />Up to the Java applet to interpret those APDUs to interface with your challenge/response protocol.</p><p>Now about implementing SNEP on a Javacard...<br />SNEP works on top of LLCP while Javacard communication is APDU-based, I don&#039;t know LLCP enough but I think it&#039;s quite incompatible.</p><p>So first option is still your best bet.</p>]]></content>
			<author>
				<name><![CDATA[yobibe]]></name>
				<uri>http://www.libnfc.org/community/user/812/</uri>
			</author>
			<updated>2012-04-29T19:07:42Z</updated>
			<id>http://www.libnfc.org/community/post/3220/#p3220</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: A dynamic NFC tag does it exist?]]></title>
			<link rel="alternate" href="http://www.libnfc.org/community/post/3218/#p3218" />
			<content type="html"><![CDATA[<div class="quotebox"><cite>yobibe wrote:</cite><blockquote><p>If you look for a product the only thing I can think of is to take a Javacard and write your own applet to emulate a Tag4.<br />But reading a NFC tag does not send much info *to* the tag so I don&#039;t know how you will send your challenge to the tag while respecting the standard procedure to read a Tag4. Writing a NDEF then reading it back?</p><p>Phil</p></blockquote></div><p>Maybe the trick is there: writing a Java applet (*) for a Javacard not to emulate a type 4 tag (**) but to talk SNEP.</p><p>But do you think it&#039;s possible for a smart card (that is to say for something that is remote powered and not self powered) to become a peer? Don&#039;t you thing that&#039;s something in the lower layers (ISO 14443-1/2/3) that could forbid such a card to establish a P2P dialog?<br />The Felica which nephets talked about is self-powered (by the Arduino for example).</p><p>Regards,</p><p>db</p><p>(*) Starting from the MUSCLE applet maybe.</p><p>(**) Because, as you said it, it&#039;s not possible for a tag, following the specification, to know that the initiator sent something to it as well as the initiator is not expected to send something during this kind of dialog.</p>]]></content>
			<author>
				<name><![CDATA[Gaduc]]></name>
				<uri>http://www.libnfc.org/community/user/3062/</uri>
			</author>
			<updated>2012-04-29T09:52:48Z</updated>
			<id>http://www.libnfc.org/community/post/3218/#p3218</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: A dynamic NFC tag does it exist?]]></title>
			<link rel="alternate" href="http://www.libnfc.org/community/post/3209/#p3209" />
			<content type="html"><![CDATA[<p>If you look for a product the only thing I can think of is to take a Javacard and write your own applet to emulate a Tag4.<br />But reading a NFC tag does not send much info *to* the tag so I don&#039;t know how you will send your challenge to the tag while respecting the standard procedure to read a Tag4. Writing a NDEF then reading it back?</p><p>Phil</p>]]></content>
			<author>
				<name><![CDATA[yobibe]]></name>
				<uri>http://www.libnfc.org/community/user/812/</uri>
			</author>
			<updated>2012-04-27T08:01:55Z</updated>
			<id>http://www.libnfc.org/community/post/3209/#p3209</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: A dynamic NFC tag does it exist?]]></title>
			<link rel="alternate" href="http://www.libnfc.org/community/post/3207/#p3207" />
			<content type="html"><![CDATA[<div class="quotebox"><cite>nephets wrote:</cite><blockquote><p>Have a look at <a href="http://blog.felicalauncher.com/en/?cat=6,">http://blog.felicalauncher.com/en/?cat=6,</a> I think that&#039;s what you&#039;re looking for.</p></blockquote></div><p>Yes, thx to point this ou.<br />But, despite the fact that this tag is well documented and publicly available it&#039;s not very autonomous as well as not very wearable: I doubt that anybody would want to use it daily with an Arduino in the pocket.t<br />The idea is there but with the CPU inside the chip not outside!<br />I&#039;m looking for a product not for something experimental.</p><p>Thx again!<br />db</p>]]></content>
			<author>
				<name><![CDATA[Gaduc]]></name>
				<uri>http://www.libnfc.org/community/user/3062/</uri>
			</author>
			<updated>2012-04-27T03:59:24Z</updated>
			<id>http://www.libnfc.org/community/post/3207/#p3207</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: A dynamic NFC tag does it exist?]]></title>
			<link rel="alternate" href="http://www.libnfc.org/community/post/3202/#p3202" />
			<content type="html"><![CDATA[<p>Have a look at <a href="http://blog.felicalauncher.com/en/?cat=6,">http://blog.felicalauncher.com/en/?cat=6,</a> I think that&#039;s what you&#039;re looking for.</p>]]></content>
			<author>
				<name><![CDATA[nephets]]></name>
				<uri>http://www.libnfc.org/community/user/89/</uri>
			</author>
			<updated>2012-04-26T15:41:03Z</updated>
			<id>http://www.libnfc.org/community/post/3202/#p3202</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[A dynamic NFC tag does it exist?]]></title>
			<link rel="alternate" href="http://www.libnfc.org/community/post/3196/#p3196" />
			<content type="html"><![CDATA[<p>I&#039;m looking for a dynamic NFC tag that is able to dynamically change its content or a NFC tag that is able to talk SNEP.<br />Don&#039;t answer &quot;a smartphone&quot;, that&#039;s not my target.<br />My target is to offer a simple way of authentifying someone that doesn&#039;t have a NFC handset (because it&#039;s expensive or because the battery is empty, etc).</p><p>The idea is to use the NDEFormat to exchange data based on a challenge sent by an initiator (the reader that stands in the wall near the door). <br />The tag then computes a NDEF with a specific field (to be defined) whose content is a result of a cryptographic function applied to the challenge (nothing new here: windows, Kerberos, etc have been working this way for a couple of years).</p><p>The reader then reads this NDEF and applies the same cryptographic function to its challenge: if they match the door opens else the door keeps closed.</p><br /><p>db</p>]]></content>
			<author>
				<name><![CDATA[Gaduc]]></name>
				<uri>http://www.libnfc.org/community/user/3062/</uri>
			</author>
			<updated>2012-04-25T08:50:44Z</updated>
			<id>http://www.libnfc.org/community/post/3196/#p3196</id>
		</entry>
</feed>
