Update existing man pages.
This commit is contained in:
parent
994b119c32
commit
9b3dbc272c
6 changed files with 44 additions and 25 deletions
|
@ -5,13 +5,15 @@ nfc-anticol \- Demonstration NFC anti-collison command line tool based on libnfc
|
||||||
.B nfc-anticol
|
.B nfc-anticol
|
||||||
.SH DESCRIPTION
|
.SH DESCRIPTION
|
||||||
.B nfc-anticol
|
.B nfc-anticol
|
||||||
is an anti-collision demonstration tool for ISO/IEC 14443-A tags, performed
|
is an anti-collision demonstration tool for ISO/IEC 14443-A tags, performed by
|
||||||
by custom constructed frames. The first frame must be a short frame which
|
custom constructed frames. The first frame must be a short frame which is only
|
||||||
is only 7 bits long. Commercial SDK's often don't support a feature to send
|
7 bits long. Commercial SDK's often don't support a feature to send frames that
|
||||||
frames that are not a multiple of 8 bits (1 byte) long.
|
are not a multiple of 8 bits (1 byte) long. This makes it impossible to do the
|
||||||
This makes it impossible to do the anti-collision yourself.
|
anti-collision yourself. The developer has to rely on closed proprietary
|
||||||
The developer has to rely on closed proprietary software and should hope it does not contain vulnerabilities during the anti-collision phase.
|
software and should hope it does not contain vulnerabilities during the
|
||||||
Performing the anti-collision using custom frames could protect against a malicious tag that, for example, violates the standard by sending frames with unsupported lengths.
|
anti-collision phase. Performing the anti-collision using custom frames could
|
||||||
|
protect against a malicious tag that, for example, violates the standard by
|
||||||
|
sending frames with unsupported lengths.
|
||||||
|
|
||||||
.SH BUGS
|
.SH BUGS
|
||||||
Please report any bugs on the
|
Please report any bugs on the
|
||||||
|
|
|
@ -1,14 +1,23 @@
|
||||||
.TH NFC-LIST 1 "June 26, 2009"
|
.TH NFC-LIST 1 "June 26, 2009"
|
||||||
.SH NAME
|
.SH NAME
|
||||||
nfc-list \- List NFC targets command line tool based on libnfc
|
nfc-list \- List NFC targets
|
||||||
.SH SYNOPSIS
|
.SH SYNOPSIS
|
||||||
.B nfc-list
|
.B nfc-list
|
||||||
.SH DESCRIPTION
|
.SH DESCRIPTION
|
||||||
.B nfc-list
|
.B nfc-list
|
||||||
utility attempts to select available tags in the field. The NFC
|
is a utility for listing any available targets like ISO14443-A, FeliCa, Jewel
|
||||||
controller is used to perform the selection procedure. This is different for each modulation type.
|
or ISO14443-B (according to the device capabilities).
|
||||||
It tries to find a ISO/IEC 14443 type A, type B, Felica or Jewel Topaz tags.
|
|
||||||
This tool demonstrates that it is possible to setup a simple NFC system using less than 10 lines of code.
|
This tool displays all available information at selection time.
|
||||||
|
|
||||||
|
.SH EXAMPLE
|
||||||
|
For an ISO/IEC 14443-A tag (i.e.Mifare DESFire):
|
||||||
|
|
||||||
|
ATQA (SENS_RES): 03 44
|
||||||
|
UID (NFCID1): 04 45 35 01 db 24 80
|
||||||
|
SAK (SEL_RES): 20
|
||||||
|
ATS (ATR): 75 77 81 02 80
|
||||||
|
Compliant with: ISO/IEC 14443-4
|
||||||
|
|
||||||
.SH BUGS
|
.SH BUGS
|
||||||
Please report any bugs on the
|
Please report any bugs on the
|
||||||
|
|
|
@ -1,6 +1,6 @@
|
||||||
.TH NFC-MFCLASSIC 1 "Nov 02, 2009"
|
.TH NFC-MFCLASSIC 1 "Nov 02, 2009"
|
||||||
.SH NAME
|
.SH NAME
|
||||||
nfc-mfclassic \- MIFARE Classic command line tool based on libnfc
|
nfc-mfclassic \- MIFARE Classic command line tool
|
||||||
.SH SYNOPSIS
|
.SH SYNOPSIS
|
||||||
.B nfc-mfclassic
|
.B nfc-mfclassic
|
||||||
.RI \fR\fBr\fR|\fBw\fR
|
.RI \fR\fBr\fR|\fBw\fR
|
||||||
|
@ -17,10 +17,12 @@ file using Mifare keys provide in
|
||||||
file.
|
file.
|
||||||
|
|
||||||
MIFARE Classic tag is one of the most widely used RFID tags.
|
MIFARE Classic tag is one of the most widely used RFID tags.
|
||||||
The firmware in the NFC controller supports authenticating, reading and writing to/from Mifare Classic tags.
|
|
||||||
This tool demonstrate the speed of this library and its easy-of-use.
|
The firmware in the NFC controller supports authenticating, reading and writing
|
||||||
It possible to read and write the complete content of a Mifare Classic 4KB tag within 1 second.
|
to/from Mifare Classic tags. This tool demonstrate the speed of this library
|
||||||
It uses a binary Mifare Dump file (MFD) to store the keys and data for all sectors.
|
and its easy-of-use. It possible to read and write the complete content of a
|
||||||
|
Mifare Classic 4KB tag within 1 second. It uses a binary Mifare Dump file (MFD)
|
||||||
|
to store the keys and data for all sectors.
|
||||||
|
|
||||||
.SH OPTIONS
|
.SH OPTIONS
|
||||||
.BR r " | " w
|
.BR r " | " w
|
||||||
|
|
|
@ -1,6 +1,6 @@
|
||||||
.TH NFC-MFULTRALIGHT 1 "Nov 02, 2009"
|
.TH NFC-MFULTRALIGHT 1 "Nov 02, 2009"
|
||||||
.SH NAME
|
.SH NAME
|
||||||
nfc-mfultralight \- MIFARE Ultralight command line tool based on libnfc
|
nfc-mfultralight \- MIFARE Ultralight command line tool
|
||||||
.SH SYNOPSIS
|
.SH SYNOPSIS
|
||||||
.B nfc-mfultralight
|
.B nfc-mfultralight
|
||||||
.RI \fR\fBr\fR|\fBw\fR
|
.RI \fR\fBr\fR|\fBw\fR
|
||||||
|
@ -39,6 +39,7 @@ and
|
||||||
are covered by the GNU Lesser General Public License (LGPL), version 3.
|
are covered by the GNU Lesser General Public License (LGPL), version 3.
|
||||||
.SH AUTHORS
|
.SH AUTHORS
|
||||||
Roel Verdult <roel@libnfc.org>
|
Roel Verdult <roel@libnfc.org>
|
||||||
|
Romuald Conty <romuald@libnfc.org>
|
||||||
.PP
|
.PP
|
||||||
This manual page was written by Romuald Conty <romuald@libnfc.org>.
|
This manual page was written by Romuald Conty <romuald@libnfc.org>.
|
||||||
It is licensed under the terms of the GNU GPL (version 2 or later).
|
It is licensed under the terms of the GNU GPL (version 2 or later).
|
||||||
|
|
|
@ -5,11 +5,14 @@ nfc-relay \- Relay attack command line tool based on libnfc
|
||||||
.B nfc-relay
|
.B nfc-relay
|
||||||
.SH DESCRIPTION
|
.SH DESCRIPTION
|
||||||
.B nfc-relay
|
.B nfc-relay
|
||||||
is an utility that demonstrates an relay attack. For this it requires two
|
is an utility that demonstrates an relay attack.
|
||||||
NFC devices. One will emulate an ISO/IEC 14443 type A tag, while the 2nd
|
|
||||||
device will act as a reader. The genuine tag can be placed on the 2nd reader and
|
This tool requires two NFC devices. One device (configured as target) will
|
||||||
the tag emulator can be placed close to the original reader. All communication
|
emulate an ISO/IEC 14443 type A tag, while the second device (configured as
|
||||||
is now relayed and shown in the screen on real-time.
|
initiator) will act as a reader. The genuine tag can be placed on the second
|
||||||
|
device (initiator) and the tag emulator (target) can be placed close to the
|
||||||
|
original reader. All communication is now relayed and shown in the screen on
|
||||||
|
real-time.
|
||||||
|
|
||||||
.SH BUGS
|
.SH BUGS
|
||||||
Please report any bugs on the
|
Please report any bugs on the
|
||||||
|
|
|
@ -5,9 +5,11 @@ pn53x-sam \- PN53x SAM comunication demonstration tool
|
||||||
.B pn53x-sam
|
.B pn53x-sam
|
||||||
.SH DESCRIPTION
|
.SH DESCRIPTION
|
||||||
.B pn53x-sam
|
.B pn53x-sam
|
||||||
utility attempts to test a simple connection with a SAM (Secure Access Module) in several modes.
|
is a utility attempts to test a simple connection with a SAM (Secure Access
|
||||||
|
Module) in several modes.
|
||||||
|
|
||||||
To run this utility you must have a SAM (like the NXP's P5CN072 chip) successfully connected to your PN53x chip.
|
To run this utility you must have a SAM (like the NXP's P5CN072 chip)
|
||||||
|
successfully connected to your PN53x chip.
|
||||||
|
|
||||||
.SH BUGS
|
.SH BUGS
|
||||||
Please report any bugs on the
|
Please report any bugs on the
|
||||||
|
|
Loading…
Add table
Reference in a new issue