How MIFARE Uses Cookies

[TapLinx Support]

Hi Sabalam,

You cannot use the TapLinx SDK to emulate a MIFARE product. If you want to have a MIFARE product on a phone or a gadget, you should think about MIFARE4Mobile:

https://www.mifare4mobile.org/

Kind regards,
The TapLinx Team

---

+ 1  |  - 0

[TapLinx Support]

Hi Denis,

We have examples of preparing a MIFARE card to a NDEF message tag:

MIFARE Classic:
http://www.nxp.com/documents/application_note/AN1304.pdf

MIFARE Ultralight:
http://www.nxp.com/documents/application_note/AN1303.pdf

MIFARE DESFire:
http://www.nxp.com/documents/application_note/AN11004.pdf

Kind regards,
The TapLinx Team

---

+ 1  |  - 0

[TapLinx Support]

Hi Narendc,

The ISO commands are available for compatibility reasons of ISO7816-4. All ISO commands are wrapped to native commands on a DESFire. If you do not need to be compatible to ISO, I recommend to use the native DESFire commands.

The ISO7816-4 allows it to deal with files either with IDs or with DF names. That is the reason for the two types of commands.

Kind regards,
The TapLinx Team

---

+ 0  |  - 0

[TapLinx Support]

Hi Guilherme,

no, I am also waiting for the update.

Sorry,
The TapLinx Team

---

+ 0  |  - 0

[TapLinx Support]

Hello Chaim,

The NTag213 supports password protection and this feature can be used with the TapLinx SDK. The class object for the NTag213 supports all features of the tag.

Please take in mind, that the NTag213 is not a high security product. If you want to have maximum security, I recommend to use the MIFARE DESFire EV1/EV2 with AES128 keys or the MIFARE Plus in Security Level 3.

Kind regards,
The TapLinx Team

---

+ 0  |  - 1

[TapLinx Support]

Hi Narendc,

You have to be careful, if you want to change a DESFire key. Before you can overwrite a key you have to prove, that you are allowed to do that—even if the key was not used before! Before you can change a key, you have to authenticate to key number with the old key value. Please have a look to this example:

https://www.mifare.net/support/forum/topic/cannot-create-desfire-ev1-aplication-with-aes-key/

Kind regards,
The TapLinx Team

---

+ 0  |  - 0

[TapLinx Support]

Hi Lagur,

Please take in mind, the MIFARE DESFire EV1 or EV2 are security products. For me it seems that the “16 bytes app key” is an AES128 key, used for protection or encryption of the data. You have two options to deal with the DESFire:

1. You use the TapLinx SDK for Android. The SDK is free and allows it to communicate with the DESFire.


2. You implement your software on a PC or a microcontroller with a “third party NFC reader”. Here you have to send the ISO or native commands to the DESFire directly. If you want to use native commands, you need to sign a NDA. Please contact us via taplinx@nxp.com for the NDA request.

Kind regards,
The TapLinx Team

---

+ 0  |  - 0

[TapLinx Support]

Hi Anuj,

Your request is very interesting and I had a conversation with the development team about it. To use the MIFARE SAM as hardware key store might also make sense in mobile environments (from my point of view). But several obstacles lay in the way to a solution for this approach. Let me pick up two of them:

1. You need an interface for the SAM. Most mobile devices does not provide an extra SIM card slot and even if so, the Google API does not provide a standard API for using such slot. Therefore it will never be integrated into TapLinx.


2. You can connect the SAM via USB or Bluetooth reader to your Android device. In this case you have to use the API of the USB or Bluetooth manufacturer. But you can only integrate the SAM into the TapLinx API, if it is possible to get access to the raw APDU stream in TapLinx. You need this for instance for an authentication to the card which is managed via SAM. But this is not possible as the development team assured me.

So, the bad news are: we have no solution for you. The only way for instance is to implement the card data stream via class android.nfc.tech.NfcA and use the method byte[] transceive(byte[] data) for sending and receiving APDU commands to the stream of the card on the one hand and with a separate APDU channel to the SAM on the other hand.

Regards,
The TapLinx Team

---

+ 0  |  - 0

[TapLinx Support]

Hi Jesús,

The development team will release a new version in the next week (CW45). This will be version 1.1.

Regards,
The TapLinx Team

---

+ 0  |  - 0

[TapLinx Support]

Hi,

The ISO14443 specification allows to handle more than one card in the field. This is not possible from the Android implementation of NFC interface. So, TapLinx does not support more than one card at the same time connected to the phone.

Regards,
The TapLinx Team

---

+ 0  |  - 0

[TapLinx Support]

Hi DevPatel,

You have to set the interface of the RC663 into SAM mode in the HostControlRegister (0x01) with value 0x28.

Regards,
The TapLinx Team

---

+ 0  |  - 0

[TapLinx Support]

Hi Anuj,

That is correct, SAM AV2 will never return key values. TapLinx does not support SAM directly, because there is no standardized interface for a SIM card slot in Android API. You can use the SAM with an external ready via USB or Bluetooth, but this requires the driver API of the vendor.

The SAM allow it to use it in “X mode” or “Non X mode”. In X mode the control of the card is done by SAM, in non X mode it is handed over. This is the mode you have to use. Please have a look to SAM_AuthenticatePICC() (chapter 11.7.1). It is required to have the authentication key in SAM. Please have also a look to the Mutual Authentication procedure. You will never move a key directly in this procedure! You always encrypt a random number and transfer this to the participant and the participant decrypt it and put its own random and encrypt it and transfers it back. If both sides verify its own random value, the authentication is done.

Kind regards,
The TapLinx Team

---

+ 0  |  - 0

[TapLinx Support]

Hi Erwin,

Sorry, the answer is no. TapLinx supports MIFARE, Ntag and ICode products.

Regards,
The TapLinx Team

---

+ 0  |  - 0

[TapLinx Support]

Hi Marko,

The bug will be fixed in the next release. But currently I do not have a schedule for the next release, sorry.

Regards,
The TapLinx Team

---

+ 0  |  - 0

[TapLinx Support]

Hi Baskaran,

If an antenna design works, depends on the whole environment, the case, other noisy components etc. At the end you have to test it in practice.

Regards,
The TapLinx Team

---

+ 0  |  - 0

[Author]

Posts