This could effectively rule out the use of separate SSH tunneling for FTP. Though SFTP uses SSH as its underlying protocol, many SFTP providers restrict SSH to only SFTP usage due to security reasons. There is even a guide for converting old ftp.exe batch commands for WinSCP and SFTP.Īlso, even if the vendor's server supports SFTP it doesn't necessarily mean that it also supports all SSH features. If using SSH keys is not an option, another popular client is WinSCP, which also supports password authentication. If you don't mind using SSH keys for authentication, I'd just use the built-in OpenSSH SFTP client: sftp.exe -b sftp-commands.txt There are several 3rd party SFTP clients available and recent Windows versions even have OpenSSH client as an optional feature. The existing text files for FTP commands may require some updating though, as not all FTP commands are the same for SFTP. This way the secure filetransfer can be done with a single command. This is the more robust version of Tiny SFTP from Rebex Labs, offering more features when you need more than just a testing platform. Cost: Free 30-day version with limited functionality Full license for 299. I'd recommend using an SFTP client instead. Operating systems: Windows XP/2003/Vista/Server /10. This would however make the system rather complicated. To do this, you should first establish a tunneled network connection to the server with the ssh.exe and then use the existing commands for ftp.exe to do your file transfers. In theory, an FTP connection to a host could be tunneled via a separate SSH tunnel. SFTP isn't quite the same as just tunneling FTP inside SSH, its actually an extension to the SSH protocol.
0 kommentar(er)
