1nfc-mfclassic(1)                 NFC Utilities                nfc-mfclassic(1)
2
3
4

NAME

6       nfc-mfclassic - MIFARE Classic command line tool
7

SYNOPSIS

9       nfc-mfclassic f|r|R|w|W a|A|b|B u|U<uid> DUMP [ KEYS [f] ]
10
11

DESCRIPTION

13       nfc-mfclassic is a MIFARE Classic tool that allow to read or write DUMP
14       file using MIFARE keys provided in KEYS file.
15
16       MIFARE Classic tag is one of the most widely used RFID tags.
17
18       The firmware in the NFC controller supports authenticating, reading and
19       writing  to/from  MIFARE Classic tags. This tool demonstrates the speed
20       of this library and its ease-of-use. It's possible to  read  and  write
21       the  complete  content  of a MIFARE Classic 4KB tag within 1 second. It
22       uses a binary MIFARE Dump file (MFD) to store the keys and data for all
23       sectors.
24
25       Be cautious that some parts of a MIFARE Classic memory are used for r/w
26       access of the rest of the memory, so please read the tag  documentation
27       before experimenting too much!
28
29       The  f  option  to format the card will reset all keys to FFFFFFFFFFFF,
30       all data to 00 and all ACLs to default.
31
32       The W option allows writing of special MIFARE cards that  can  be  'un‐
33       locked' to allow block 0 to be overwritten. This includes UID and manu‐
34       facturer data. Take care when amending UIDs to set the correct BCC (UID
35       checksum). Currently only 4 byte UIDs are supported.
36
37       Similarly,  the  R  option allows an 'unlocked' read. This bypasses au‐
38       thentication and allows reading of the Key A and Key B data  regardless
39       of ACLs.
40
41       R/W  errors  on some blocks can be either considered as critical or ig‐
42       nored.  To halt on first error, specify keys with lowercase ( a or b ).
43       To ignore such errors, use uppercase ( A or B ).
44
45       When  using multiple tags infront of a reader, the U option can be used
46       to supply the UID of tag to be read or written. Append the  hexadecimal
47       UID to the U option. For example U01ab23cd for the 4 byte UID 0x01 0xab
48       0x23 0xcd. Using the u parameter instead will use whatever  libnfc  de‐
49       cides which generally is the lowest UID.
50
51       ***  Note  that W and R options only work on special versions of MIFARE
52       1K cards (Chinese clones).
53
54

OPTIONS

56       f | r | R | w | W
57              Perform format ( f ) or read from ( r ) or unlocked read from  (
58              R ) or write to ( w ) or unlocked write to ( W ) card.
59
60       a | A | b | B
61              Use  A  or  B MIFARE keys.  Halt on errors ( a | b ) or tolerate
62              errors ( A | B ).
63
64       u | U  Use the default UID ( u ) or supply a valid 4 byte UID (  U<uid>
65              ).
66
67       DUMP   MiFare Dump (MFD) used to write (card to MFD) or (MFD to card)
68
69       KEYS   MiFare  Dump  (MFD) that contains the keys (optional). Data part
70              of the dump is ignored.
71
72       f      Force using the keyfile KEYS even if UID  does  not  match  (op‐
73              tional).
74
75

BUGS

77       Please report any bugs on the libnfc issue tracker at:
78       https://github.com/nfc-tools/libnfc/issues
79

LICENCE

81       libnfc  is licensed under the GNU Lesser General Public License (LGPL),
82       version 3.
83       libnfc-utils and libnfc-examples are covered by the  the  BSD  2-Clause
84       license.
85
86

AUTHORS

88       Adam Laurie <adam@algroup.co.uk>,
89       Roel Verdult <roel@libnfc.org>,
90       Romain Tartière <romain@libnfc.org>,
91       Romuald Conty <romuald@libnfc.org>.
92
93       This manual page was written by Romuald Conty <romuald@libnfc.org>.  It
94       is licensed under the terms of the GNU GPL (version 2 or later).
95
96
97
98libnfc                           Nov 02, 2009                 nfc-mfclassic(1)
Impressum