Problem connecting to Core FTP server from solaris client

Jet · Post by **Jet** » Sat Jan 06, 2007 1:28 am

Hello there,

I have a client trying to access the Core FTP server that I installed on a windows platform. My client is a unix user. Here is a debug log of what's happening when he tried to connect through SSH using port 22.

datamvr@datamvrpub1-dc-aus ~ : ssh -v activant@64.60.130.103
SSH Version Sun_SSH_1.0, protocol versions 1.5/2.0.
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Rhosts Authentication disabled, originating port will not be trusted.
debug1: ssh_connect: getuid 202 geteuid 202 anon 1
debug1: Connecting to 64.60.130.103 [64.60.130.103] port 22.
debug1: Connection established.
debug1: identity file /export/home/datamvr/.ssh/identity type 3
debug1: Bad RSA1 key file /export/home/datamvr/.ssh/id_rsa.
debug1: identity file /export/home/datamvr/.ssh/id_rsa type 3
debug1: Bad RSA1 key file /export/home/datamvr/.ssh/id_dsa.
debug1: identity file /export/home/datamvr/.ssh/id_dsa type 3
debug1: Remote protocol version 2.0, remote software version CoreFTP-0.1.1
debug1: no match: CoreFTP-0.1.1
Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-Sun_SSH_1.0
debug1: sent kexinit: diffie-hellman-group1-sha1
debug1: sent kexinit: ssh-rsa,ssh-dss
debug1: sent kexinit: aes128-cbc,blowfish-cbc,3des-cbc,rijndael128-cbc
debug1: sent kexinit: aes128-cbc,blowfish-cbc,3des-cbc,rijndael128-cbc
debug1: sent kexinit: hmac-sha1,hmac-md5
debug1: sent kexinit: hmac-sha1,hmac-md5
debug1: sent kexinit: none
debug1: sent kexinit: none
debug1: sent kexinit:
debug1: sent kexinit:
debug1: send KEXINIT
debug1: done
debug1: wait KEXINIT
debug1: got kexinit: diffie-hellman-group1-sha1,diffie-hellman-group14-sha1
debug1: got kexinit: ssh-rsa
debug1: got kexinit: aes128-cbc,3des-cbc,blowfish-cbc,aes192-cbc,aes256-cbc,rijndael128-cbc,rijndael192-cbc,rijndael256-cbc,rijndael-cbc@lysator.liu.se
debug1: got kexinit: aes128-cbc,3des-cbc,blowfish-cbc,aes192-cbc,aes256-cbc,rijndael128-cbc,rijndael192-cbc,rijndael256-cbc,rijndael-cbc@lysator.liu.se
debug1: got kexinit: hmac-sha1,hmac-md5,none
debug1: got kexinit: hmac-sha1,hmac-md5,none
debug1: got kexinit: none,none
debug1: got kexinit: none,none
debug1: got kexinit:
debug1: got kexinit:
debug1: first kex follow: 0
debug1: reserved: 0
debug1: done
debug1: kex: server->client unable to decide common locale
debug1: kex: server->client aes128-cbc hmac-sha1 none
debug1: kex: client->server unable to decide common locale
debug1: kex: client->server aes128-cbc hmac-sha1 none
debug1: Sending SSH2_MSG_KEXDH_INIT.
debug1: bits set: 505/1024
debug1: Wait SSH2_MSG_KEXDH_REPLY.
debug1: Got SSH2_MSG_KEXDH_REPLY.
debug1: Host '64.60.130.103' is known and matches the RSA host key.
debug1: Found key in /export/home/datamvr/.ssh/known_hosts:48
debug1: bits set: 529/1024
debug1: ssh_rsa_verify: signature correct
debug1: Wait SSH2_MSG_NEWKEYS.

On the first part, there is an error on key identification. Thus I decided to follow with what MartinDCC from the post 'Problem connecting from Unix client to Core Server' did. Deleting and generating new keys. On the bottom logs it didn't give any more bad key error message.

However, my client claimed that he after the msg 'Wait SSH2_MSG_NEWKEYS.', it just stuck there and didn't give him any user/password prompt or any means of proceeding to the next step.

Previously, I tried to connect to the server from windows core ftp client, it worked fine. My client guaranteed that he had opened port 22 on the router.

Help would really be appreciated. Thank you very much!

Jet · Post by **Jet** » Mon Jan 08, 2007 10:19 pm

CP,

Thank you for the reply. I have added the public key to the Core FTP Server user's -> security -> pub cert and still didn't work. If you can find more information on configuration adjustment on the sun client, that would be great. Thanks again!

Jet · Post by **Jet** » Mon Jan 15, 2007 5:22 pm

CP, Thanks for the update.

I will get my client to upgrade their Solaris and I will let you know whether that will work or not.

Thanks again.

Jet · Post by **Jet** » Wed Jan 24, 2007 10:05 pm

Ok, we passed the sending of the SSH2_MSG_NEWKEYS authenticating process. However in the next authenticating, we had a new problem. This was taken from the debug log:

debug1: Found key in /export/home/callen/.ssh/known_hosts:1
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering public key: /export/home/callen/.ssh/id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 277
debug1: read PEM private key done: type RSA Received disconnect from xx.xx.xxx.xxx: 2: key check failed Connection closed

We set it in a way that only key exchange will be used, no password is needed.

Any help would really be appreciated. Thanks!