This is a collection of test programs to check if the the current
implementation for the HBCI-relevant chipcard functions work with
your card.

There will be NO tests involving real HBCI servers. The tests will
only try to execute some cryptographic functions on the chipcard which
are needed later to use HBCI-RDH-profiles RDH-3 to RDH-9.

To run the tests, follow these steps:

1) Modify config/config-ctapi.sh (or config\config-ctapi.bat if you
   are using Windows). The variable CTAPI must be set to the shared 
   library containing the CTAPI driver for your chipcard terminal. 

   For me (under Linux), this is libct.so for a Kobil terminal,
   libctapi-cyberjack.so for a ReinerSCT device, libtowitoko.so for an 
   old device from Towitoko etc. Windows users typically find the
   CTAPI drivers somewhere under <WINDOWS>\system32, they often contain
   "ct" in the filename, and have the extension .dll.


2) You need a "bridge" between Java and the CTAPI library for your
   terminal driver. You find precompiled bridge libraries for some
   platforms in the "lib" directory.

   Choose the correct one for your system, copy it to the directory
   containing the executable scripts (*.sh and *.bat) and rename it 
   according to the following rules: on Linux platforms, rename the 
   correct file to libhbci4java-ctapi.so. On Windows platforms, rename 
   it to hbci4java-ctapi.dll.

   An example: you are on an 64-Bit-Linux system. So you change to
   the directory containing all the executable shell scripts and run

     cp lib/libhbci4java-ctapi-linux-64.so ./libhbci4java-ctapi.so

   On a Windows system you would execute

     copy lib\hbci4java-ctapi-win32.dll .\hbci4java-ctapi.dll


3) Change into the directory containing all the shellscripts (*.sh resp. 
   *.bat) and run each of them in the suggested order. Linux users
   should run 01-data.sh, 02-hash.sh etc. Windows user should run
   01-data.bat, 02-hash.bat etc.

   You will first see a small description explaining what will
   happen. After this you can press ENTER to really start the
   execution of the test or hit Ctrl-C to abort it.

   Important: for most of the tests you have to enter the CSA PIN
   or the SIGNATURE PIN on the chipcard terminal. Be careful - if
   this fails, dont try again and again, because this could lock
   your card!


4) Every tool creates some log output in the log directory. To
   support the developer of Chipcards4Java (that's me ;-) ), 
   please create an archive (tar, zip, whatever) with as much
   of these files as you want (ideally, with ALL of them) and
   send it to hbci4java@kapott.org.

   Do this, even if everything seems to be OK, because the output
   may contain detailed information about strange behaviour, which 
   is currently handled correctly, but which is not expected, so 
   this special case could break in the future if nobody knows
   about it.

   Special note for Windows users: The Linux scripts run the test
   programm and filter the output with "tee", which is a tool that
   displays the output on the console AND writes it to a log file
   (log/XXX.out). For Windows such a feature does not exist (at
   least not without installing special software), so the Windows
   .bat files will NOT write the output into a log file. If you need
   some help for one of the test programs, please manually copy
   the output from the console into a separate log file and add
   it to the files in the log directory before sending them to me.


-stefan-
hbci4java@kapott.org