Dear DECF User
You're receiving this message because we have identified you as one of several users whose public key we were unable to convert to OpenSSH format. The reason is because you only have a public key on our server, but not private key on our server.
What you need to do:
1. If you generated a public/private key pair on your localhost and copied the public key onto kepler.
People who do this usually want to connect remotely to kepler w/o a password or to use a passphrase instead of password.
Nothing. You most likely generated an OpenSSH public/private key pair on your local machine and copied the public key onto kepler in order to ssh into kepler with a passphrase or null passphrase. We have a copied and converted this key into your .ssh directory (directory used by OpenSSH). So things should work out of the box.
However, if, after kepler switches over to OpenSSH, you are unable to ssh into kepler with passphrase or null passphrase, you should go ahead and copy your local public key onto kepler's ~/.ssh/authorized_key file.
If you don't know what version of SSH you're running, type ssh -V on the command prompt.
2. If you generated a public/private key pair ON kepler with the aim of ssh'ing from kepler onto any DECF hosts with no passphrase or null passphrase for cluster computing purposes, follow the instructions for converting your keys at
http://www.decf.berkeley.edu/help/apps/ssh/#convertnull
Subscribe To
Posts
Comments