Serverprobleme mit Kobil Kaan Standard Plus

# config derived from chipcardc2.conf example
#    copyright   : (C) 2004 by Martin Preuss
#
# Each server section tells a chipcard2 client where a chipcard2-server
# is sitting.
#
server {
  #
  # Connection type the server uses, currently supported are these:
  #
  # - "local"
  #   local server, using Unix Domain Sockets which can only be
  #   connected from the very same machine. In this case "addr" must point
  #   to the socket file used by the server.
  #   Some systems to not support these kinds of sockets (most notably
  #   Win32 systems).
  #   On all other systems this is the recommended type if no authentification
  #   is needed.
  # 
  # - "public"
  #   server using TCP sockets (not encrypted, for security reasons you should
  #   not use such a server with chipcard2)
  #
  # - "private"
  #   server using SSL secured sockets.
  #   New certificates are stored in the folder given by "newcertdir",
  #   received certificates are checked against those in "certdir"
  #   This is the recommended type if "local" is not available.
  #
  # - "secure"
  #   server using SSL secured sockets. In addition to mode
  #   "private" the certificate of the server is checked against
  #   those stored in the "certdir". If the server certificate could
  #   not be found or is invalid the connection is aborted.
  #
  typ="local"

  #
  # address the server is listening on (or socket file if type is "local")
  #
  addr="/tmp/.chipcard2/chipcard2.sock"
  
  #
  # TCP port the server is listening on (not used if type is "local")
  #
  #port="55555"


  # if type is "private" or "secure" the following variables are used
  
  #
  # folder which contains valid SSL certificates (if the certificate of the
  # server is amongst those stored there then the connection is regarded as
  # secure).
  # Please note that this folder must be readable by every user who wants
  # to use libchipcard2-client programs.
  #
  #certdir="/etc/chipcard2-client/certificates/valid"
  
  #
  # this is the folder where newly received SSL certificates are stored.
  # By copying a file from this folder to the one given as "certdir" you
  # tell the SSL code that the certificates inside those files are to be
  # accepted
  #
  #newcertdir="/home/martin/.chipcard2/certificates/new"
  
  #
  # if type is "secure" then the client needs to send a certificate to the
  # server in order to identify itself. This file should be in PEM format.
  # (see OpenSSL documentation)
  # When creating a certificate you should set the "commonName" field in the
  # certificate to the name used to identify yourself to the chipcard2 
  # server (most likely your username or real name)
  #
  #certfile="/etc/chipcard2/client/cert.pem"
  
} # service

# derived from chipcardd2.conf example file
#    copyright   : (C) 2004 by Martin Preuss

# This is the chipcardd2.conf specially modified by Philipp Sternberg for the use of USB readers

# if this is "0" then the server won't start
enabled="1"

server {
  # local server, using Unix Domain Sockets which can only be
  # connected from the very same machine
  typ="local"                 
  addr="/tmp/.chipcard2/chipcard2.sock"
} # server



#Autokonfiguration aktivieren:
int disableAutoConf="0"

#Nicht ttyUSBx devieces werden nur beim Serverstart abgefragt:
int usbScanInterval="0"

#ttyUSBx devices werden alle zehn Sekunden abgefragt:
int usbTtyScanInterval="10"

#Remote Clients (betrifft auch einige lokalen Programme) zulassen
allowRemote="1"

#
# timeout when starting a driver (in seconds)
#
int driverStartTimeout="10"

#
# timeout when starting a reader (including driverStartTimeout, in seconds)
#
int readerStartTimeout="20"

#
# time after which a driver is shut down when idle (in seconds)
#
int driverIdleTimeout="60"

#
# time after which a reader is shut down when idle (in seconds)
#
int readerIdleTimeout="30"

#
# maximum execution time for a command (in seconds)
#
readerCommandTimeout="60"