Issue activity log

2009-03-04 21:53 Created Ignore empty SSH keyboard interactive prompts
Component Core
Severity Enhancement
Comment https://winscp.net/forum/viewtopic.php?t=6620
PuTTY Commit 713df723
Status RESOLVED
Resolution FIXED
Implemented in 4.2.2
Comment Upgraded to PuTTY revision 8492, which included a workaround.
2009-03-04 21:55 Version 4.2 beta
2009-04-08 08:24 Comment https://winscp.net/forum/viewtopic.php?t=6758
2009-05-29 09:52 Comment Possibly related:
https://winscp.net/forum/viewtopic.php?t=6897
2009-07-01 09:22 Status RESOLVED → REOPENED
Priority High
Resolution FIXED
Comment Reopening.
The workaround in PuTTY just solved stray authentication announcement. It did not avoid the prompt itself.

Anyway: WinSCP behaves correctly, it display the empty authentication prompt, just as requested by the SSH server. Obviously it is bug in the server. Until 4.1.9 WinSCP was resistant to the bug and just ignored the empty prompts. Until the resistance is introduced back to WinSCP (in 4.1.3), either have you server fixed or downgrade to 4.1.9.
Implemented in 4.2.2
2009-07-02 19:46 Comment Emails with Alexey in July 2009.
2009-07-02 20:06 Comment Workaround implemented. Confirmed by Alexey.
Resolution FIXED
Status REOPENED → RESOLVED
Implemented in 4.2.3
2009-07-06 23:26 Comment https://winscp.net/forum/viewtopic.php?t=7067
2009-07-17 08:58 Comment https://winscp.net/forum/viewtopic.php?t=7106
2022-10-03 10:51 Comment Reopening.·  The workaround in PuTTY just solved stray authentication announcement. It did not avoid the prompt itself.·  ·  Anyway: WinSCP behaves correctly, it display the empty authentication prompt, just as requested by the SSH server. Obviously it is bug in the server. Until WinSCP 4.1.9 WinSCP, it was resistant to the bug and just ignored the empty prompts. Until the resistance is introduced back to WinSCP (in 4.1.3), either have you server fixed or downgrade to 4.1.9.
2022-10-03 10:52 Comment Reopening.   The workaround in PuTTY just solved stray authentication announcement. It did not avoid the prompt itself.     Anyway: WinSCP behaves correctly, it display the empty authentication prompt, just as requested by the SSH server. Obviously it is bug in the server. Until WinSCP 4.1.9, it was resistant to the bug and just ignored the empty prompts. Until the resistance is introduced back to WinSCP (in WinSCP 4.1.3), either have you server fixed or downgrade to 4.1.9.