I can confirm the ATR's as Michael pointed and add an interesting
follow on. When I do scardconnect and then scardsttus to get uid I get
the 5 byte (4 byte dynamic first by 08 static e.g. 080A97A6) from the
phone whenever the NFC service is running. if I leave the connection
open and run multiple commands the uid stays the same but if i
disconnect and reconnect the uid dynamically changes. Is there a way
to capture this uid as it is being created/sent from the phone? Is
this uid generated by the secure element?
On Jun 2, 11:21 am, Alberto González doctorg...@gmail.com wrote:
Have anyone read this?
2.3.4. adds hidden classes for secure element and
related:http://gibraltarsf.com/blog/?p=247
On Jun 2, 2:55 pm, Jorn Cruijsen jorncruij...@gmail.com wrote:
Hey Michael,
Oh, it seems I failed terribly.. That's the value I thought to receive when
the device is in peer-to-peer mode. I confused the two.
Thanks for the clarification.
--
Met vriendelijke groet, | Best regards,
Jorn Cruijsen
jorncruij...@gmail.com
(+31) (0)6 272 492 91
On Thu, Jun 2, 2011 at 1:15 PM, Michael Roland mi.rol...@gmail.com wrote:
Hallo JMC,
Are you guys sure it's a MIFARE 4k card it's emulating?
Yes, I'm very sure it is emulating a MIFARE Classic 4K card and an APDU
based smart card (depending on the protocol activation level).
When I put the device in emulation mode and read its ATR, I'm getting:
3B 8F 80 01 80 4F 0C A0 00 00 03 06 03 00 00 00 00 00 00 6B
Decoding this PC/SC ATR gives this:
3B ... Contactless card
8F ... Number of historical bytes: 0xF (15)
80
01
80 ... Category indicator: A status indicator may be present
in an optional COMPACT-TLV data object.
4F ... Application identifier Presence indicator
0C ... Length of application identifier: 0x0C (12)
Application identifier:
A0 00 00 03 06 ... RID: PC/SC Working Group
03 ... Byte for Standard: ISO 14443 A, part 3
00 00 ... Bytes for Card Name: not in standard
00 00 00 00 ... RFU (Shall be set to zero)
6B ... Checksum
This is a typical ATR if the card emulation mode is not activated. I
receive that ATR if I put the phone in peer-to-peer communication mode
(which is the default if card emulation is disabled).
While I'm actually expecting:
3B 8F 80 01 80 4F 0C A0 00 00 03 06 03 00 02 00 00 00 00 69
With the phone you would not normally receive such an ATR for the card
emulation mode either. Usually a contactless smart card reader (like the
Omnikey 5321) activates the contactless smart card up to its highest
supported protocol layer. For the SmartMX, this means that ISO 14443-4
protocol layer is activated for APDU based communication with the
JavaCard. Thus, the ATR generated by the smart card reader would reflect
the properties of the APDU-based JavaCard and not those of the MIFARE 4K
area. This is the value I recieve when card emulation is on:
3B 8A 80 01 00 31 C1 73 C8 40 00 00 90 00 90
Best regards,
Michael
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
