7 views

Description

SNCSSH computes the largest possible packet resulting from encoding the maximum possible payload size (32768) with the negotiated algorithms, but rfc4253 requires implementations handle an arbitrary limit of 35000 bytes.

Some versions of ssh exceed the maximum limits as calculated by sncssh resulting in an error message like "2017-09-20 11:22:10 (097) SSHProtocolEngine SYSTEM SEVERE *** ERROR *** [1/10.11.12.13:22] Session failure, closing connection: Corrupt packet received, claims impossible length of 32836 bytes:"


Steps to Reproduce

 

Trying to connect to an sftp server produces the error message:

com.glide.db.impex.datasource.DataSourceException: java.io.IOException: Cannot create task: ReadFileTask, SFTPJob is terminated

 

Workaround

If not possible to upgrade to one of the latest patches in the Fixed In section, the workaround is to modify the SFTP server configuration to not send packets larger than 30536 bytes. This value leaves the correct margin to avoid the error.

Example below:




Related Problem: PRB1192173

Seen In

Eureka

Intended Fix Version

London

Fixed In

Jakarta Patch 9
Kingston Patch 3

Safe Harbor Statement

This "Intended Fix Version" information is meant to outline ServiceNow's general product direction and should not be relied upon in making a purchasing decision. The information provided here is for information purposes only and may not be incorporated into any contract. It is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at ServiceNow's sole discretion.

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2018-06-14 13:19:28
Published:2018-06-14