How MIFARE Uses Cookies

[mifaresdk]

Hi neobagsjol and kamii47,

currently the MIFARE SDK is available only for Android but a release for Windows .NET is being planned. You can use the NXPRdLib for communicating with the “Contactless Reader RD710” also known as Pegoda Reader. The NXPRdLib is written in C but you can used as “unmanaged library” in your Visual Studio project.

These links may useful:

http://www.nxp.com/documents/application_note/AN10993.pdf
http://www.nxp.com/documents/application_note/AN10992.pdf
http://www.nxp.com/documents/application_note/AN10990.pdf

Regards,
The MIFARE Team

---

+ 0  |  - 0

[mifaresdk]

Hello CRaghwani,

the Nexus 5 uses a NFC chip which does not support the MIFARE Classic interface specification. So the Nexus 5 is not able to communicate with the MIFARE Classic card. But for other MIFARE cards there is no such restriction. Using a MIFARE DESFire or NTAG products will work with the Nexus 5.

The MIFARE Team

---

+ 1  |  - 0

[mifaresdk]

Hi Phil,

I don’t know about intentions of NXP to release such software in future.

Regards,
MIFARE Team

---

+ 0  |  - 0

[mifaresdk]

Hi Phil,

you use the MIFARE Classic card to control the usage of printing. Please take in mind that the security of this approach is that the coping of a Classic card is very difficult. The NFC infrastructure on Android is open, so anyone may be able to break our emulation software and copy the software and share the print access to everybody at your school (the security and copy-protections are the key topics here).

You can implement several application counters and read/write sectors on a Classic card to support different purposes (e.g. door access, print access, payment in the canteen etc). I would recommend to use a DESFire card for this multi-purpose needs for security reasons.

Regards,
MIFARE Team

---

+ 0  |  - 0

[mifaresdk]

Hi kerry9842,

as I argue to you on another thread we cannot provide support for the libnfc library.

Please take in mind the MIFARE DESFire card is a security product and the communication between the card and the reader is normally encrypted. This means that every read or write cycle is a sequence of encrypted commands. The first step is to personalize the card from the factory settings to dedicated keys and format sectors on the card with use this keys. You need a cypher component on the library which do the encrypting of the sequence byte streams.

Best regards,
MIFARE Team

---

+ 0  |  - 0

[mifaresdk]

Hi kerry9842,

the libnfc is an Open Source library for NFC access on Linux systems. We cannot provide support for the libnfc library on this site. But you will find discussion threads in the net about using the libnfc and about issues of the libnfc.

Best regards,
MIFARE Team

---

+ 0  |  - 0

[mifaresdk]

Hi Phil,

I do not know about such app. This is a question what do you want to do. To emulate a DESFire card for what purpose? I do not see any reason why someone will provide a universal usable HCE implementation. All booking and payment systems use secure chips on the device which makes it very difficult to copy or emulate this at all in software.

Best regards,
MIFARE-Team

---

+ 0  |  - 0

[mifaresdk]

Dear Darkknight512,

usually for Arduino shields you get all necessary library software you need to program the shield.

If you want to communicate with MIFARE Classic cards you need a NFC reader which fulfill specifications for this card. Not all manufacturers fulfill the specs, e.g. the reader chip in the Nexus 4 doesn’t. To be always on the right side prefer readers with NXP chip sets.

Regards,
MIFARE-Team

---

+ 0  |  - 0

[mifaresdk]

Hi Samuel,

The MIFARE SDK helps you to communicate with MIFARE products on mobile devices (Android and Windows). The SDK does not emulate any MIFARE product!

Best regards,
The MIFARE SDK Team

---

+ 0  |  - 0

[mifaresdk]

Hi mostafahk,

Please consider the security aspects of your idea. To have a SAM AV2 on a server means you need a secure channel from the customer to your server. Generally the SAM AV2 should be as close as possible to the customers NFC input station – usually direct at the reader.

The MIFARE Team

---

+ 0  |  - 0

[mifaresdk]

Hi dizgah,

in generally NFC phones can share NDEF messages via the build-in-chip. There are a lot of applications for send and receive this kind of messages. But you ask for an emulation of an entire card which is emulated in the phone. This is called Host Card Emulation (HCE). Unfortunately the MIFARE SDK does not support HCE.

Best regards,
The MIFARE SDK Team

---

+ 0  |  - 0

[mifaresdk]

Dear mack23,

The Nexus 4 and 7 devices uses a Broadcom NFC reader which is not full certified for using MIFARE DESFire products (for Android devices with NXP NFC readers this problem should not occur). With updates this problem should be fixed:

Nexus 7 Android Version 4.4.4
Nexus 5 Android Version 5.0
Nexus 4 Android Version 5.0

We suggest you to update your Android device.

Regards,
The MIFARE SDK Team

---

+ 0  |  - 0

[mifaresdk]

Hi rock82egy,
this is the support forum for MIFARE SDK users. When you use a MIFARE Plus product, you will found the method com.nxp.nfclib.plus.Plus.authenticateSL3() which performs an authenticate into secure level 3 (you cannot work only in secure level 1 if you work with the SDK).

The anti-collision is part of the reader infrastructure and handled out of the view of you programming model. When the card is properly detected you have access and start the authenticate and if was successful the read/write access to the card.

The MIFARE SDK Team

---

+ 0  |  - 0

[mifaresdk]

Hi mikeactatek,

I verify your question. The output of Plus.getTagName() (package com.nxp.nfclib.plus.Plus) is in my case "MIFare PLUS SL0" when I use a MIFARE Plus S card.

The MIFARE SDK Team

---

+ 0  |  - 0

[mifaresdk]

MIFARE Plus is available in two versions: MIFARE Plus S and MIFARE Plus X.
The MIFARE Plus S (MF1SPLUSx0y1, described in this data sheet) is the standard
version for straight forward migration of MIFARE Classic systems. It is configured to
offer high data integrity.
The MIFARE Plus X (MF1PLUSx0y1) offers more flexibility to optimize the command
flow for speed and confidentiality. It offers a rich feature set including proximity checks
against relay attacks.
Both products comes with 2 kB or 4 kB EEPROM.

The MIFARE SDK Team

---

+ 0  |  - 0

[Autor]

Artigos