How do I fix a "Key Check Failed" issue

Report bugs or issues with Core FTP Server here
Post Reply
jkurrle
Posts: 4
Joined: Wed Nov 01, 2006 6:05 pm

How do I fix a "Key Check Failed" issue

Post by jkurrle »

I have CoreFTP server on a box that has been working ok up to today. All of a sudden, when I try to connect from my Linux box to my CoreFTP windows box, I get the following message:

Received disconnect from XXX.XX.XX.XXX: 2: key check failed
Couldn't read packet: Connection reset by peer

This has been fine until today. I have tried stopping and restarting the service, but it doesn't make any difference.

My version of CoreFTP is build 178.

Any help would be appreciated.
Top
jkurrle
Posts: 4
Joined: Wed Nov 01, 2006 6:05 pm

Never mind. Fixed it myself.

Post by jkurrle »

Took care of the problem myself. Never mind.
Top
jonasja
Posts: 1
Joined: Thu Apr 03, 2008 8:37 am

Have the same problem

Post by jonasja »

Could you or anybody share the solution, as I have the same problem.
Top
mahlambane
Posts: 2
Joined: Thu Aug 20, 2009 3:57 pm

How did you Sort it out?

Post by mahlambane »

"I have CoreFTP server on a box that has been working ok up to today. All of a sudden, when I try to connect from my Linux box to my CoreFTP windows box, I get the following message:

Received disconnect from XXX.XX.XX.XXX: 2: key check failed
Couldn't read packet: Connection reset by peer "

I have more or less the same problem. Find error below

$ sftp -vvvv -o "IdentityFile=/chrooted/gmsainfd/home/gmsainfd/.ssh/gmsainfd_ide107_id_rsa" gmsa@124.229.247.238
Connecting to 124.229.247.238...
OpenSSH_4.7p1+sftpfilecontrol-v1.2-hpn12v17, OpenSSL 0.9.7m 23 Feb 2007
HP-UX Secure Shell-A.04.70.009, HP-UX Secure Shell version
debug1: Reading configuration data /opt/ssh/etc/ssh_config
debug3: RNG is ready, skipping seeding
debug2: ssh_connect: needpriv 0
debug1: Connecting to 124.229.247.238 [124.229.247.238] port 22.
debug1: Connection established.
debug3: Not a RSA1 key file /chrooted/gmsainfd/home/gmsainfd/.ssh/gmsainfd_ide107_id_rsa.
debug2: key_type_from_name: unknown key type '-----BEGIN'
debug3: key_read: missing keytype
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug2: key_type_from_name: unknown key type '-----END'
debug3: key_read: missing keytype
debug1: identity file /chrooted/gmsainfd/home/gmsainfd/.ssh/gmsainfd_ide107_id_rsa type 1
debug1: Remote protocol version 2.0, remote software version CoreFTP-0.1.2
debug1: no match: CoreFTP-0.1.2
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.7p1+sftpfilecontrol-v1.2-hpn12v17
debug2: fd 4 setting O_NONBLOCK
debug3: RNG is ready, skipping seeding
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: kex_parse_kexinit: diffie-hellman-group1-sha1,diffie-hellman-group14-sha1
debug2: kex_parse_kexinit: ssh-rsa
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,aes192-cbc,aes256-cbc,rijndael128-cbc,rijndael192-cbc,rijndael256-cbc,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,aes192-cbc,aes256-cbc,rijndael128-cbc,rijndael192-cbc,rijndael256-cbc,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: hmac-sha1,hmac-md5,none
debug2: kex_parse_kexinit: hmac-sha1,hmac-md5,none
debug2: kex_parse_kexinit: none,none
debug2: kex_parse_kexinit: none,none
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: mac_setup: found hmac-md5
debug1: kex: server->client aes128-cbc hmac-md5 none
debug2: mac_setup: found hmac-md5
debug1: kex: client->server aes128-cbc hmac-md5 none
debug2: dh_gen_key: priv key bits set: 127/256
debug2: bits set: 1040/2048
debug1: sending SSH2_MSG_KEXDH_INIT
debug1: expecting SSH2_MSG_KEXDH_REPLY
debug3: check_host_in_hostfile: filename /chrooted/gmsainfd/home/gmsainfd/.ssh/known_hosts
debug3: check_host_in_hostfile: match line 8
debug1: Host '124.229.247.238' is known and matches the RSA host key.
debug1: Found key in /chrooted/gmsainfd/home/gmsainfd/.ssh/known_hosts:8
debug2: bits set: 1062/2048
debug1: ssh_rsa_verify: signature correct
debug2: kex_derive_keys
debug2: set_newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug2: set_newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug2: key: /chrooted/gmsainfd/home/gmsainfd/.ssh/gmsainfd_ide107_id_rsa (40031fa0)
debug1: Authentications that can continue: publickey
debug3: start over, passed a different list publickey
debug3: preferred publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Offering public key: /chrooted/gmsainfd/home/gmsainfd/.ssh/gmsainfd_ide107_id_rsa
debug3: send_pubkey_test
debug2: we sent a publickey packet, wait for reply
debug1: Server accepts key: pkalg ssh-rsa blen 277
debug2: input_userauth_pk_ok: fp 36:f5:70:48:64:90:dc:d2:6b:7f:e4:ef:3f:c2:ae:2c
debug3: sign_and_send_pubkey
debug1: read PEM private key done: type RSA
[b]Received disconnect from [b]xx.xx.xx.xx[/b]: 2: key check failed
Connection closed[/b]
[u][/u]
Top
Post Reply

Return to “Server - Issues”