1.3. Preparation

1.3.1. Generate SSH Key

SSH to the server/local host As a user you implement please the following, if still none exists ssh to pair of keys.

$ssh keygen - t rsa

That should look approximately in such a way:

Generating public/private rsa keys pair.

Enter file in which to save the keys (/home/huette/.ssh/id_rsa): Created directory /home/huette/.ssh

Enter passport (empty for NO passport ): enter (nothing else)

Enter same passport again: (also only enter)

Your identification has been saved in /home/huette/.ssh/id_rsa.

Your public keys has been saved in /home/huette/.ssh/id_rsa.pub

The key finger print is: 48:4 f: 7d: d8: ba: a4: 6a: 4c: 8b: 8c: 05: b6: 3b: 4d: 26: 40 huette@localhost

The public key in id_rsa.pub can confidently to all will pass on. If one deposits now the public key on the target computer in the file root/.ssh/authorized_keys, then it is possible to insert in place of the inquiry of the system password the identity defined by a pair of keys to the Authentifizierung.

The following procedure is perhaps simplest:

Client: scp id_rsa.pub root@IP://root then ssh - lroot IP and now man/woman is on the server and can with cd /root change to the Homedir of root. No do change this:

If no directory .ssh exists, create it with mkdir .ssh now and go to this directory

then do a cat ../id_rsa.pub >> authorized_keys and everything will be good.

Tap: Test if you can login to the server now with

ssh - lroot IP without password

1.3.2. Postgres

The Installer Program has install Postgres, so you have now to do a little preparation. Create the cuon Database. Be the user postgres with

              

su postgres
createdb - E utf-8 cuon

              
            

              
createuser admin
and type Yes on the question if this role should be a superuser 
            

Now do check the plpgsql language. The creation of Proceduren and triggers happens with plpgsql, so this language must be installed. The following call as the postgres user create this:

createlang - D cuon plpgsql

And now edit the postgres configuration file pg_hba.conf (located at /etc/postgres-dir).Set the local connections and local IP connections to trust

# "local" is for Unix domain socket connections only
local   all         all                               trust
# IPv4 local connections:
host    all         all         127.0.0.1/32          trust
# IPv6 local connections:
host    all         all         ::1/128               trust

1.3.3. SSL Certificate

If you will connect to the Cuon Server over Internet, it is recommended to activate a security connection. Otherwise all data, passwords etc. are theoretically readable by each other! The standard server listen on 7580 for security connection (https) and 7080 stands for unencrypted connection (should become equivalent by Firewall closed). The own certificates can provide you as follows:

openssl genrsa -out serverkey.pem 2048
openssl req -new -x509 -key serverkey.pem -out servercert.pem -days 1095 

Copy they then the beiten certificates from /etc/cuon. Then you start the cuonxmlrpc server. You can make a first test as follows:

openssl s_client -connect xxx.xxx.xxx.xxx:7580 -ssl3

Please set for xxx.xxx.xxx.xxx your server IP.

1.3.4. Testing the Server

To do a first tests of the installation the current postgresql server and cuonxmlrpc are enough. In order to have a better overview of the activities it is advisable to start the cuonxmlrpc server by hand :

python /usr/share/cuon/cuon_server/src/server_xmlrpc

Then open an other shell window and view the log files of the SQL database :

tail - f /var/log/postgresql/main.log

if all is ok, you can use the Linux startscripts now. These start please in such a way:

• /etc/init.d/cuonxmlrpc start

• /etc/init.d/cuonweb start

• /etc/init.d/cuonreport start

1.3.5. That's all

Yes, now you can go on with the Setup-Tool, you may now do the same steps as they are describe at the chapters Configuration and Update.