Incoming Packet Garbled message

Hi, we have regular replication scripts between DR and Prod servers, I keep getting the message "Incoming packet was garbled by decryption" for only two folders out of the 8 that I'm copying.

I have my scripts in "D:\Replication Scripts" folder on the production server.

Searching on the internet will suggest that this is SSH issue, but after troubleshooting it, I don't believe so. Not only that it works for the other 6 folders in the same session, it also does not work using other admin logins just like my logon. Another thing I found with the "publish" folder is that, when refreshing over 345 files in the folder, say 346 files or more, the script will then fail with the "garbled" message. The same message will display if trying to view the folder's content using WINSCP GUI. I wonder if there is a limit of number of files per folder or something along that line ...
running WINSCP 4.1.6

Any help would be great.

Thanks

What is your SSH server?

Hi,

the FTP server on DR is GlobalSCAPE Secure FTP Server 3.3.1 Build 04.28.2008.1

Hi,


I have a GlobalScape v3.31 to which I connect with SFTP and I have the same problem when files are >200KB or when the directory listed contains several files from 200 to ... depending on their name length and/or quantity inside the directory.
The issue first occured when WinSCP went from v4.0.7 to v4.1b. I think at that time the PuTTY code went to PuTTY 0.60.
I had the same issue with FileZilla when it went from v2.2.32 to v3.0.0.

When I use the psftp included in the PuTTY 0.60 package, all is fine.

From GlobaScape:
javascript:emoticon(':shock:')"According to latest SSH file transfer draft: https://datatracker.ietf.org/doc/html/draft-ietf-secsh-filexfer-13

Implementations MUST ignore excess data at the end of an otherwise
valid packet. Implementations MUST respond to unrecognized packet
types with an SSH_FX_OP_UNSUPPORTED error. This will allow the
protocol to be extended in a backwards compatible way as needed.

So it appears that the client is not following the spec. It should process the data up the lenght of the packet that it expects to receive.

Another section states:

The maximum size of a packet is in practice determined by the
client (the maximum size of read or write requests that it sends,
plus a few bytes of packet overhead). All servers SHOULD support
packets of at least 34000 bytes (where the packet size refers to
the full length, including the header above). This should allow
for reads and writes of at most 32768 bytes.

Granted the recommended approach is for the server to honor packet size stipulated by the client; however the spec is clear in that the client shouldn't simply error out if the packet exceeds the expected length." :shock:

Perhaps it can help?

hi, thanks for the info,
is there anything specifically that I should be checking, changing within winscp and/or Globalscape in relation ti the above. I saw the details on psftp and it doesn't look like it has a synch option like winscp has (or similar command like remote|local within a batch file).

Hi,

I just pointed out psftp to take a look to the PuTTY code implementation into WinSCP and try to find if there were some changes in PuTTY 0.60 that were not reflected into WinSCP v4.x.
Most of our accounts are accessed from WinSCP.

Rub

Are you able to tell me on how you can "point PSFTP to take a look to the PuTTY code implementation into WinSCP"? I cannot find it anywhere in the psftp command options. Can you please give me a code example of, say how you will go about doing a winscp synchronize using psftp?

Thanks.

mimi wrote:

I just pointed out psftp to take a look to the PuTTY code implementation into WinSCP and try to find if there were some changes in PuTTY 0.60 that were not reflected into WinSCP v4.x.
Most of our accounts are accessed from WinSCP.

I believe that all PuTTY 0.60 code is in WinSCP 4.1.x.

tomlego wrote:

Are you able to tell me on how you can "point PSFTP to take a look to the PuTTY code implementation into WinSCP"? I cannot find it anywhere in the psftp command options. Can you please give me a code example of, say how you will go about doing a winscp synchronize using psftp?

It was suggestion for WinSCP development ;-)

PSFTP cannot synchronize.

OK it seems as the same problem as reported here:
https://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/ssh2-bug-maxpkt.html

WinSCP reports window size as 4 times the max packet size.

So actually it still looks like a server-side bug.

This issue has been added to tracker.

martin wrote:

tomlego wrote:

Are you able to tell me on how you can "point PSFTP to take a look to the PuTTY code implementation into WinSCP"? I cannot find it anywhere in the psftp command options. Can you please give me a code example of, say how you will go about doing a winscp synchronize using psftp?

It was suggestion for WinSCP development ;-)

PSFTP cannot synchronize.

Hi, so just to double check and confirm, there is no way to "configure psftp to use winscp implementation codes to do the synchronize" as per mimi's suggestion?

Hi, so just to double check and confirm, there is no way to "configure psftp to use winscp implementation codes to do the synchronize" as per mimi's suggestion?

Correct.

So is there any workaround for this issue that you can recommend? Is there other WinSCP version I should try?

Thanks.

tlegowo wrote:

So is there any workaround for this issue that you can recommend? Is there other WinSCP version I should try?

If you provide me your email address I can send you a development version for testing.

I get the garbled message when installing the server key at first connection to the server.

freeSSHd 1.2.1 server on win 2003, winscp 4.17 on client.

mrose6 wrote:

I keep getting the message "Incoming packet was garbled by decryption"

I get the message on my Vista machine with WinSCP 4.1.7 (build 413)
But on XP, 3.8.2 (330) WinSCP downloads the same files without problems.

kr

Anton

I get the message on my Vista machine with WinSCP 4.1.7 (build 413)
But on XP, 3.8.2 (330) WinSCP downloads the same files without problems.

What is your server?

rdevries wrote:

I get the garbled message when installing the server key at first connection to the server.

The same! Solaris server, winscp 4.17, Vista on my machine.
The older version 4.0.0 on XP works fine with the same server.