...
Please make sure that the key is placed in a single line (remove the Carriage Returns).
7. Check access permissions to ~/.ssh and ~/public, they shouldn't be more "open" that drwxr-xr-x:
$ ls -ld ~/.ssh ~/public
If necessary, correct them with this command:
$ chmod 755 ~/.ssh ~/public ~/.ssh/authorized_keys
8. When logged at your Linux/Unix machine, if you have set a key passphrase, use ssh-agent to avoid having to type your passphrase everytime you call cvs/svn. For that just call the following commands in your Linux/Unix machine:
% eval `ssh-agent`
% ssh-add ~/.ssh/id_rsa
% ssh-add -l
If all goes well, the last command should list the key you've added to the key agent, and your SSH commands in this shell have access to your key without further intervention from you.
If already in bash with an ATLAS release set up, I use this script instead:
source ~ahaas/bin/agent.sh
Then try connecting to svn.cern.ch
ssh USERNAME@svn.cern.ch
and accept the server key (only, if the fingerprint is 05:1c:53:5c:2b:cc:70:5f:75:0b:b7:f6:19:fe:f8:8e!).
You shouldn't be prompted for a password, and you should see the message:
*******************************************************************************
* *
* http://cern.ch/ComputingRules : Govern the use of CERN computing facilities *
* *
*******************************************************************************
Interactive login disabled
Connection to svn closed.
which means that ssh access to SVN servers is properly configured.
As you probably realized, when you login on LXPLUS without providing your password, you don't have AFS and Kerberos tokens. In order to be asked for the password while connecting to LXPLUS and not to be asked for it for CVS connections, create ~/.ssh/config file on your Linux/Unix machine, and put the following contents in it:
...