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 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
33       'unlocked'  to  allow  block 0 to be overwritten. This includes UID and
34       manufacturer data. Take care when amending UIDs to set the correct  BCC
35       (UID checksum). Currently only 4 byte UIDs are supported.
36
37       Similarly,  the  R  option  allows  an  'unlocked'  read. This bypasses
38       authentication and allows reading of the Key A and Key B  data  regard‐
39       less of ACLs.
40
41       R/W  errors  on  some  blocks  can  be either considered as critical or
42       ignored.  To halt on first error, specify keys with lowercase ( a or  b
43       ). To ignore such errors, use uppercase ( A or B ).
44
45       ***  Note  that W and R options only work on special versions of MIFARE
46       1K cards (Chinese clones).
47
48

OPTIONS

50       f | r | R | w | W
51              Perform format ( f ) or read from ( r ) or unlocked read from  (
52              R ) or write to ( w ) or unlocked write to ( W ) card.
53
54       a | A | b | B
55              Use  A  or  B MIFARE keys.  Halt on errors ( a | b ) or tolerate
56              errors ( A | B ).
57
58       DUMP   MiFare Dump (MFD) used to write (card to MFD) or (MFD to card)
59
60       KEYS   MiFare Dump (MFD) that contains the keys (optional).  Data  part
61              of the dump is ignored.
62
63       f      Force  using  the  keyfile  KEYS  even  if  UID  does  not match
64              (optional).
65
66

BUGS

68       Please report any bugs on the libnfc issue tracker at:
69       http://code.google.com/p/libnfc/issues
70

LICENCE

72       libnfc is licensed under the GNU Lesser General Public License  (LGPL),
73       version 3.
74       libnfc-utils  and  libnfc-examples  are covered by the the BSD 2-Clause
75       license.
76
77

AUTHORS

79       Adam Laurie <adam@algroup.co.uk>,
80       Roel Verdult <roel@libnfc.org>,
81       Romain Tartière <romain@libnfc.org>,
82       Romuald Conty <romuald@libnfc.org>.
83
84       This manual page was written by Romuald Conty <romuald@libnfc.org>.  It
85       is licensed under the terms of the GNU GPL (version 2 or later).
86
87
88
89libnfc                           Nov 02, 2009                 nfc-mfclassic(1)
Impressum