On Wed, Mar 13, 2013 at 2:15 PM, Luã de Souza <[email protected]> wrote:
> Hello,
>
> I'm developing a NFC application with for now is only using the card's UID,
> but in the future will use PIN authentication for payments.
>
> As I'm choosing with chip my cards will use, I was pretty sure about the
> classic 1k, which appears to solve all my needs. As I was doing some
> research, I saw that the ultralight chip is at least 2 times cheaper than
> the classic 1k. There's a real downside for me if I choose the ultralight
> card?

Standard ultralight cards do not have any sort of
password/authentication and they have a 7 byte UID, they are always
free to read/update. There is another model of the Ultralight card
called "Ultralight C" which have a more modern authentication system
similar to the Desfire card. And recently NXP introduced the newer
Ultralight EV1 card that have a password system with limited attempts.
Ultralight cards are usually made of paper instead of plastic so they
are used for discardable tickets.

Standard old mifare cards have a 4 byte UID (newer mifare cards have 7
byte UID) and the A and B keys to protect the data reading/updating.
Mifare cards are made of plastic and are thicker than Ultralight
cards.

> I know that the classic 1k has "native" cryptographic security (although
> it's been hacked), but since I don't need too much space in the chip, I
> don't know any other advantage.

You should no rely in the mifare keys, you need to protect the data
inside the card with other methods like data signing/ciphering with
the help of an irreversible global counter (which is supported by the
mifare).

> Someone who had experience with this kind of project can give me some
> advice?

I hope my answers help you, if not, feel free to contact me in portuguese =)

> Thank you.

Best wishes,
Bruno

> --
> Luã J. de Souza
> http://www.lsouza.pro.br
> Analista Desenvolvedor Web e Programador de Interfaces
> +55 21 81072993
>
> _______________________________________________
> Muscle mailing list
> [email protected]
> http://lists.musclecard.com/mailman/listinfo/muscle_lists.musclecard.com
>

_______________________________________________
Muscle mailing list
[email protected]
http://lists.musclecard.com/mailman/listinfo/muscle_lists.musclecard.com

Reply via email to