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

IWouldLikeToBeCalledKurt

I've the same issue.
Seems to be related to the server response. Can't verify but I think it happens when the server doesn't allow any new connections.
I get this "handshake" error messages when I'm connected to one server with multiple WinSCP instances and all of them use multiple connections in the background.
The messages vary sometimes
Received invalid elliptic curve point in ECDH reply

Registered server host key is invalid

(if I remember correctly)

Would be great if this error could be catched and forking new background connections could be stopped for this upload or session.
martin

Re: Background connections when happening quickly causes error

Thanks for your report.
I see that you have indeed reported this already – and I've responded, but you never came back to me...

Anyway, can you please try to find out what exact version (including beta versions) did introduce the problem?
You can download all past versions of WinSCP from:
https://sourceforge.net/projects/winscp/files/WinSCP/
elephantspirit

Background connections when happening quickly causes error

When many background connections are started, errors come up. Usually invalid key, this is all using SFTP.

Can be reproduced by

  1. Have background transfer set above 4, the higher the more likely to trigger the bug. I used 9
  2. Making a folder with 10~ files
  3. Edit them all in a text editor
  4. Save all in editor causing WinSCP to upload them all
  5. Error pop up, clicking OK on all error pop ups gets all uploaded eventually.

I previously made a bug report about this. It's been a bug since after 5.17. 
. 2023-12-15 14:29:45.277 [Background 1] Remote version: SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.4
. 2023-12-15 14:29:45.277 [Background 1] Using SSH protocol version 2
. 2023-12-15 14:29:45.278 [Background 1] Have a known host key of type ssh-ed25519
. 2023-12-15 14:29:45.286 [Background 2] Remote version: SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.4
. 2023-12-15 14:29:45.286 [Background 2] Using SSH protocol version 2
. 2023-12-15 14:29:45.287 [Background 3] Remote version: SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.4
. 2023-12-15 14:29:45.287 [Background 3] Using SSH protocol version 2
. 2023-12-15 14:29:45.287 [Background 2] Have a known host key of type ssh-ed25519
. 2023-12-15 14:29:45.288 [Background 3] Have a known host key of type ssh-ed25519
. 2023-12-15 14:29:45.293 [Background 4] Remote version: SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.4
. 2023-12-15 14:29:45.293 [Background 4] Using SSH protocol version 2
. 2023-12-15 14:29:45.293 [Background 4] Have a known host key of type ssh-ed25519
. 2023-12-15 14:29:45.302 [Background 1] Doing NTRU Prime / Curve25519 hybrid key exchange, using hash SHA-512 (unaccelerated)
. 2023-12-15 14:29:45.313 [Background 2] Doing NTRU Prime / Curve25519 hybrid key exchange, using hash SHA-512 (unaccelerated)
. 2023-12-15 14:29:45.321 [Background 3] Doing NTRU Prime / Curve25519 hybrid key exchange, using hash SHA-512 (unaccelerated)
. 2023-12-15 14:29:45.322 [Background 4] Doing NTRU Prime / Curve25519 hybrid key exchange, using hash SHA-512 (unaccelerated)
. 2023-12-15 14:29:45.465 [Background 1] Received invalid elliptic curve point in ECDH reply
. 2023-12-15 14:29:45.465 [Background 1] Attempt to close connection due to fatal exception:
* 2023-12-15 14:29:45.465 [Background 1] Received invalid elliptic curve point in ECDH reply
. 2023-12-15 14:29:45.465 [Background 1] Closing connection.
. 2023-12-15 14:29:45.465 [Background 1] Asking user:
. 2023-12-15 14:29:45.465 [Background 1] Received invalid elliptic curve point in ECDH reply ()
. 2023-12-15 14:29:45.519 [Background 3] Signature from server's host key is invalid
. 2023-12-15 14:29:45.519 [Background 3] Attempt to close connection due to fatal exception:
* 2023-12-15 14:29:45.519 [Background 3] Signature from server's host key is invalid
. 2023-12-15 14:29:45.519 [Background 3] Closing connection.
. 2023-12-15 14:29:45.519 [Background 3] Asking user:
. 2023-12-15 14:29:45.519 [Background 3] Signature from server's host key is invalid ()
. 2023-12-15 14:29:45.529 [Background 2] Signature from server's host key is invalid
. 2023-12-15 14:29:45.529 [Background 2] Attempt to close connection due to fatal exception:
* 2023-12-15 14:29:45.529 [Background 2] Signature from server's host key is invalid
. 2023-12-15 14:29:45.529 [Background 2] Closing connection.
. 2023-12-15 14:29:45.529 [Background 2] Asking user:
. 2023-12-15 14:29:45.529 [Background 2] Signature from server's host key is invalid ()
. 2023-12-15 14:29:45.560 [Background 4] Signature from server's host key is invalid
. 2023-12-15 14:29:45.560 [Background 4] Attempt to close connection due to fatal exception:
* 2023-12-15 14:29:45.560 [Background 4] Signature from server's host key is invalid
. 2023-12-15 14:29:45.561 [Background 4] Closing connection.
. 2023-12-15 14:29:45.561 [Background 4] Asking user:
. 2023-12-15 14:29:45.561 [Background 4] Signature from server's host key is invalid ()
. 2023-12-15 14:29:48.960 [Background 1] Answer: OK

Documentation

Support

Associations

Follow Us