0
1
I have a process scheduled to send files to an SFTP server (Tumbleweed) using WinSCP.
It works 99.5% of the time.
0.5% of the time, the login fails and WinSCP reports:
Server refused public-key signature despite accepting key
WinSCP Log Excerpt:
! 2013-04-07 12:05:18.913 Using username "XXXXXX".
. 2013-04-07 12:05:18.928 Offered public key
. 2013-04-07 12:05:19.460 Offer of public key accepted
! 2013-04-07 12:05:19.460 Authenticating with public key "XXXXXXXXX"
. 2013-04-07 12:05:19.491 Sent public key signature
! 2013-04-07 12:05:19.491 Server refused public-key signature despite accepting key!
. 2013-04-07 12:05:19.491 Server refused public-key signature despite accepting key!
. 2013-04-07 12:05:19.491 Attempting keyboard-interactive authentication
The server logs no error:
2013-04-07 12:05:19,816 DEBUG [SSHD-TRANSFER-1] com.tumbleweed.st.server.sshd.SSHSession - Adding session xxxxxxx. Session count: 0
2013-04-07 12:05:19,816 DEBUG [SSHD-TRANSFER-1] com.tumbleweed.st.server.events.AgentSession - Created unique session ID: xxxxxx
2013-04-07 12:05:19,816 DEBUG [SSHD-TRANSFER-1] com.tumbleweed.st.server.sshd.PublicKeyStoreImpl - invoke cert agent
2013-04-07 12:05:20,350 DEBUG [SSHD-TRANSFER-1] com.tumbleweed.st.server.sshd.PublicKeyStoreImpl - cert agent success [username=xxxxxx]
2013-04-07 12:05:20,386 DEBUG [SSHD-TRANSFER-1] com.tumbleweed.st.server.sshd.PublicKeyStoreImpl - User "xxxxx" logged in with cached key.
How can I diagnose / resolve this issue?
The fix was included into 1.3.5rc4 release. – Martin Prikryl – 2014-03-14T19:41:37.677