Bitvise SSH Client is highly customizable tool to be used in specific situations and controlled environments. The portable Bitvise SSH Client version was developed to run Bitvise SSH Client distribution from a USB key, in the U3 and PortableApps formats.
Additionally, remote server configuration is supported: using Bitvise SSH Client, all WinSSHD settings can be configured remotely. The server's event log can also be remotely viewed and managed.
Features of Bitvise SSH Client:
- Support for RSA and DSA public key authentication with comprehensive user keypair management.
- Powerful SSH port forwarding capabilities.
- Dynamic forwarding through integrated SOCKS and HTTP CONNECT proxy.
- Automatic resuming, text file awareness, recursive subdirectory transfers.
- High speed - up to 5 MB/s when connected to a WinSSHD server, network bandwidth and disk resources permitting.
- Fast responsiveness to user input even when in the middle of multiple file transfers.
- Advanced, scriptable command-line SFTP client.
- All terminal emulation is done in a regular Windows console.
- UTF support with VT-100 and xterm, Unicode support with bvterm (full Unicode support on NT-series Windows platforms).
- Sftpc - an advanced command-line SFTP client.
Changes in recent version
The Notes tab is now scrollable and may contain much more text.
SSH Client version 8.46 introduced an issue where text file uploads would not work when using the file transfer modes Auto Std or Text, which are available in SFTP protocol versions 4 and 6. Fixed.
When downloading a file using the Auto Std file transfer mode, which is available in SFTP protocol versions 4 and 6, the SSH Client first opens the file in binary mode. If the client detects that the file is textual, it closes and reopens the file using the flag SSH_FXF_TEXT_MODE.
Some servers do not handle this scenario gracefully and do not allow the file to be reopened. With these servers, the Auto Std mode cannot work. In this case, the SSH Client will now display a more useful error to suggest changing the file transfer mode.
The SFTP v4 draft specification from 2002 contains a typo in the definition of SSH_FILEXFER_ATTR_PERMISSIONS. This flag is defined with incorrect value 0x40 instead of the correct value, 0x04. This conflicts with previous and subsequent SFTP versions, as well as SSH_FILEXFER_ATTR_ACL defined in the same draft. Implementations should use the correct value, 0x04.
There exist implementations of SFTP v4 that do not identify this error, and do not use the correct value. To aid compatibility with such servers, the SSH Client will no longer request SSH_FILEXFER_ATTR_PERMISSIONS as part of SSH_FXP_LSTAT if the Permissions column is not enabled on the Remote pane of the Browse tab.