From bf538445ae6a06c741658a38eb8df81bde45c94a Mon Sep 17 00:00:00 2001 From: Louwrentius Date: Sat, 14 Mar 2009 23:21:23 +0000 Subject: [PATCH] Edited wiki page through web user interface. --- wiki/Manual2.wiki | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/wiki/Manual2.wiki b/wiki/Manual2.wiki index 7bbfa71..9edacc6 100644 --- a/wiki/Manual2.wiki +++ b/wiki/Manual2.wiki @@ -42,8 +42,11 @@ drwxr-xr-x+ 51 ppss staff 1,7K 14 mrt 17:45 .. The result is a private and a public key (.pub). The private key is the key that needs to be distributed to all nodes in order to be able to logon to the server. - # Add the SSH key to the authorized_keys file of the 'ppss' user on the server. - # Add the SSH key to the authorized_keys file of the 'ppss' user on the client. + # Add the public SSH key to the authorized_keys file of the 'ppss' user on the server. + # Add the public SSH key to the authorized_keys file of the 'ppss' user on the client. + +This is necessary if you want to deploy PPSS on the nodes using PPSS in an automated fashion. The alternative is to manually copy PPSS and all necessary files to each node by hand. + # Create a 'known_hosts' file containing the public key of the server. When a node connects to the server for the first time, SSH wil show you the fingerprint of the server and ask if it is ok to connect to this host. To prevent this question, you must perform one of these actions: