Modifications

Mifare Classic cards typically have a '''4-byte NUID''' that uniquely (within the numeric limits of the value) identifies the card. It's possible to have a 7 byte IDs as well, but the 4 byte models are far more common for Mifare Classic. }}

Mifare Classic cards typically have a '''4-byte NUID''' that uniquely (within the numeric limits of the value) identifies the card. It's possible to have a 7 byte IDs as well, but the 4 byte models are far more common for Mifare Classic. }}

== Memoire EEPROM ==

=== Memoire EEPROM ===

{{bloc-etroit|text=Mifare Classic cards have either 1K or 4K of EEPROM memory. Each memory block can be configured with different access conditions, with two seperate authentication keys present in each block.

{{bloc-etroit|text=Mifare Classic cards have either 1K or 4K of EEPROM memory. Each memory block can be configured with different access conditions, with two seperate authentication keys present in each block.

}}

}}

== Secteurs de 4 blocs ==

=== Secteurs de 4 blocs ===

1K and 4K cards both use 16 sectors of 4 blocks each, with the bottom 1K of memory on the 4K cards being organised identically to the 1K models for compatability reasons. These individual 4 block sectors (containing 64 byts each) have basic security features are can each be configured with seperate read/write access and two different 6-byte authentication keys (the keys can be different for each sector). Due to these security features (which are stored in the last block, called the '''Sector Trailer'''), only the bottom 3 blocks of each sector are actually available for data storage, meaning you have 48 bytes per 64 byte sector available for your own use.

1K and 4K cards both use 16 sectors of 4 blocks each, with the bottom 1K of memory on the 4K cards being organised identically to the 1K models for compatability reasons. These individual 4 block sectors (containing 64 byts each) have basic security features are can each be configured with seperate read/write access and two different 6-byte authentication keys (the keys can be different for each sector). Due to these security features (which are stored in the last block, called the '''Sector Trailer'''), only the bottom 3 blocks of each sector are actually available for data storage, meaning you have 48 bytes per 64 byte sector available for your own use.

               0      [                    Manufacturer Data                    ]  Manufacturer Block</nowiki>

               0      [                    Manufacturer Data                    ]  Manufacturer Block</nowiki>

=== Secteur de fin (3 blocs) ===

==== Secteur de fin (3 blocs) ====

Le secteur de fin s'appelle "sector trailer" en anglais. Ce secteur contient deux clés secrètes Clé A et Clé B (''Key A'' et ''Key B'' en anglais), ainsi que les conditions d'accès pour les 4 blocs.  

Le secteur de fin s'appelle "sector trailer" en anglais. Ce secteur contient deux clés secrètes Clé A et Clé B (''Key A'' et ''Key B'' en anglais), ainsi que les conditions d'accès pour les 4 blocs.  

For more information in using Keys to access the clock contents, see Accessing Data Blocks further below.

For more information in using Keys to access the clock contents, see Accessing Data Blocks further below.

=== Blocs de données (Blocs 0..2) ===

==== Blocs de données (Blocs 0..2) ====

Data blocks are 16 bytes wide and, depending on the permissions set in the access bits, can be read from and written to. You are free to use the 16 data bytes in any way you wish. You can easily store text input, store four 32-bit integer values, a 16 character uri, etc.

Data blocks are 16 bytes wide and, depending on the permissions set in the access bits, can be read from and written to. You are free to use the 16 data bytes in any way you wish. You can easily store text input, store four 32-bit integer values, a 16 character uri, etc.

=== Blocs de données comme "bloc valeurs" ===

==== Blocs de données comme "bloc valeurs" ====

An alternative to storing random data in the 16 byte-wide blocks is to configure them as "bloc valeur" ("''Value Blocks''" en anglais). Value blocks allow performing electronic purse functions (valid commands are: read, write, increment, decrement, restore, transfer).

An alternative to storing random data in the 16 byte-wide blocks is to configure them as "bloc valeur" ("''Value Blocks''" en anglais). Value blocks allow performing electronic purse functions (valid commands are: read, write, increment, decrement, restore, transfer).

           [  Value  ]  [  ~Value  ]  [  Value  ]  [A  ~A  A  ~A]</nowiki>

           [  Value  ]  [  ~Value  ]  [  Value  ]  [A  ~A  A  ~A]</nowiki>

=== Bloc Fabricant (Secteur 0, Bloc 0) ===

==== Bloc Fabricant (Secteur 0, Bloc 0) ====

Sector 0 is special since it contains the bloc Fabricant ("''Manufacturer Block''" en anglais). This block contains the manufacturer data, and is read-only. It should be avoided unless you know what you are doing.  

Sector 0 is special since it contains the bloc Fabricant ("''Manufacturer Block''" en anglais). This block contains the manufacturer data, and is read-only. It should be avoided unless you know what you are doing.  

               0      [                            Data                          ]  Data</nowiki>

               0      [                            Data                          ]  Data</nowiki>

== Accéder à la mémoire de l'EEPROM ==

=== Accéder à la mémoire de l'EEPROM ===

To access the EEPROM on the cards, you need to perform the following steps:

To access the EEPROM on the cards, you need to perform the following steps:

# Once authenication has succeeded, and depending on the sector permissions, you can then read/write/increment/decrement the contents of the specific block. Note that you need to re-authenticate for each sector that you access, since each sector can have it's own distinct access keys and rights!

# Once authenication has succeeded, and depending on the sector permissions, you can then read/write/increment/decrement the contents of the specific block. Note that you need to re-authenticate for each sector that you access, since each sector can have it's own distinct access keys and rights!

== Note sur l'Authentification ==

=== Note sur l'Authentification ===

Before you can do access the sector's memory, you first need to "authenticate" according to the security settings stored in the Sector Trailer. By default, any new card will generally be configured to allow full access to every block in the sector using Key A and a value of 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF. Some other common keys that you may wish to try if this doesn't work are:

Before you can do access the sector's memory, you first need to "authenticate" according to the security settings stored in the Sector Trailer. By default, any new card will generally be configured to allow full access to every block in the sector using Key A and a value of 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF. Some other common keys that you may wish to try if this doesn't work are:

               0XAB 0XCD 0XEF 0X12 0X34 0X56</nowiki>

               0XAB 0XCD 0XEF 0X12 0X34 0X56</nowiki>

== Carte MiFare Classic 1K - Exemple ==

=== Carte MiFare Classic 1K - Exemple ===

Voici un exemple avec un carte MiFare Classic toute neuve.

Voici un exemple avec un carte MiFare Classic toute neuve.