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
SFTP: When used under Parallels for Mac, the SSH Client was unable to list folders shared by the Mac (for example, \MacHomeDesktop). This arose because the SSH Client used an advanced Windows filesystem API which the Mac does not implement. The SSH Client now uses a simpler version of this API, allowing the listing of Mac folders.
sftpc: The get command now supports a -wait switch. This causes the get command to wait for the server's confirmation that the file has been closed before continuing any further actions. When used with conjunction with -del, this causes sftpc to wait for the server's confirmation that the file has been closed before attempting to delete the file.
sftpc now supports a new wait command. This causes sftpc to wait until it receives from the server any pending confirmations for file and directory close requests, before proceeding with any other actions. If there are no outstanding close requests pending confirmations, the wait command does nothing.
stermc: When using the stermc terminal shell command-line client, if the remote shell exited with a non-zero exit code, the SSH Client's totermc or bvtermc terminal client process would continue to run after stermc exits. These processes would potentially interfere with console input. Fixed.
Command-line clients: When input or output is redirected, then by default, the SSH Client's command-line clients (including sftpc, sexec, stnlc, stermc and spksc) will now use the input/output code page associated with the console in which they run (Windows functions GetConsoleCP and GetConsoleOutputCP), instead of the system-wide ANSI code page (Windows function GetACP). This causes output from Bitvise command-line clients to respect the code page set using chcp. For example, when chcp has been used, sftpc >> file.txt will now use the same code page as echo xxxx >> file.txt.
Improved BOM handling when output is redirected with code pages UTF-8, UTF-16, and UTF-16BE. The BOM will now be consistently emitted when redirecting into an empty file, but not when redirecting into a non-empty file or a stream.