Is anyone else having problems getting ssh 2.3.0 to use a DSA key
other than the default ~/.ssh/id_dsa?
Here's the testing procedure: I used ssh-keygen to create
a DSA key in ~/.ssh/id_dsa (without passphrase for testing),
and put the public part in ~/.ssh/authorized_keys2. Then I use
'ssh -2 localhost' to successfully connect using SSH v2. If I move
the private key to (say) id_dsa_other and try connecting with
'ssh -v -2 -i ~/.ssh/id_dsa_other localhost', it fails with (among
other lines from the -v):
debug: authentications that can continue: publickey,password
debug: next auth method to try is publickey
debug: key does not exist: /users/roosen/.ssh/id_dsa
debug: next auth method to try is password
Looking at the source code, I'm not surprised to find that the -i
flag adds only to 'options.identity_files[]' (for RSA keys) and
not to 'options.identity_files2[]' (for DSA keys).
The strange part is, when I reported this to the debian maintainer,
he has no problems getting it to work with the -i flag. So I'm
left wondering how it is that my source code distribution matches
my .deb and neither work :). Anyone else have the same problem?
This happens for 2.2.0 and 2.3.0 (the latest).
Cheers,
Andy Roosen
--
- Andrew R. Roosen, Ph.D.
- Computer Operations Administrator
- Center for Theoretical and Computational Materials Science
- National Institute of Standards and Technology
-
- [EMAIL PROTECTED]
- http://www.ctcms.nist.gov/~roosen/
