* Pigeon (jah.pigeon@ukonline.co.uk) [030208 20:16]: > > > debug3: Not a RSA1 key file /root/.ssh/id_rsa. > (and the same for id_dsa) > > Looking in these files, I find they don't look right compared to the > id_?sa.pub files. The .pub files contain "ssh-rsa fv487t509n0etcetcetc= > root@pigeon" all as one long line. The private key files contain > "-----BEGIN RSA PRIVATE KEY-----" followed by the key as 12 separate > lines and an "-----END......" line. > > So, I take my text editor to the private key files and change them to > the same format as the public key files. It still doesn't work, but > the error message changes: > > debug3: Not a RSA1 key file /root/.ssh/id_rsa. > key_read: uudecode ptu5087509nrounrin975tetcetcetc= root@pigeon > failed > > Does that mean anything to anyone? Yup. Your ssh is expecting ~/.ssh/id_rsa to contain a version 1 rsa key, as would be generated by using "ssh-keygen -t rsa1". That's the kind of key ssh would use when trying to connect with protocol version 1. Does 'ssh -2 remotehost' work? If so, try setting 'Protocol 2' (or 'Protocol 2,1') in your ~/.ssh/config or /etc/ssh/ssh_config . So you should either generate a version 1 key (in ~/.ssh/identity, for convention's sake) or connect using protocol version 2. If I'm incorrect about why it's failing, some more of that -vvv output and/or your ssh_config would help. good times, Vineet -- http://www.doorstop.net/ -- http://www.eff.org/
Attachment:
pgphZZcdNpFE1.pgp
Description: PGP signature