Support DESFire EV1

[GoogleCodeExporter]

libfreefare does support MIFARE DESFire but not EV1 features, mainly AES 
encryption.

Original issue reported on code.google.com by romu...@libnfc.org on 18 Aug 2010 at 2:19

• Blocked on: #57

[GoogleCodeExporter]

Reviewing Issue 17, I remember that EV1 can also be configured to have a random 
UID.

Original comment by romu...@libnfc.org on 18 Aug 2010 at 3:35

[GoogleCodeExporter]

Original comment by romu...@libnfc.org on 25 Oct 2010 at 8:27

• Changed state: Started

[GoogleCodeExporter]

API improvement suggestion probably related to this:
The mifare_desfire_create_application function does not allow to specify the 
crypto method atm (which is new to EV1 if i'm correct). It is possible to code 
this in the key_no byte but the API does not make this clear.

One possibility is to rename key_no to settings2 or if separate key_no 
parameter is wanted maybe another parameter for the crypto method could be 
added? Either way improves the API i think. What is your opinion on this?

Original comment by glenn.er...@gmail.com on 22 Feb 2011 at 8:00

[GoogleCodeExporter]

I quite agree.  There are still a few glitches to fix before rolling a new 
release.

Original comment by romain.t...@gmail.com on 22 Feb 2011 at 8:53

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by romain.t...@gmail.com on 25 Mar 2011 at 12:46

• Changed state: Started

[GoogleCodeExporter]

This issue was updated by revision r769.

Only ISO application creation as requested by Issue 57 is lacking now.

Original comment by rtarti...@il4p.fr on 25 Mar 2011 at 1:00

[GoogleCodeExporter]

GetISOFileIDs() is also missing as of r770

Note for myself: go through the documentation to find-out all missing functions.

Original comment by romain.t...@gmail.com on 25 Mar 2011 at 5:04

• Changed state: Accepted

[GoogleCodeExporter]

This issue was closed by revision r771.

Original comment by rtarti...@il4p.fr on 26 Mar 2011 at 1:22

• Changed state: Fixed