Trying SSH on Trinux I've run into some problems and I'm wondering if anyone
has seen this.
I've installed opensshd.tgz from Matthew's site, and a Windows port of the
openssh client from NetworkSimplicity.com.
I installed the client, generated the keys, and followed Matthew's
directions on the Trinux site for setting up ssh. When I try to connect, my
client outputs the following:
C:\>ssh -v -i c:\ssh\.ssh\identity 192.168.12.149
SSH Version OpenSSH_2.3.0p1, protocol versions 1.5/2.0.
Compiled with SSL (0x0090581f).
debug: Seeding random number generator
debug: ssh_connect: getuid 500 geteuid 500 anon 0
debug: Connecting to 192.168.12.149 [192.168.12.149] port 22.
debug: Seeding random number generator
debug: Allocated local port 864.
debug: Connection established.
debug: Remote protocol version 1.99, remote software version OpenSSH_2.1.1
debug: match: OpenSSH_2.1.1 pat ^OpenSSH[-_]2\.[012]
debug: Local version string SSH-1.5-OpenSSH_2.3.0p1
debug: Waiting for server public key.
debug: Received server public key (768 bits) and host key (1024 bits).
The authenticity of host '192.168.12.149' can't be established.
RSA key fingerprint is 11:ef:3a:60:96:c7:20:7c:86:9d:d1:9c:44:23:28:91.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.12.149' (RSA) to the list of known
hosts.
debug: Seeding random number generator
debug: Encryption type: 3des
debug: Sent encrypted session key.
debug: Installing crc compensation attack detector.
debug: Received encrypted confirmation.
debug: Trying RSA authentication with key 'e60824@NDEV94F'
debug: Server refused our key.
debug: Doing password authentication.
e60824@192.168.12.149's password:
Permission denied.
debug: Calling cleanup 0x414cf0(0x0)
On the server in /var/log/messages I see:
Feb 23 09:42:12 (none) auth.info sshd[3967]: Faking authloop for illegal
user e60824 from 192.168.15.126 port 626
Feb 23 09:42:15 (none) auth.info sshd[3967]: Connection closed by
192.168.15.126
The only difference I can see is the protocol versions built into the client
(v1.5) and server (v1.99), but I don't know that this is the problem.
Any ideas?
Sam
|