-Install all needed packages
-~~~~~~~~~~~~~~~~~~~~~~~~~~~
-See README for a list of required software. Don't be afraid of the long
-list of unusal libraries: Most of them are only needed for optional
-programs. Autoconf will detect what is installed on your system and
-will only build those executables that can be built with your setup.
-
-
-Install server and client
-~~~~~~~~~~~~~~~~~~~~~~~~~
-Install the package on all machines, you'd like this software to run on:
-
- (./configure && make) > /dev/null
-
-There should be no errors (but probably many warnings about missing
-software). Then, as root,
-
- make install
-
-Setup user list and create rsa keys
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-If you already have your rsa keys, skip this step. If you are new
-to paraslash, you have to generate an rsa key pair for each user you
-want to allow to connect. You need at least one user.
-
-Let's assume that you'd like to run the server on host server_host
-as user foo, and that you want to connect from client_host as user bar.
-
-As foo@server_host, create ~/.paraslash/server.users by typing the
-following commands:
-
- target=~/.paraslash/server.users
- key=~/.paraslash/key.pub.bar
- perms=DB_READ,DB_WRITE,AFS_READ,AFS_WRITE
- mkdir -p ~/.paraslash
- echo "user bar $key $perms" >> $target
-
-This gives bar full privileges.
-
-Change to the bar account on client_host and generate the key-pair
-with the commands
-
- key=~/.paraslash/key.bar
- mkdir -p ~/.paraslash
- (umask 077 && openssl genrsa -out $key)
-
-Next, extract its public part:
-
- pubkey=~/.paraslash/key.pub.bar
- openssl rsa -in $key -pubout -out $pubkey
-
-and copy the public key just created to server_host (you may
-skip this step for a single-user setup, i.e. if foo=bar and
-server_host=client_host):
-
- scp $pubkey foo@server_host:.paraslash/
-
-Finally, tell para_client to connect to server_host:
-
- echo 'hostname server_host' > ~/.paraslash/client.conf
-
-Start para_server