Yubico Forum

...visit our web-store at store.yubico.com
It is currently Tue Jan 30, 2018 6:25 pm

All times are UTC + 1 hour




Post new topic Reply to topic  [ 3 posts ] 
Author Message
PostPosted: Sat Nov 09, 2013 10:55 am 
Offline

Joined: Sat Nov 09, 2013 9:49 am
Posts: 2
Hi

I'm trying to simulate my own NFC Forum Type 4 tag on a Yubikey Neo.

I played a bit with the personalization tool to set a dedicated NDEF URL - at some point the Mifare zone ended up being reset (keys A/B set to FF...FF), then with a Java Card applet using the javacardx.external.Memory standard interface to validate that I can write something into the Mifare zone.

There is apparently an NDEF Tag application already present, however it doesn't answer as expected (on all interfaces, in Mifare classic or Mifare DESfire configurations using the Windows 8 tool seen at some other place on this forum)

Code:
nba@kostal:/tmp$ scriptor
No reader given: using Yubico 00 00
Using T=1 protocol
Reading commands from STDIN
00a4040007d276000085010100
> 00 a4 04 00 07 d2 76 00 00 85 01 01 00
< 90 00 : Normal processing.
00a4000c02e103
> 00 a4 00 0c 02 e1 03
< 90 00 : Normal processing.
00b000000f
> 00 b0 00 00 0f
< 00 0F 20 00 7F 00 7F 04 06 E1 04 00 7F 00 00 90
00 : Normal processing.
00a4000c02e104
> 00 a4 00 0c 02 e1 04
< 90 00 : Normal processing.
00b0000002
> 00 b0 00 00 02
< 69 83 : Command not allowed. Authentication method blocked.


Now on to the questions :

- Can I fix this ?

- Can I disable the d276000085010100 application and code my own ? (preferred, as I would like mine to avoid answering on the contact interface)

Thanks for your help ;)


Last edited by nbasim on Tue Nov 12, 2013 3:10 pm, edited 1 time in total.

Top
 Profile  
Reply with quote  

Share On:

Share on Facebook FacebookShare on Twitter TwitterShare on Tumblr TumblrShare on Google+ Google+

PostPosted: Tue Nov 12, 2013 12:17 pm 
Offline
Site Admin
Site Admin

Joined: Wed May 28, 2008 7:04 pm
Posts: 263
Location: Yubico base camp in Sweden - Now in Palo Alto
The NDEF type 4 tags are handled through APDUs on the ISO14443-4 layer and in order to support these, we've added an NDEF applet with AID D2760000850101. The operation is described in the NFC forum document "Type 4 Tag Operation Specification", which can be downloaded at their website.

This applet can be removed or replaced with your own applet of choice of you want. Just be aware that you cannot restore our NDEF applet, thereby losing the possibility to get NDEFs with embedded OTPs.

The current NEO does not feature Mifare DesFire support, but you can use Mifare Classic if you want. Then, in order to not confuse your reader (unless you have full control of that), you probably need to change the ATQA and SAK responses to let the host believe you have an ISO14443-3 only tag. Then, you can use the Mifare Classic ISO14443-3 NDEF tag type 2, if that is what you want.

Do you have a Windows 8 phone ? That one gets a bit confused by the "hybrid" Mifare Classic emulation. If you send the following APDU to the NEO, it will change the SAK and ATQA responses to please the W8 phone - 80e2800007df3504a5034420

Please let me know if this answered your questions in a satisfactory way.

Best regards,

JakobE
Hardware- and firmware guy @ Yubico


Top
 Profile  
Reply with quote  
PostPosted: Tue Nov 12, 2013 3:09 pm 
Offline

Joined: Sat Nov 09, 2013 9:49 am
Posts: 2
Hi

Thanks for the detailed answer

I just realized that I didn't delete the correct AID when trying to delete it, so it's fixed.


Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 3 posts ] 

All times are UTC + 1 hour


Who is online

Users browsing this forum: No registered users and 10 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group