pcsc-spy(1) [centos man page]

PCSC-SPY(1)							    PC/SC lite							       PCSC-SPY(1)

NAME

       pcsc-spy - A PC/SC spy command

SYNOPSIS

       pcsc-spy [-n|--nocolor] [-d|--diffable] [-h|--help] [fifo_filename]

DESCRIPTION

       pcsc-spy displays PC/SC calls of an application. It must be used with the libpcscspy.so library.

       To be able to spy the PC/SC layer, the application flow must be modified so that all PC/SC calls are redirected. Two options are available:

       - the application is linked with libpcsclite.so.1
       - the application loads the libpcsclite.so.1 library using dlopen(3)

OPTIONS

       -d, --diffable
	   Demove the variable parts (like handler values) from the output so that two execution can be more easily compared.

       -h, --help
	   Display a short help text.

       -n, --nocolor
	   Disable the output colorization (if you want redirect the output in a file for example).

       -v, --version
	   Print the version of the pcsc-spy program plus a copyright, a list of authors.

EXAMPLES

   Applications linked with libpcsclite.so.1
       We will use the standard LD_PRELOAD loader option to load our spying library.

       Example:
	LD_PRELOAD=/usr/lib/libpcscspy.so pcsc_scan

   Application loading libpcsclite.so.1
       This is the case for the PC/SC wrappers like pyscard (for Python) and pcsc-perl (for Perl). The LD_PRELOAD mechanism can't be used. Instead
       we replace the libpcsclite.so.1 library by the spying one.

       You may use install_spy.sh and uninstall_spy.sh to install and uninstall the spying library.

       Using the spying library without pcsc-spy is not a problem but has side effects:

       - a line "libpcsclite_nospy.so.1: cannot open shared object file: No such file or directory" will be displayed

       - some CPU time will be lost because of the PC/SC calls redirection

   Starting the spy tool
	pcsc-spy

       If a command argument is passed we use it instead of the default ~/pcsc-spy FIFO file. It is then possible to record an execution log and
       use pcsc-spy multiple times on the same log.

       To create the log file just do:

	mkfifo ~/pcsc-spy
	cat ~/pcsc-spy > logfile

       and run your PC/SC application.

   Mac OS X
       The installation is not automatic. In the pcsc-lite/src/spy directory do:
	make framework

       Then copy the PCSC.framework directory in /tmp
	cp -a PCSC.framework /tmp

       Copy the official PCSC.framework (binary only) in /tmp
	cp /System/Library/Frameworks/PCSC.framework/PCSC /tmp

       Run the application to debug as:
	DYLD_FRAMEWORK_PATH=/tmp pcsctest

FILES

       ~/pcsc-spy FIFO file is used by libpcsclite.so.1 to send the raw log lines

SEE ALSO

       pcscd(8)

AUTHOR

       This manual page was written by Ludovic Rousseau <rousseau@free.fr>

pcsc-lite 1.8.8 						    2012-08-25							       PCSC-SPY(1)

PCSCD(8)							    PC/SC Lite								  PCSCD(8)

NAME

       pcscd - PC/SC Smart Card Daemon

SYNOPSIS

       pcscd [options]

OPTIONS

       -a, --apdu
	      log APDUs and SW using the debug method (see --debug).

       -c, --config file
	      Specifies the file file as an alternate location for /etc/reader.conf.

       -f, --foreground
	      Runs pcscd in the foreground and sends log messages to stderr instead of syslog(3).

       -d, --debug
	      use the lowest log level. Any log message of this level or above will be sent to stderr or syslog(3) depending on the use of --fore-
	      ground.

       --info use info log level. This is the default log level.

       --error
	      use error log level.

       --critical
	      use critical log level.

       The log levels are ordered as: debug < info < error < critical. Use a log level l will log this level and all the levels above it.

       -h, --help
	      Displays information about the pcscd command line

       -v, --version
	      Displays the program version number

       -H, --hotplug
	      Ask pcscd to rescan the USB buses for added or removed readers and re-read the /etc/reader.conf file to detect added or removed non-
	      USB readers (serial or PCMCIA).

DESCRIPTION

       pcscd is the daemon program for pcsc-lite and the MuscleCard framework. It is a resource manager that coordinates communications with smart
       card readers and smart cards and cryptographic tokens that are connected to the system.

       pcscd is normally started at boot time from /etc/init.d/pcscd.  It allows applications to access smart cards and  readers  without  knowing
       details of the card or reader.

       pcscd coordinates the loading of drivers for card readers.

       The purpose of pcsc-lite is to provide a cross compatible API (called winscard) for migrating Windows based PC/SC applications to Unix.

       At startup, pcscd loads the smart card reader drivers specified in the /etc/reader.conf file (or specified using --config file).

SERIAL SMART CARD READER DRIVERS

       Smart  card  reader  drivers  are  placed in the /usr/lib64/readers directory. Each driver is simply an .so file.  pcscd locates the driver
       using the /etc/reader.conf file.  See the reader.conf(5) manual page for more information.  Drivers  are  available  at	http://www.muscle-
       card.com/drivers.html.

USB SMART CARD READER DRIVERS

       USB  smart  card reader drivers are located in /usr/lib64/readers directory as a bundle. You shall not add a USB driver in /etc/reader.conf
       file.

FILES

       /etc/reader.conf : Reader configuration file

       /etc/init.d/pcscd : pcscd startup script

       /var/run/pcscd/pcscd.pid : process id of the running pcscd

       /usr/lib64/readers : directory containing bundles for USB drivers

SEE ALSO

       bundleTool(8), reader.conf(5), syslog(3)

AUTHORS

       David Corcoran <corcoran@musclecard.com> and Ludovic Rousseau <ludovic.rousseau@free.fr>

Muscle								   January 2007 							  PCSCD(8)