Eternity Service
User's guide

Platform
Tested on: FreeBSD 2.2.x, FreeBSD 3.0 (It is necessary to replace Source/Common/RSAEuro/librsaeuro.a with a version for FreeBSD 
3.0, that is in the same directory).
After some tampering with pthread library it should be possible to run it on Linux too.

Requirements:
Pthread library 	- standard part of FreeBSD distribution.
g++ 			- standard part of FreeBSD distribution.
RSAEURO knihovnu 	- part of Eternity service distribution.
gmake 			- in packages for FreeBSD.
To run service more seriously (not just testing on loopback) an ethernet caard is necessary.

Instalation:
Add a special user (let's call him eternity) and into his home directory unpack the contents of distribution.
It contains Sources, documenttion, binaries and all necessary files.

Compilation
Compilation is driven by Makefiles placed in Source directories. You can compile the whole system:
$cd Source
$gmake
or by 'gmake Mix' or similar you can translate just some part of the system.

Running
Executables are then placed here:
Mix/mix
Client/client
Eso/eso
Bank/bank
Acs/acs

Binaries included in distribution are placed in bin directory.

All servers (mix, acs, eso, bank) accept one switch on the commandline -f that specifies the place of configuration file of the server.

'./eso -f  home/eternity/conf/eso.conf'

Client accepts several other switches, as it serves as user interface. 

-u			upload 		Upload file to Eternity Service
-d			download 	Download Eternity Service
-s <string>		search 		search Eternity Service (using keywords)
-c <file>		config file 	Configuration file of client program
-k <keywords> 		keywords	keywords describing the file
v Eternity Servisu.
-f <filename>		filename 	Local filename that we upload or that we want to store to
-n <count>		number 		of Eso's to ask or to store to
soubor.
-i <fid>		id 		pseudo unique id that is used to identify the file in service

Concrete usage of these switches for practical using the Client program (as downloading and uploading data) is described in help that is a part of Client program and is displayed after running client -h.

When first run, all servers generate needed certificates and publish them on Acs.
The aim of our project was only to prove the ability of the cryptographical protocols (by Tonda Benes) to be implemented. That's why the user interface provides only the minimal set of functions needed for configuring and running the parts of system.

Config files
The basic user interface for all servers are their config files. Their structureand the meaning of different lines is described in comments. 
The directory structure and its meaning is self-explanatory.

In bin subdirectory there are some sample scripts.

runServers			runs mix, acs, bank, and eso so that client can communicate with them

upload, download, search 	perform the specific action and promt the user for input.