# This is an example configuration file for the chipcard server. 
# Such a file is used by "chipcardd". 
# Please see "man 5 chipcardc.conf" for more details.

#
# specifies the service type. Possible values are:
# - "net"    for network services, allowing other machines to use this server
# - "local"  for local services only (uses Unix Domain Sockets)
#
type="net"

#
# address to bind the server to. This is the address chipcardd listens on
# for client requests. 
# If the service type is "net" then this must be a valid IP address (or
# "0.0.0.0" to bind to every interface). If the service type is "local" then
# this must be the name of a file to be used for communication. This name
# must then be used by the clients as well.
#
address="192.168.115.2"
# address="/tmp/chipcardd-socket"

#
# TCP port to bind to. This is the port chipcardd listens on for
# client requests. It defaults to "32891". This is only needed if service
# type is "net". For "local" this is not needed.
#
port="32891"

#
# time to wait for client requests per round (in millisends)
# Please see "man 5 chipcardd.conf" for an explanation.
# Recommended value is 750
#
timeout="750"

#
# number of client requests to handle per round.
# Recommended value is 20
#
maxmsg="20"

#
# set to "0" to disable the card server. Upon startup chipcardd checks
# this value. If it is zero then chipcardd will sleep without actually
# accessing the readers listed in this file. "0" is also assumed if there
# is no configuration file at all. You can then send the signal SIGHUP or
# SIGCONT to chipcardd to make it recheck the configuration.
#
enabled="0"

#
# a reader sections contains information about one reader.
#
[reader/1]

#
# manufacturer of the reader. Currently the following values are known:
#  "kobil"    for Kobil devices
#  "towitoko" for Towitoko devices (like Chipdrive etc)
#  "cyberjack for Reiner SCT Cyberjacks
#  "other" for other devices.
# For each reader type there must be a driver description file. For the
# types listed above these files are already supplied by Libchipcard.
#
readertype="kobil"

#
# driver type. LibChipCard currently supports the two most important driver
# types:
#  "ctapi" for CTAPI drivers (most manufacturer provide such a driver)
#  "pcsc" for PCSC (SCard, M.U.S.C.L.E) drivers
#
drivertype="ctapi"

#
# path and name of the driver
# please see "man 5 chipcardd.conf" for a list of known driver names.
#
driver="/usr/local/lib/libct_b1.so"

#
# name of the reader. The name is ignored for CTAPI drivers, but PCSC
# drivers need the exact name by which PCSC identifies the reader.
#
name="kobil1"

#
# tells LibChipCard where your reader is connected. Possible values are 
# defined by the corresponding driver description file, but common values
# are:
# "COM1" to "COM4" for serial ports (used by mice and modems)
# "LP1" to "LP2" for parallel ports (used by printers)
# "USB0" to "USB3" for USB devices
# If the "drivertype" is "other" then you must fill in a numeric value.
# Most drivers accept values between 0 and 5
#
port="COM2"

#
# comma separated list of attributes of the reader. 
# The following values may appear in the list:
#  "keypad"  indicates that the reader has a keypad which you want to use
#  "display" reader has a display
# Missing of one of those attributes in the list means missing of that
# feature. The Kobil Kaan Professional in this example has a keypad AND a
# display, so these attributes are listed here. If you don't want to use
# the keypad for secure pin verification then simply omit the corresponding
# attribute. That makes libchipcard think the reader has none.
#
flags="keypad","display"