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

Thanks for your report.
I have sent you an email with a debug version of WinSCP to the address you have used to register on this forum.
burghcoder

I updated the code to the new version of WinSCP (5.9.3) and we were still seeing the issue. I am thinking this is an issue with our customers remote server.
burghcoder

It just started happening when we starting testing with a customers remote server. I can send thousands of files to our server without any issues.


I would open to using a debug version. Do you want me to update our code to use version 5.9.3 first? Reading the release notes, it looks like there are some changes to the classes.
martin

Re: Public key not being offered intermittently using winscp .net

I've never seen this problem before.

If you are willing to, I can provide you a debug build of WinSCP, which does extensive logging. It can help with tracing the problem down.
burghcoder

Public key not being offered intermittently using winscp .net

I have a service that uses WinSCP.net to send files to a vendor. We use pulic key authentication to log into the remote server. Things seem to be sending fine, but every once in a while a session connection is able to open because the public key is not being offered.

All the files we send use the same sessionOptions. The only thing that changes is the filename.

I found this using session logging.

Good file:
. 2016-12-07 12:40:51.761 Host key matches configured key

. 2016-12-07 12:40:51.761 Host key fingerprint is:
. 2016-12-07 12:40:51.761 ssh-rsa 1024 xxxxxxxxxxx
. 2016-12-07 12:40:51.761 Initialised AES-256 SDCTR client->server encryption
. 2016-12-07 12:40:51.761 Initialised HMAC-SHA-256 client->server MAC algorithm
. 2016-12-07 12:40:51.761 Initialised AES-256 SDCTR server->client encryption
. 2016-12-07 12:40:51.761 Initialised HMAC-SHA-256 server->client MAC algorithm
. 2016-12-07 12:40:51.902 Reading private key file "xxx.ppk"
! 2016-12-07 12:40:51.902 Using username "xxx-01".
. 2016-12-07 12:40:51.949 Offered public key
. 2016-12-07 12:40:52.012 Offer of public key accepted
! 2016-12-07 12:40:52.012 Authenticating with public key "rsa-key-xxxx"
. 2016-12-07 12:40:52.012 Prompt (passphrase, "SSH key passphrase", <no instructions>, "Passphrase for key "rsa-key-xxx": ")
. 2016-12-07 12:40:52.012 Using configured passphrase.
. 2016-12-07 12:40:52.261 Sent public key signature
. 2016-12-07 12:40:52.324 Access granted


Bad file in the same process:

. 2016-12-07 12:40:56.386 Host key matches configured key

. 2016-12-07 12:40:56.386 Host key fingerprint is:
. 2016-12-07 12:40:56.386 ssh-rsa 1024 xxxxxxx
. 2016-12-07 12:40:56.386 Initialised AES-256 SDCTR client->server encryption
. 2016-12-07 12:40:56.386 Initialised HMAC-SHA-256 client->server MAC algorithm
. 2016-12-07 12:40:56.386 Initialised AES-256 SDCTR server->client encryption
. 2016-12-07 12:40:56.386 Initialised HMAC-SHA-256 server->client MAC algorithm
. 2016-12-07 12:40:56.527 Reading private key file "xxx.ppk"
! 2016-12-07 12:40:56.527 Using username "xxx-01".
. 2016-12-07 12:40:56.589 Prompt (password, "SSH password", <no instructions>, "&Password: ")
. 2016-12-07 12:40:56.589 Disconnected: Unable to authenticate



I am currently using version 5.7.7. Before I submit a request to have the services recompiled against version 5.9.3, is this a bug that was fixed or is this something else that I have missed?