No computer can be truly called useful if it cannot transfer files. But this process is not easy and requires a lot of risks and technical prowess. That is why file transfer clients are the salvation of modern computing. And the most prominent of those clients is the veteran, WinSCP.
WinSCP is a free open-source client for Microsoft Windows operating with SCP, SFTP and FTP protocols. It was made for secure file transfers between a local computer and remote devices, but can also serve as a tool for file synchronization and a file manager.
WinSCP is based on SSH implemented from PuTTY and FTP implemented from FileZilla. The client has been originally released in 2000 and is being updated since then on a regular basis.
WinSCP has the ability to be used as a plug-in in an another file manager and flexible integration options for Windows OS. It provides a text editor of its own, a file uploading option, and an ability to store session info and many other options.
WinSCP can be used as a remote editor. Clicking on a file in the remote file manager transfers it to the local machine and opens it in the integrated editor. Also, depending on the file extension local editors may be selected. Remote version is updated automatically when the file is saved.
All in all, WinSCP is something of an essential piece of software to have, so there isn't much to say besides 'have it'.
v5.17 [Sep 24, 2012]
-SSL core upgraded to OpenSSL 1.0.1e.
-Not requiring the .NET assembly to exist in file.
-Not considering 3xx error code an error for post-login FTP commands.
-Bug fix: Failure after system-wide change.
-Bug fix: Issuer and Subject were swapped on Certificate verification prompt.
-Bug fix: Traversed subfolders are incorrectly included in find results.
-Bug fix: Wrong color indicator on session tab when session was not switched by clicking on the tab.
-Bug fix: Failure when auto remote directory refresh was triggered during operation initiated by drag&drop.
-Bug fix: Wrong timezone offset was applied with FTP protocol.
-Bug fix: It was not possible to preserve timezone offset of 24 hours and greater in stored session.
-Bug fix: Wrong timestamp conversion with FTP protocol.
-Bug fix: Error in .NET assembly when temporary path contains exclamation mark.
-Bug fix: Indefinite chain of errors when XML logging fails.
