115 lines
3.2 KiB
Plaintext
115 lines
3.2 KiB
Plaintext
.. highlight:: sh
|
|
|
|
.. _pcsc-relay:
|
|
|
|
################################################################################
|
|
@PACKAGE_NAME@
|
|
################################################################################
|
|
|
|
:Authors:
|
|
- `Frank Morgner <morgner@informatik.hu-berlin.de>`_
|
|
- `Dominik Oepen <oepen@informatik.hu-berlin.de>`_
|
|
:License:
|
|
GPL version 3
|
|
:Tested Platforms:
|
|
- Windows
|
|
- Linux (Debian, Ubuntu, OpenMoko)
|
|
:Potential Platforms:
|
|
Unix-like operating systems (Mac OS, Solaris, BSD, ...)
|
|
|
|
Welcome to @PACKAGE_NAME@. The purpose of @PACKAGE_NAME@ is to relay a smart
|
|
card using an contact-less interface. Currently the following contact-less
|
|
backends are supported:
|
|
|
|
- `Hardware supported by libnfc`_
|
|
- OpenPICC_
|
|
|
|
Command APDUs are received with the contact-less interface and relayed. The
|
|
Response APDUs are then sent back via RFID. The contact-less data will be
|
|
relayed to one of the following:
|
|
|
|
- to a smart card inserted into one of the systems smart card readers. The
|
|
smart card reader must be accessible with PC/SC.
|
|
- to a :ref:`vicc` that directly connects to :command:`pcsc-relay`. The virtual
|
|
smart card's native interface is used and (despite its name) @PACKAGE_NAME@
|
|
does not need to access PC/SC in this case.
|
|
|
|
With @PACKAGE_NAME@ you can relay a contact-less or contact based smart card
|
|
over a long distance. Also you can use it in combination with the :ref:`vicc`
|
|
to completely emulate an ISO/IEC 14443 smart card.
|
|
|
|
|
|
|
|
.. include:: relay-note.txt
|
|
|
|
|
|
.. include:: download.txt
|
|
|
|
|
|
.. include:: autotools.txt
|
|
|
|
@PACKAGE_NAME@ has the following dependencies:
|
|
|
|
- PC/SC middleware
|
|
- libnfc_
|
|
|
|
===============
|
|
Hints on libnfc
|
|
===============
|
|
|
|
Here is an example of how to get the standard
|
|
installation of libnfc::
|
|
|
|
PREFIX=/tmp/install
|
|
LIBNFC=libnfc
|
|
git clone https://code.google.com/p/libnfc $LIBNFC
|
|
cd $LIBNFC
|
|
autoreconf -i
|
|
# See `./configure --help` for enabling support of additional hardware
|
|
./configure --prefix=$PREFIX
|
|
make
|
|
make install
|
|
|
|
Building @PACKAGE_NAME@ with libnfc is done best using :command:`pkg-config`. The file
|
|
:file:`libnfc.pc` should be located in ``$INSTALL/lib/pkgconfig``. Here is how to
|
|
configure @PACKAGE_NAME@ to use it::
|
|
|
|
./configure PKG_CONFIG_PATH=$PREFIX/lib/pkgconfig
|
|
|
|
|
|
=========================
|
|
Hints on PC/SC middleware
|
|
=========================
|
|
|
|
A PC/SC middleware is included by default in most modern operating systems. On
|
|
Unix-like systems (Linux, OS X, Sun OS) it is realized by PCSC-Lite_. To
|
|
compile @PACKAGE_NAME@ you will need to install the PCSC-Lite headers from
|
|
your distribution.
|
|
|
|
Windows also ships with a PC/SC middleware in form of the Winscard module.
|
|
@PACKAGE_NAME@ can be (cross) compiled with MinGW-w64. Also, Microsoft's
|
|
developement environment Visual Studio includes all necessary data for building
|
|
@PACKAGE_NAME@.
|
|
|
|
|
|
*****
|
|
Usage
|
|
*****
|
|
|
|
.. program-output:: pcsc-relay --help
|
|
|
|
|
|
.. include:: questions.txt
|
|
|
|
|
|
********************
|
|
Notes and References
|
|
********************
|
|
|
|
.. target-notes::
|
|
|
|
.. _`Hardware supported by libnfc`: http://nfc-tools.org/index.php?title=Devices_compatibility_matrix
|
|
.. _libnfc: http://www.libnfc.org/
|
|
.. _OpenPICC: http://www.openpcd.org/OpenPICC
|
|
.. _PCSC-lite: http://pcsclite.alioth.debian.org/
|