> C:\>ssh2 -v 2 user@site
> debug: SshAppCommon/sshappcommon.c:154: Allocating global SshRegex context.
> debug: SshConfig/sshconfig.c:2184: Unable to open C:/Documents and
> Settings/rmager/Application Data/SSH/ssh2_config
> debug: Connecting to 2, port 22...
> ssh2: FATAL: Connecting to 2 failed: No address associated to the name
You tried to connect to a computer named "2". This failed because you
don't have a computer named "2" in your domain.
Try "ssh2 -v user@site" or "ssh2 -v -l user site".
If you were trying to force protocol version 2, the proper switch is "-2".
If you were trying to force extra-verbose debugging, try "-v -v".
> when I ran it on another computer I had similar output but the "Unable to
> open..." message tried to open a file called 'identities' (or something like
> that, I'm not at that other machine right now) in the same directory. Also
> the other machine did not print the "No address associated to the name"
> error, instead it says it can't use keys and falls back to prompting me for
> a password.
So it worked, yes?
> 1. What is it looking for in the 'ssh2_config' or 'identities' files?
> 2. How can I use the command line version to connect via keys?
>From the man page for OpenSSH:
SSH protocol version 2
When a user connects using the protocol version 2 different authentica-
tion methods are available: At first, the client attempts to authenticate
using the public key method. If this method fails password authentica-
tion is tried.
The public key method is similar to RSA authentication described in the
previous section except that the DSA or RSA algorithm is used instead.
The client uses his private key $HOME/.ssh/id_dsa to sign the session
identifier and sends the result to the server. The server checks whether
the matching public key is listed in $HOME/.ssh/authorized_keys2 and
grants access if both the key is found and the signature is correct. The
session identifier is derived from a shared Diffie-Hellman value and is
only known to the client and the server.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
