 |
Using JAP at the command line
Switch im JAP
Type
java -jar JAP.jar --console
to start JAP without graphical user interface. If a configuration file exists (jap.conf),
it is read and used, otherwise a new configuration is created. There is no control interface
for the command line yet, but JAP will automatically (re-)connect if you have specified
this in the graphical view before.
Using the Mix executable as local anonymizer proxy
If you have successfully installed the Mix server binary, you may also use it as
a local anonymizer proxy for your web browser instead of the graphical JAP client.
Choosing the cascade
Before using the software as a local proxy you have to decide which mix-cascade to use.
You can use JAP to get the addresses of all currently available Mixes. The address of the
'Dresden-Dresden'-cascade for instance is:
mix.inf.tu-dresden.de:6544
If you know the address of an InfoService, you can directly 'ask' it about
cascade addresses, for example the Dresden InfoService:
http://infoservice.inf.tu-dresden.de/cascades
There are some other commands it accepts, try mixes and
status.
Starting the local proxy
Now you are ready to start the program. The parameters are:
-? --> list all parameters
-j --> to tell the mix to act as local proxy (like JAP)
-p [IP:]Port --> local port to use (and IP if given)
-n mix.inf.tu-dresden.de:6544
--> to which cascade to connect ('Dresden-Dresden' in this example)
Optional parameters:
-l <logdir> --> Directory where logfile should be placed (if omitted syslog is used)
-d --> to tell the mix to be a daemon (run in background)
If you have started the local proxy you should get messages like:
[2001/05/03-11:54:26, info ] Anon proxy started!
[2001/05/03-11:54:26, info ] Using: OpenSSL 0.9.6 24 Sep 2000!
[2001/05/03-11:54:26, info ] Starting MIX...
[2001/05/03-11:54:26, info ] Try connecting to next Mix...
[2001/05/03-11:54:26, info ] connected!
[2001/05/03-11:54:26, info ] Chain-Length: 2
| |
|
