2.1. Developer CVS Access via SSH (Version 1, RSA)

Only project developers can access the CVS tree via this method. SSH1 must be installed on your client machine. If you have SSH version two, add
Host subversions.gnu.org
Protocol 1

In my case, I simply re-installed ssh, and made sure both Protcol 1 and 2 were allowed and then put in
Protocol 1,2
in my ~/.ssh/config file.

Getting a ssh1 key is quite simple. You may either use an already existing ssh1-key (e.g. the one you already use to encrypt/sign your mail) or create a new one.

2.1.1. Use an existing ssh1-key

Copy the contents of the public part of the key (usually the file ~/.ssh/identity.pub to the ssh-key text field at Savannah (see below). Add the line
export CVS_RSH=ssh
to your .profile.

2.1.2. Create a new ssh1-key (using OpenSSH)

  1.  ssh-keygen [-i ~/.ssh/key_file_name] -t rsa1  
    key_file_name is the name of the key you want to create. If you want to create your primary key (the key you want to use for mail etc.) you can drop the part in brackets. In this case you will find the key file in ~/.ssh/identity.pub.

  2. Then copy and paste the contents of the public part of the key (the file ~/.ssh/key_file_name.pub to the ssh-key text field at Savannah (see below). Be sure not to copy line breaks.

  3. If you created a your primary key,add the line
    export CVS_RSH=ssh
    to your .profile.

    If you created a new key particularly for the cvs, enter the following lines
     echo "#! /bin/sh\nssh -i ~/.ssh/key_file_name $@" > ~/bin/ssh_cvs
    chmod +x ~/bin/ssh_cvs
        	    	
    Add the line
    export CVS_RSH=ssh_cvs
    to your .profile.

2.1.3. Uploading your SSH1-Key

Copy and paste the public part of the ssh1-key to savannah.gnu.org using https://savannah.gnu.org/account/editsshkeys.php.