Bitvise SSH Client Version History
Changes in Bitvise SSH Client 6.05: [ 15 August 2014 ]
- SFTP: When downloading, characters in the file name that are invalid on Windows will now be replaced with an underscore. Files whose name contains a colon (':') will no longer be downloaded to an alternate NTFS stream.
- Remote Desktop: When using a custom Remote Desktop profile, prompting for credentials will now be properly disabled if "Use SSH login credentials" is checked.
- Added support for UTF-8 and UTF-16 byte order markers when importing keys from textual files.
- Fixed log message describing when reconnection attempt is scheduled.
- Fixed issues with proxy support for outgoing connections when "Resolve DNS names locally" was enabled.
- The SOCKS/HTTP proxy forwarding subsystem (dynamic tunneling) did not correctly handle IPv6 HTTP CONNECT request. Fixed.
- Several warning messages related to port forwarding are now informational messages, to avoid unnecessary pop-ups from being displayed.
- Graphical SFTP: Fixed an issue which prevented the "Target file already exists" dialog from opening when resuming is not available.
Changes in Bitvise SSH Client 6.04: [ 13 July 2014 ]
- When creating remote directories and files, Bitvise SSH Client will no longer send a default set of POSIX permissions, instead letting the server choose appropriate POSIX permissions for the new directories and files.
- In sftpc, batch list and download operations, such as "get *.txt", would always return an unsuccessful exit code. Fixed.
Changes in Bitvise SSH Client 6.03: [ 5 July 2014 ]
- In sftpc, the exit code would not be set properly after failed transfers. Fixed.
- When the SSH Client is run for the first time after installation, it would be run under the installer's elevated security context. This could cause subtle discrepancies in behavior compared to when the client is run without elevation later. Fixed.
- Since the new terminal client implementation introduced with version 4.60, the bvterm client would close with an exception if the server sent a particular rarely sent packet (BVT2_WRITEOUTPUTCHAR). Fixed.
Changes in Bitvise SSH Client 6.02: [ 1 July 2014 ]
- The graphical SFTP remote files pane was incorrectly using start directory and other settings from the local pane.
Changes in Bitvise SSH Client 6.01: [ 26 June 2014 ]
- New features in the sftpc command line client:
- The put and get commands now support a "-del" flag to delete files after they have been transferred successfully.
- When using put or get with the "-s" flag (recursive transfer), matching empty directories will now also be transferred.
- Importing of OpenSSH private keys encrypted using "aes192-cbc" and "aes256-cbc" algorithms is now also supported.
- When converting file times from UTC for display in local time, the SSH Client would not correctly account for DST when there was a mismatch between the file's DST offset and current DST. Fixed.
- An SFTP pane resizing issue is now believed fixed.
- Fixed a number of 6.00 beta issues:
- If exiting of the graphical client was canceled through the "profile changed" dialog, the Login button would no longer work.
- When viewing help for command line clients piped through a pager such as "more" or "less", the command line clients would terminate with an error if the pager was exited prematurely.
- Tooltips would not show when hovering the mouse pointer over an SSH Client icon in the system notification area.
- sftpc would show file modification times in UTC instead of local time when listing files.
- In the graphical SFTP window, under Browse, selecting the local or remote path from the dropdown list failed to work properly.
- On older Windows versions, including Windows XP, the Remote Desktop window title would not update properly when opening a single-click Remote Desktop window in full screen mode.
- On older Windows versions that did not include IPv6 support, including Windows XP, the newly added IPv6 support would fail, interfering with some aspects of the client.
Changes in Bitvise SSH Client 6.00 beta: [ 28 May 2014 ]
- Bitvise SSH Client now uses FlowSsh and the technological platform of Bitvise SSH Server versions 5.xx and 6.xx. This includes, but is not limited to:
- The cryptographic algorithms used by the SSH Client are now implemented in a FIPS 140-2 certified cryptographic module.
- The SSH Client now supports Elliptic Curve algorithms - key exchange using ECDH, and ECDSA public keys for client and server authentication.
- The SSH Client now implements defensive measures against attacks based on the CBC encryption mode.
- IPv6 is now supported.
- Command line clients:
- A new command line client, stnlc, supports scriptable and command line access to port forwarding functionality and the FTP-to-SFTP bridge.
- A new command line client, spksc, supports scriptable and command line access to the SSH public key subsystem. With Bitvise SSH Server, and other servers that support SPKS, the client can manage public keys which the server will accept for the client's authentication.
- The sftpc and stermc command line clients now also support an implied trailing command without the "-cmd=..." parameter, for example: "sftpc user@host get *.txt", or "stermc user@host dir".
- The sexec command line client now supports X11 forwarding.
- FTP-to-SFTP bridge:
- Wildcards (* and ?) can now be used in directory listings.
- As a compatibility improvement, the FTP-to-SFTP bridge now attempts to detect and ignore parameters passed to the LIST command.
- An optional FTP password can now be configured, which an FTP client then must provide in order to access the bridge.
- A port range for PASV mode transfers can now be configured.
- The starting directory for the FTP-to-SFTP bridge session can now be configured.
- Usability improvements:
- Settings changes in the Options, Terminal, Remote Desktop, and SFTP tabs now have immediate effect even if a session is active.
- Settings changes in the Services, C2S, and S2C tabs can now take effect, even if a session is active, after clicking Apply.
- Settings changes in the Login and SSH tabs continue to take effect for the next SSH session, and are not applied to any currently active session.
- Errors in initializing a port forwarding or the FTP-to-SFTP bridge will now no longer prevent establishment of the SSH session.
- Algorithms in the SSH settings tab can now be reordered in terms of priority.
- The graphical client's close behavior can now be configured. (Whether to exit, or hide to the system notification area.)
- When using single-click Remote Desktop forwarding in full screen mode, the Remote Desktop window title now reflects the destination server.
Security Clarification: [ 9 April 2014 ]
- We have recently received many inquiries about whether our software is affected by the heartbeat vulnerability in OpenSSL (nicknamed "Heartbleed"). This vulnerability relates to a protocol we do not implement, and a code base that is independent of ours. None of our software shares common code with OpenSSL or OpenSSH.