v8.4 [May 10, 2020]
- Installation:
- The SSH Client adds its installation directory to the system PATH environment variable when installing, but did not remove it when uninstalling. The SSH Client installation directory is now removed from PATH when uninstalling. Reinstallations or upgrades from version 8.43 will briefly remove and then re-add the SSH Client installation directory to PATH.
- SSH:
- Certain versions of the Pragma Fortress SSH server - including the most recent version when testing - can send a corrupted SSH authentication banner where an inexact, duplicate copy of the banner message is included before the language tag. SSH Client versions 7.xx and earlier could connect because they ignored the language tag, but SSH Client 8.xx versions would not because they check that the language tag does not exceed an unreasonable length.
The SSH Client now allows an exception for this server where the incorrect encoding is ignored. If the server cannot be identified as "Pragma FortressSSH", the language tag length check remains enforced.
- Command-line clients:
- Previously, an implied command such as the following:
sexec user@host dir /?
... would incorrectly cause command line clients including sftpc, stermc and sexec to display their own help text instead of invoking the remote command as specified. Fixed.
- Graphical client:
- The graphical SSH Client now detects and warns about an insecure installation directory in an expanded, more thorough set of circumstances.
- In version 8.42, the -sendExtInfo=... parameter was added to command line clients. An equivalent setting, Send EXT_INFO, is now also available in the graphical client, on the SSH tab.
- SFTP:
- Fixed an issue with auto-completion which could cause the SFTP graphical interface to dead-lock.
v8.38 [Apr 19, 2019]
- When creating a new profile or when using the SSH Client's command line clients (sftpc, sexec, stermc, stnlc, spksc) without the -profile=... parameter, the SSH Client will now by default prefer Curve25519 and ECDH key exchange over traditional Diffie Hellman. Classic DH is significantly slower and more computationally expensive, while there continues to be no known reason to de-prefer Elliptic Curve cryptography. Existing profiles are unaffected and will keep their algorithm preference order.
- SFTP GUI: In Windows 10 version 1903, when using the Open action or when double-clicking a file whose extension has no file association, Windows may no longer offer to select a program with which to open the file, but may instead fail the action. The SSH Client will now automatically use Open with if the Open action fails in this manner.
- SFTP GUI: The SFTP GUI now supports mouse button 4 to trigger the Back action and mouse button 5 to trigger Forward, in a manner consistent with common browsers.
- There exist interim, but deployed versions of SSH implementations including SmartFTP which implement the no-flow-control extension based on a previous, non-final draft where the extension value was empty. Bitvise SSH Server, SSH Client and FlowSsh will now no longer disconnect when receiving an unrecognized no-flow-control extension value, but will attempt to continue; and will now treat an empty value as if the remote party sent "p" (for "preferred").
- Polished a few issues in BvSshUpdate, the SSH Client's command-line version update utility.
v8.29 [Dec 24, 2018]
Fixed an issue in previous 8.xx versions which would prevent Bitvise SSH Client and FlowSsh from connecting to a server that supports host key synchronization and employs a key type the client does not support. This affected connections from Windows XP and Windows Server 2003, where our cryptographic provider does not support Ed25519; and use under FIPS mode, where Ed25519 and ECDSA/secp256k1 are not supported.
v7.39 [May 9, 2017]
- Small changes in key places improve CPU efficiency on the order of 30% (impact may depend on the system). This improves transfer speeds where CPU is the bottleneck – or maintaining same performance, allows for a greater number of simultaneous connections. Users who were previously maxing out a single core and seeing transfer speeds of e.g. 150 MB/s, may now see e.g. 200 MB/s.
- Fixed VT-100 keyboard mappings. Function keys will now be sent correctly over VT-100 and xterm when VT-100 mode is enabled. Adapted navigation keys for VT-100, including: Insert, Delete, Home, End, Page Up, and Page Down.
- Removed unnecessary input length limitations in user authentication input boxes by permitting scrolling. This should allow the use of long YubiKey two-factor authentication strings using the method keyboard-interactive.
- Diffie-Hellman key exchange algorithms that use group exchange are once again deprioritized, regardless of which cryptographic provider is in use.
v7.15 [Jul 1, 2016]
Updated EULA to make more explicit our licensing and support policies. The policies themselves remain unchanged.
In command line clients (sftpc, stermc, sexec, stnlc, spksc), the parameter -proxyPassword had no effect. Fixed.
v6.47 [Aug 20, 2014]
Improved uninstallation to reduce the likelihood that Windows might need to be restarted to complete a reinstallation or upgrade. If a restart would be required, the user can now choose to abort reinstallation.
In the graphical SFTP interface, file icons are now loaded asynchronously, to avoid the interface blocking due to lengthy antivirus scans.
Fixed an issue that prevented X11 forwarding from working properly in terminal windows other than the first one. This issue was introduced with 6.xx versions.
Terminal:
The RIS and DECST instructions to reset terminal and screen buffer are now supported in conjunction with xterm. This allows the Linux reset command to be used to fully reset the terminal.
A copy and paste notification is now displayed also when Shift Insert is used to paste.
FTP Bridge:
Fixed an issue which caused the SSH Client main window to freeze if an FTP client was not disconnecting the control connection.
Added IPv6 support to the FTP Bridge, implementing support for EPSV and EPRT commands.
The GSSAPI DH key exchange method with group exchange is now also de-prioritized when connecting to non-Bitvise servers, along with other methods that use group exchange. (Non-Bitvise servers tend to generate DH parameters that are incompatible with the FIPS cryptographic provider used by FlowSsh; this results in key exchange failures.)
v4.63 [Feb 4, 2013]
•The xterm/vt100 terminal client has been re-implemented to improve performance and add new features.
•Default colors displayed by the xterm/vt100 terminal client can now be configured on the Terminal tab.
•Command-line clients (sftpc, stermc, sexec) now support a parameter to enable delegation when using Kerberos user authentication with standard SSH host authentication and key exchange. Previously, the command line clients supported delegation only when using Kerberos-based key exchange.
•The Host Key Manager can now store multiple host key fingerprints per SSH host. When a new host key is verified by the user, it is now added to other known keys for that host, instead of replacing them.
•To improve compatibility with some FTP clients, FTP-to-SFTP bridge will now send more conventional reply codes to USER and PASS commands, mimicking the behavior of FTP servers that require authentication.
•When launched from the Bitvise SSH Client graphical client, the terminal client now supports executing a custom command (as an exec request) instead of requesting a plain shell.
•When using single-click Remote Desktop forwarding, temporary RDP profiles are now removed from the "most recently opened" list for the Remote Desktop Connection shortcut.
•WoW64 filesystem redirection is now disabled when creating temporary RDP profiles for single-click Remote Desktop forwarding.
•Improved keyboard accessibility for launch bar icons in the graphical client.
