|Version 1 (modified by annette, 17 months ago) (diff)|
SSH setup for PUMA to Archer
Please Note: These instructions assume that you DO NOT already have an ssh-key set up on PUMA.
1. Generate the authentication key on PUMA and install it on ARCHER
Run the install-ssh-keys script. This will take you through ssh-key creation and copy the key over to ARCHER.
puma$ source ~um/um-training/install-ssh-keys <archer-user-name>@login.archer.ac.uk
When prompted to Enter passphrase, this should be a fairly complicated and unguessable passphrase. You can use spaces in the pass phrase if it helps you to remember it more readily. It is recommended that you don’t use your password in case it is hacked.
Warning: DO NOT use an empty passphrase as this presents a security issue.
After generating your ssh-key, the script will copy it over to ARCHER.
When prompted for Password, enter your Archer password.
2. Verify the authentication works
puma$ ssh <archer-user-name>@login.archer.ac.uk Enter passphrase for key '<puma-user-name>'@puma.nerc.ac.uk: [TYPE_YOUR_PASSPHRASE]
If you don’t get asked for your Passphrase (i.e. DSA key), then something has gone wrong. In this case, make sure the public key, was successfully copied over to ARCHER by logging into ARCHER and opening the file ~/.ssh/authorized_keys. It should contain something similar to:
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAt1JmHYgsuf0UWVLqNqnDSaUUP2xJ+Um0H5WnUt/i 2mxhlBrwOtvVWRjnzo5EcylZJs/Cg5JVe4UR6toqNXbZG1RXscLQnQoPAvzFoWLzfP7Q3lrzeC1S kM2FWfWC38ga3Svs6fm63/I7WmJy+4D8BWWaXj/9yM1OskFj6yfWItr150rwwNauOQbWJhl7I/Kk fhVPBvZ9vHiAK4cjUMQ9fFS1dij3GSBmOfu2RuMgNNg9y1MLSzEk2242F4tOg7paTk7wwUZ+ZLqR BtT2aREnjIGI7KvACBZD1y40tXXPIZw9m2Dl0dK7mFQ2/YFWh2/NAmkFMXzDOmkg0biq1m+QKw== ros@puma
Once you have this part working, log out of Archer.
3. Start up ssh-agent
Run the following command and type your passphrase:
puma$ ssh-add Enter passphrase for ~/.ssh/id_dsa (<puma-user-name>@puma.nerc.ac.uk): [TYPE_YOUR_PASSPHRASE]
You may need to do this every time a new ssh-agent is started, i.e. every time you re-start your local session.