5.2 beta calls putty incorrectly
Hello,
I'm running a dedicated firewall system (ipfire) that uses non-default port 222 for it's own SSH in order to connect to external SSH servers by default port 22.
Now with WinSCP 5.2 beta the normal session works fine, only if I try "Open in PuTTY" command, the connection will be refused. PuTTY event log shows, that the port propagated is 22 rather then real session port 222 (found in PuTTY event log).
With WinSCP 5.1.4 there is no problem.
Would be nice, if this will be fixed in final 5.2
Best regards,
Johannes
I'm running a dedicated firewall system (ipfire) that uses non-default port 222 for it's own SSH in order to connect to external SSH servers by default port 22.
Now with WinSCP 5.2 beta the normal session works fine, only if I try "Open in PuTTY" command, the connection will be refused. PuTTY event log shows, that the port propagated is 22 rather then real session port 222 (found in PuTTY event log).
With WinSCP 5.1.4 there is no problem.
Would be nice, if this will be fixed in final 5.2
Best regards,
Johannes