[gnucash-de] Problem mit Towitoko CHIPDRIVE pinpad SPR532
Clemens Janssen
clemens.janssen at xjns.de
Die Jul 29 22:31:03 CDT 2003
Hallo Martin,
siehe unten ...
Am Dienstag, 29. Juli 2003 19:18 schrieb Martin Preuss:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Moin,
>
> On Tuesday 29 July 2003 19:02, Clemens Janssen wrote:
> [...]
>
> > Glückwunsch, das Lesegerät ist verfügbar ;-)
>
> Ok, geht also grundsaetzlich.
>
> > Meine Eingaben:
> > Treiber: Kann ich leer lassen, oder libtowitoko.so.xxx oder
> > libpcsclite.so.xxx angeben. Treibertyp: PCSC; Hersteller:towitoko;
> > Anschluss: COM2
> >
> > Das Ergebnis lässt sich aber nicht speichern!
>
> Du musst das Programm als Root starten. Ansonsten hast Du nicht die
> noetigen Rechte, um die Dateien in den Systemverzeichnissen zu speichern.
>
> > Ich habe chipcard.conf von Hand konfiguriert:
> > ...
> > #
> > type="local"
> > address="/tmp/chipcardd-socket"
> > timeout="750"
> > maxmsg="20"
> > enabled="1"
> > [reader/1]
> > readertype="towitoko"
> > drivertype="pcsc"
> > driver="/usr/lib/libpcsclite.so.0.0.1"
> > name="term1"
>
> Der Name muss genau der sein, den PC/SC verwendet. Schaue dazu einmal in
> der Datei "reader.conf" nach. Die muesste in "/etc/pcsc" oder so liegen.
> Darin steht dann der Friendly-Name. Diesen nimmste und haengst " 0 0"
> (Leerzeichen davor!) an. Das ist der Name. Wenn Dein KCardSetup mit
> PC/SC-Untersuetzung kompiliert wurde (kenne die Debian-Pakete nicht),
> kannst Du die PC/SC-Leser auch automatisch suchen lassen ("Import
> PC/SC"-Button).
>
> > port="COM2"
>
> Ist fuer PC/SC unwichtig, stoert aber auch nicht ;-)
>
> > ...
> > #flags="keypad","display"
> > flags=
>
> Ok, kannst hier spaeter noch "keypad" angeben, sobald das funktioniert
> (konnte Dein Geraet allerdings noch nicht testen, weil ich so eines noch
> nicht gesehen habe. Mache das also am besten erst, wenn das Geraet
> grundsaetzlich laeuft).
>
> [...]
>
> > Type: CTService Code: Service unreachable (13)
> > Server ist nicht erreichnar, eventuell läuft "chipcardd" nicht ?
>
> Schaue einmal nach, ob der chipcardd laeuft:
> ps ax | grep "chipcardd"
>
das Ergebnis ist leider nicht gut:
clemens at dlux:~$ ps ax | grep "chipcardd"
398 ? S 0:00 /usr/sbin/chipcardd --pidfile
/var/run/chipcardd/chipcardd.pid --exit-on-error
400 ? S 0:00 /usr/sbin/chipcardd --pidfile
/var/run/chipcardd/chipcardd.pid --exit-on-error
clemens at dlux:~$
> Dieser Befehl sollte Dir 2 Zeilen anzeigen !
> Ist nur eine zu sehen, schaue einmal in Dein System-Log
> ("/var/log/messages" oder "/var/log/daemon.log", je nach System). Da
> muesste der Chipcard-Daemon den Grund fuer seine Weigerung
> hineingeschrieben haben.
Der Rest von daemon.log:
Jul 29 20:45:30 dlux rpc.statd[392]: Version 1.0.5 Starting
Jul 29 20:45:30 dlux rpc.statd[392]: statd running as root. chown
/var/lib/nfs/sm to choose different user
Jul 29 20:45:30 dlux chipcardd[397]: chipcardd.c: 717: Chipcardd v0.9.1.0
(STABLE) started.
Jul 29 20:45:30 dlux chipcardd[398]: chipcardd.c: 780: Nanny now supervising
daemon 400
Jul 29 20:45:30 dlux chipcardd[400]: chipcardd.c: 950: Initializing daemon.
Jul 29 20:45:30 dlux chipcardd[400]: ctcore.c: 1141: Checking for PC/SC
readers
Jul 29 20:45:30 dlux chipcardd[400]: ctdriver_pcsc.c: 785: SCard error:
8010001d
Jul 29 20:45:30 dlux chipcardd[400]: ctcore.c: 621: Severity: Error Type:
CTCore Code: Driver IO error (2)
Jul 29 20:45:30 dlux chipcardd[400]: ctcore.c: 1149: PCSC supported but not
available
Jul 29 20:45:30 dlux chipcardd[400]: ctcore.c: 244: Added reader "Towitoko
Chipdrive Reader, 0 0" (id=3649)
Jul 29 20:45:30 dlux chipcardd[400]: ctdriver_pcsc.c: 785: SCard error:
8010001d
Jul 29 20:45:30 dlux chipcardd[400]: ctcore.c: 621: Severity: Error Type:
CTCore Code: Driver IO error (2)
Jul 29 20:45:30 dlux chipcardd[400]: ctcore.c: 702: Could not allocate driver
for reader "3649"
Jul 29 20:45:30 dlux chipcardd[400]: ctcore.c: 850: Could not allocate reader
Jul 29 20:45:30 dlux chipcardd[400]: readerserver.c: 301: Could not allocate
reader "Towitoko Chipdrive Reader, 0 0"
## wenn kein Komma, dann Meldung:
## Jul 29 20:30:42 dlux chipcardd[615]: conf.c: 958: Komma expected
## Jul 29 20:30:42 dlux chipcardd[615]: conf.c: 1074: Error in
## /etc/libchipcard/chipcardd.conf:82
Jul 29 20:45:30 dlux chipcardd[400]: chipcardd.c: 407: Severity: Error Type:
CTCore Code: Unknown (5)
Jul 29 20:45:30 dlux chipcardd[400]: chipcardd.c: 410: No reader allocated
Jul 29 20:45:30 dlux chipcardd[400]: chipcardd.c: 1039: No readers in
configuration file
>
> Ansonsten: Hast Du auch die Datei "chipcardc.conf" geaendert (also mit "c"
> vor dem Punkt) ? Da muessen die Adressen/Typen uebereinstimmen (in Deinem
> Fall also beide "local").
als Anhang die Dateien chipcardc.conf und chipcardd.conf
Wie kann es weiter gehen?
Gruß
Clemens
>
>
> Gruss
> Martin
>
>
> - --
> LibChipcard - http://www.libchipcard.de
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.2 (GNU/Linux)
>
> iD8DBQE/Jqx5iVxhnDyjV4MRAkYrAKCGPF8ieuGpJ/pzS6AC5Y5aY9HifQCfX5jX
> r3Msm47dx2fI57cag9h2XqQ=
> =TMNM
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> gnucash-de mailing list
> gnucash-de at lists.gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-de
-------------- nächster Teil --------------
# This is an example configuration file for the client mode. Such a
# file is used by any application that uses libchipcard to access a card
# reader. Please see "man 5 chipcardc.conf" for more details.
#
# time to wait for server responses per round (in millisends)
# Please see "man 5 chipcardc.conf" for an explanation.
# Recommended value is 750
#
timeout="750"
#
# number of server responses to handle per round.
# Recommended value is 20
#
maxmsg="20"
#
# a service section describes the location of a card server which can
# be used to access readers
#
[service/1]
#
# This service here is a network service, so we need to know the IP adddress
# and TCP port of the server
#
type="local"
#
# address or name of a machine running "chipcardd", the card server
# if you only want local access (i.e. not using readers at other hosts in
# your local network) then you can safely use "127.0.0.1". Please note that
# in this case the corresponding "address" setting in the server configuration
# file (chipcardd.conf) shows the same address.
#
address="127.0.0.1"
#
# TCP port the server is listening on. The chipcardd uses "32891".
#
# port="32891"
#
# next service
#
#[service/2]
#
# This service here is a local service. For this kind of service unix domain
# sockets are used. These are basically sockets represented by a file instead
# of an IP address. So we need to know the path and name of the file. The
# TCP port is not needed, since TCP is not used here.
# With this type you can only reach a server on the very same machine, and
# this server must of course use "local" type as well.
#
type="local"
#
# Path and name of the file to be used for communication.
# Please note that the corresponding server must have this name as address in
# its setting, too!
#
address="/tmp/chipcardd-socket"
-------------- nächster Teil --------------
# 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="local"
#
# 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="127.0.0.1"
# 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 exits immediately.
#
enabled="1"
#
# a reader sections contains information about one reader.
#
[reader/1]
#
# manufacturer of the reader. Currently the following values are allowed:
# "kobil" for Kobil devices
# "towitoko" for Towitoko devices (like Chipdrive etc)
# "cyberjack for Reiner SCT Cyberjacks
# "other" for other devices.
#
readertype="towitoko"
#
# 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="pcsc"
#
# path and name of the driver
# please see "man 5 chipcardd.conf" for a list of known driver names.
#
driver="/usr/lib/libtowitoko.so.2.0.0"
#
# 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="Towitoko Chipdrive Reader, 0 0"
#
# tells LibChipCard where your reader is connected. Possible values:
# "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"
flags=