[Nottingham] synchronisation using ftp-update

[Peter Chang]

On Fri, 7 May 2004, David Wolfson wrote:

[snipped much to do about ssh setup]

Okay, let's get back to basics.

1) install and run sshd on your linux box @ work

The defaults are usually fine (on this red hat box, anyway). All I usually
change is the X11Forwarding option which isn't applicable to you unless
you run an X server on your client.

These are the defaults in my sshd_config (they are commented out as they
already in effect):

#RSAAuthentication yes
#PubkeyAuthentication yes
#AuthorizedKeysFile     .ssh/authorized_keys

2) generate a key using ssh-keygen without a passphrase on the client box
(your windows pc)

$ ssh-keygen -P '' -t dsa

3) find the public key (id_dsa.pub) and copy it to the server (your linux
@ work). In your account there, add the client's public key to your
authorized_keys file (usually kept in ~/.ssh/authorized_keys).
So your authorized_keys file read something like

ssh-dsa ABCDE1234....Z david at home

4) test it works from home

$ ssh david at work

5) if you use a passphrase, then look at using an authentification agent

$ exec ssh-agent bash -l

which replaces the current shell with the agent. This in turn sets up the
environment and starts a new login shell as a subprocess. Now you can add
keys to the agent using ssh-add and so any processes using ssh can work
without asking for passphrases.

hth
 Peter



This message has been scanned but we cannot guarantee that it and any
attachments are free from viruses or other damaging content: you are
advised to perform your own checks.  Email communications with the
University of Nottingham may be monitored as permitted by UK legislation.