SHA Encryption - unable to connect

rleatherwood · Post by **rleatherwood** » Mon Sep 19, 2016 5:13 pm

We use CoreFtp v.1853 to connect to a customer sftp server. Everything was working fine until they updated their server software (secure transport) that required them to enable their SHA settings. In doing so, we lost our connection ability and received the error:

Failed to read binary packet data!
SFTP connection error

I did find a previous thread on here that said to click through the cipher order under the SSH advanced site settings, but I tried various ones and it didn't work.

When the customer disables their SHA settings, we can connect just fine. Due to their security policies, they prefer the SHA setting be enabled.

Any ideas or suggestions?

cp · Post by cp » Wed Sep 21, 2016 4:58 am

The 1881 may help fix this issue. Install over your existing version (or test on another machine first)

rleatherwood · Post by **rleatherwood** » Thu Sep 22, 2016 3:28 pm

1881 didn't like their ftp server at all. Regardless of the SHA1 setting, it would just come back as:

FTP connection error - Connection timed out
Can't establish connection - [ftp address] @ [date]

At least with 1853, I could connect when SHA1 was disabled. And when SHA1 was enable, it just failed to read the binary packet data.

cp · Post by cp » Thu Sep 22, 2016 4:12 pm

> FTP connection error - Connection timed out

This is a different error. Either the server is down or something external to Core FTP is blocking the connection. Check with the server administrator to see if the server is down.

rleatherwood · Post by **rleatherwood** » Thu Sep 22, 2016 6:16 pm

The server is fine, because when I switched back to 1853 it connects. When I use 1881, I get the time out error. I switched to a different ftp client, and can connect just fine as well. Just weird that 1881 doesn't like their server, and 1853 doesn't like SHA1 encryption.

cp · Post by cp » Fri Sep 23, 2016 12:20 am

could you send the hostname (or IP address) to feedback at coreftp.com

I'll test it and see what I can determine...

cp · Post by cp » Fri Sep 23, 2016 3:39 pm

Are you sure it was the 1881 build? Was it the 32-bit version or the 64-bit?

x.x.x.x [22] connecting...
SSH-2.0-SSHD
diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha256
diffie-hellman-group-exchange-sha256
client -> aes128
server -> aes128
c0:c3

df:20:63:70:f7:e1:99:b0:33:3d:f9:98:60
ssh-rsa
Sending password
SFTP connection error - Invalid username or password reported by server
Can't establish connection --> 206.224.96.35:22 @ Fri Sep 23 08:21:09 2016 (10038-30015)

cp · Post by cp » Fri Sep 23, 2016 5:27 pm

It may be that the message being displayed by the server is causing the problem. Build 1883 will be available shortly and should fix it.