Forum » Support and Bug Reports »

Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

martin

Re: Initiating key re-exchange (too much data received)

The key re-exchange is transparent to the transfer. I.e. it has no impact on it.
Guest

Initiating key re-exchange (too much data received)

I'm trying to transfer a rather large file through sftp. I'm getting these lines in the log:
> 2018-03-05 11:10:21.493 Type: SSH_FXP_OPEN, Size: 71, Number: 4172291
< 2018-03-05 11:10:21.494 Type: SSH_FXP_STATUS, Size: 24, Number: 4172036
. 2018-03-05 11:10:21.494 Discarding reserved response
< 2018-03-05 11:10:21.509 Type: SSH_FXP_HANDLE, Size: 13, Number: 4172291
> 2018-03-05 11:10:21.509 Type: SSH_FXP_FSTAT, Size: 13, Number: 4172552
< 2018-03-05 11:10:21.623 Type: SSH_FXP_ATTRS, Size: 37, Number: 4172552
> 2018-03-05 11:10:21.623 Type: SSH_FXP_READ, Size: 25, Number: 4172805
. 2018-03-05 11:28:56.828 Initiating key re-exchange (too much data received)
. 2018-03-05 11:28:56.953 Doing ECDH key exchange with curve Curve25519 and hash SHA-256
. 2018-03-05 11:28:57.293 Initialised AES-256 SDCTR client->server encryption
. 2018-03-05 11:28:57.293 Initialised HMAC-SHA-256 client->server MAC algorithm
. 2018-03-05 11:28:57.293 Initialised AES-256 SDCTR server->client encryption
. 2018-03-05 11:28:57.293 Initialised HMAC-SHA-256 server->client MAC algorithm

My question is, when it initiates a key re-exchange, does that mean it is starting the transfer over? Or will it eventually finish?

Documentation

Support

Associations

Follow Us