You can use perldoc to read this document: perldoc README.client.
This document details all the necc. information to run a DiCoP client.
The Dicop-Client package is a part of the Dicop server/client package and contains all the neccessary parts to run a client, inclusive bundled modules from the Dicop::Base package.
You can create a Dicop-Client package by doing the following steps:
Copy the matching Dicop-Server and Dicop-Base packages into the same directory and in the following steps replace the version numbers with the version you got:
tar -xzf Dicop-Server-3.04.tar.gz
tar -xzf Dicop-Base-3.04.tar.gz
cd Dicop-Server-3.04
./build/bundle
This will create a Dicop-Client bundle in the current directory.
You can simple unzip this client bundle into a directory.
There is no need to install anything, except maybe some Perl modules on some platforms, please see below for a list.
The only thing you might want to do is to edit the configuration file inside config/.
It is possible to specify the most important options on the command line, though, so you can even skip this step:
Rename the file config/client.cfg.sample to config/client.cfg.
Change the server URL and port settings, and maybe specify the id.
Here is a sample client start:
./client --id=123456 --server=192.168.0.1:8888
You will need Perl v5.8.1 or better (Perl v5.8.8 recommended), for Windows you need to use ActiveState Perl 8xx from http://www.activestate.com/Products/ActivePerl/.
For non-Windows platforms you will probably need some additional modules. All of these modules can be found via http://search.cpan.org/.
Please see the platform specific README files for more details.
The client needs some additional perl modules to work properly. You can either install all of them at the target machine, or bundle them together with the client (for modules that consist only of pure Perl). See "Client.pod" in doc for how to automatically update the client on each machine.
The client should run under Windows, Linux, MAC OS, BSD, Debian, Solaris etc. OS/2 *should* work, but we could not test this lately due to lack of a working OS/2 system.
The client should also work under armv4l linux - but we tested it only one a Compaq iPAQ H3870 running kernel 2.4.18-hh6 with Perl v5.004 and v5.005 in conjunction with --via=wget (since LWP was not easily available). See http://www.handhelds.org/|http://www.handhelds.org/ for how to obtain and install Linux for the iPAQ.
However, we can not guaranty that it will work on your platform. If you experience any problems, please contact us (see below).
A Dicop client will communicate with the Dicop server, maybe via a Dicop proxy. It will also download files from a file server as instructed by the Dicop server.
The actual work, however, is done by workers. These workers must be compiled for the platform the client runs under.
To develop workers for a Dicop system, please use the Dicop-Workerframe package, as it makes this very easy.
(C) Bundesamt fuer Sicherheit in der Informationstechnik 1998-2006.
For licensing information please refer to the LICENSE file.
Please see the README.
