How to configure the Commercial SSH client to use public keys to connect to org.apache.cvs

[Steve Brewin <sb...@synsys.com>]

OK, this should reside elsewhere, but while its fresh in my mind I will
record it here as it may be of use to other committers.

The commercial SSH client can be used to connect to org.apache.cvs, but
there are two issues to be overcome first:

1) Commercial SSH's public keys use the SECSH Public Key Format whereas
openSSL, as used on org.apache.cvs uses it own format, so a key must be
translated to the correct format.

2) As configured on org.apache.cvs, the openSSH server looks for authorized
keys in file '~/.ssh/authorized_keys'. This is not where Commercial SSH
uploads the keys to.

Here is what to do:

1) Use the Commercial SSH client to login to org.apache.cvs using your
password.

2) Use the Commercial SSH client to generate a key-pair and upload the
public key to org.apache.cvs (consult the product's help for details). The
public key will be uploaded to '~/.ssh2'.

3) If it doesn't exist (it didn't for me), create directory '~/.ssh'.

4) On cvs.apache.org, cd to '~/.ssh2' and run 'ssh-keygen -i -f yourkey.pub
>> '../.ssh/authorized_keys'

5) logout and reconnect. If everything worked you will now be told that
org.apache.cvs is willing to accept your certificate.

Job done!

-- Steve

RE: How to configure the Commercial SSH client to use public keys to connect to org.apache.cvs

["Noel J. Bergman" <no...@devtech.com>]

Steve,

Want to submit a patch for http://www.apache.org/dev/committers.html ?
Other pages with related material are:

  http://jakarta.apache.org/site/cvsonunix.html
  http://jakarta.apache.org/site/cvsonwin32.html

	--- Noel