Bitvise SSH Client v8.44

Зачем ЭТО, когда есть putty ?

In previous 8.xx versions, if the system clock was moved back after a check for updates (in UTC, not time zone specific), an automatic check would be repeated with high frequency. This could consume 80 kbps in bandwidth while the graphical SSH Client was running until the clock caught up. Fixed.
In previous 8.xx versions, an automatic check for updates would be performed if the graphical SSH Client was run with -noRegistry. An automatic check is no longer performed in this situation, but can be performed manually.

Highlights:
The SSH Client now supports automatic updates. An administrator can configure the SSH Client to automatically apply all updates; only recommended updates; only strongly recommended updates; to apply updates only manually; or to never check for updates.
Currently, the SSH Client does not install an update service. It needs to be started from time to time by an administrative user in order to apply updates.
The graphical SSH Client and sftpc now support recursive directory mirroring. A directory and all of its subdirectories and files can be synchronized either in the upload or download direction. The SSH Client can synchronize updated files and detect and automatically remove files and directories from the target location that are not present in the source.
The graphical SSH Client and sftpc can now display hashes (cryptographic digests) of local and remote files if the server supports the SFTP v6 check-file extension.
Bitvise SSH Client and SSH Server now implement automatic host key rotation. The SSH Client will synchronize keys from the SSH Server and any other servers that support the OpenSSH mechanism "hostkey update and rotation". The SSH Server will announce to clients all configured host keys, including those not employed, to facilitate host key rotation. The SSH Client will automatically trust new keys announced by a trusted server and remove any keys the server has removed, as long as they were added automatically.
The SSH Client now supports high resolutions and will display crisp text on high-DPI displays such as retina or 4K. The SSH Client now comes with new, higher resolution icons.
SSH Client profiles downloaded from the internet will now be considered unsafe. If a profile is marked by a browser using which it was downloaded as originating from an unsafe zone, the SSH Client will now load safe parts only. When loading a profile interactively in the graphical SSH Client, a prompt will be displayed, allowing the user to mark the profile as safe. If the user confirms, the profile can be fully loaded.
Cryptography:
Bitvise SSH Server, SSH Client and FlowSsh once again support non-standard DSA keys larger than 1024 bits. We do not recommend using these keys, and new keys of this type cannot be generated. Also, these keys cannot be used when FIPS mode cryptography is enabled in Windows. Re-adding support for these keys is intended to resolve an obstacle that may still be preventing some users of 6.xx versions from upgrading.
When using Windows cryptography, Bitvise SSH Server, SSH Client and FlowSsh now implement a backup strategy for DH and ECDH key exchange. Windows implements key exchange, but it does not expose the agreed value in a form suitable for SSH. Bitvise software must retrieve the value by carefully traversing undocumented Windows structures. In versions 7.xx, this required our software to be upgraded to continue working after the Windows 10 1803 update. Our software will now log a warning and fall back to Crypto++ if it cannot perform key exchange because Windows internal structures have changed. However: if FIPS mode is enabled in Windows, this backup strategy is not used, and the software must be updated.
When importing keys, such as from files, the stage at which an import failed is now described in more detail.
SSH session:
Bitvise SSH Server and Client now support the elevation extension. In previous versions, if a Windows account with administrative rights connected to the SSH Server, the server would always elevate the session if possible. Otherwise, the user would not be able to get an elevated session because there was no way to convey the user's preference. With the elevation extension, the user can request a non-administrative security context by requesting no elevation (elevation is still applied by default). In command line clients including stermc, sexec and sftpc, this is controlled using the switch -elevation=n.
Bitvise SSH Server and Client now support the no-flow-control extension. This disables SSH flow control for clients that only support opening one channel. No flow control is now preferred by sftpc, stermc, sexec and spksc, which only need to open one channel in the SSH session. The graphical SSH Client does not support no-flow-control because it requires multiple channels.
Bitvise SSH Server and Client now support the ext-auth-info extension. This allows the server to respond to user authentication failures with more detailed information in situations where this is safe. For example, if the client attempts to perform a password change but the new password does not meet complexity requirements, the server can communicate this instead of making the user guess.
Bitvise SSH Server and Client now support the delay-compression extension. Delayed compression reduces attack surface for unauthenticated clients by delaying availability of compression until after a user is authenticated. The delay-compression extension is an improvement over previously supported alternatives: the zlib@openssh.com method contains a by-design race condition, while the approach of invoking a second key exchange doubles the overhead of establishing an SSH session.
Terminal:
Settings for the graphical xterm/vt100 terminal console window (totermw) are now stored in the SSH Client profile instead of in the Windows registry.
SFTP:
In the graphical SFTP interface, the Open and Edit commands will now be much more responsive if a transfer is already in progress. The in-progress transfer will be paused and the file associated with the Open or Edit command will be transferred as a priority.
Both the graphical SFTP interface and sftpc can now work with local paths longer than 259 characters, as well as unsafe paths not permitted by Windows in some contexts (e.g. "C:Com1file").
A new file transfer mode, TextLf, is now supported. This works the same as AutoLf, but forces newline conversions without relying on file type detection.
Tunneling:
The SSH Client now displays the country (if available) of remote IP addresses. The SSH Client uses the MaxMind GeoLite2 Country database (under license). The country database comes with the SSH Client installation and is not automatically updated, other than by updating the SSH Client itself.
Command line clients:
It is now easier to connect to SSH servers that accept connections on non-default ports. If no port is specified on the command line, but the SSH Client knows a host key for the destination server, the SSH Client will automatically connect to the port associated with the server in the host key database. If there are multiple port associations, however, the port still needs to be specified, unless one of them is 22.
It is now easier to enable and disable individual algorithms with our command-line clients. Previously, to use non-default algorithms, either a -profile needed to be used, or a complete algorithm list had to be supplied using -hkey, -kex, -encr or -mac. It is now still possible to pass a whole list using the same parameters, or using their new aliases -hkeyAlgs, -kexAlgs, -encrAlgs or -macAlgs. In addition, it is possible to modify the default algorithm lists using -hkeyMod, -kexMod, -encrMod or -macMod. When using the "Mod" versions, provide a comma-separated list of algorithm names with optional prefixes. Names prefixed with "+" are added to the front of the list; names without a prefix are appended to the end; and names prefixed with "!" are removed. Example: -encrMod=+aes256-gcm,!3des-ctr
Utilities:
The log utility now supports filesystem paths in Unicode.

Development, licensing, and US export control:
This is the first version of Bitvise SSH Server, SSH Client, and FlowSsh published from the United States.

All assets, operations, relationships, and agreements related to Bitvise software development and licensing; including license agreements for use of Bitvise software by users; have been transferred from Bitvise Limited incorporated in Gibraltar, to Bitvise Limited now incorporated in Texas.

Final builds are now performed in Texas. Our software development continues in Slovenia, Germany, and Hungary, and may include developers elsewhere in the future.

This move is an administrative change. Our development, ownership, pricing, support, terms and policies and relationship to customers generally remain the same.

For the purpose of export from the United States, our SSH Server, SSH Client and FlowSsh are self-classified as Mass-Market products using the ECCN 5D992, with the encryption authorization type identifier MMKT. These denote eligibility under License Exception ENC § 740.17(b)(1) of the Export Administration Regulations (EAR).

Bitvise SSH Server, SSH Client, and FlowSsh now come with new license agreements. Users must review the new EULAs, even though the terms remain substantially the same. We apologize for this inconvenience, and have attempted to draft the agreements in a way that this might not be necessary very often.

SSH:
Windows 10 version 1709, OS build 17046.1000, changed internal Windows structures in a way that prevented Bitvise SSH Server, SSH Client, and FlowSsh from obtaining the agreed value in DH or ECDH key exchange. This prevented successful SSH connections using this new Windows build. Fixed.

There exist SSH implementations based on WeOnlyDo, e.g. freeSSHd, which might not send failure description and language tag fields when sending an SSH_MSG_CHANNEL_OPEN_FAILURE message. Bitvise SSH Server, SSH Client and FlowSsh will now behave as though these fields were sent as empty strings, instead of disconnecting due to an unexpected packet format.

sexec:
Now supports the command line parameter -git, which is shorthand for the new parameters -cmdQuoted and -exitZero. This allows sexec to be more easily configured for use with Git.

Now supports the command line parameter -cmdQuoted. This can be used when the remote command to execute is provided outside of the -cmd=... parameter, but is enclosed in single or double quotes.

Now supports the command line parameter -exitZero. If the remote command executes and returns exit code 0, this will cause sexec to return exit code 0 as well.

Now supports the command line parameter -p <portNr>. This can be used to specify the port number instead of -port=<portNr>.

Fixed an issue which would cause sexec to interpret as its own parameter a port number passed as part of the remote command to be executed. This could cause sexec to fail, or to connect to the SSH server on an unintended port.

In Windows 10, there appears to be an undocumented change in the GetConsoleTitle function. In previous versions, this would prevent our command line clients (such as sftpc, stermc, sexec, stnlc) from starting when a long command line was used.
In response to attacks on SHA-1, a number of server administrators appear to be reducing supported key exchange algorithms to only diffie-hellman-group-exchange-sha256. This algorithm involves compatibility issues arising from the dynamic generation of DH group parameters, and was disabled in recent SSH Client versions unless enabled explicitly on the SSH tab. Because some servers support only this algorithm, it is now enabled again by default, but algorithms without group exchange will be preferred, if available.

Fixed a rarely occurring race condition which could cause the SSH Client to terminate when closing an SFTP channel.

Implemented changes to reduce the incidence of MSI error 1638 during installation of the FlowSshNet component.
Fixed positioning of the right-click menu for the SSH Client system tray icon on systems with larger than normal (more than 100%) display DPI settings.

Incorporates an update to the Bitvise SSH Server Remote Control Panel for SSH Server versions 7.21+. The update fixes an issue introduced with version 7.21, where exporting a single server host keypair in Bitvise format, using the "Manage host keys" interface in the SSH Server Control Panel, would result in a corrupted file. (Multiple key export worked fine.)

SFTP compatibility improvements for older versions of Cerberus FTP Server:
When downloading a textual file using the file transfer mode Auto Std, the SSH Client will now close the file before reopening it in text mode. This is to avoid issues with servers that do not properly handle two open handles to the same file simultaneously.
The default file transfer mode when connecting to Cerberus FTP Server is now Binary.
When the uninstaller detects that a file is still in use, it can now display the names of applications keeping the file open. (Requires Windows Vista or later.)

Includes an update to the Bitvise SSH Server Remote Control Panel for SSH Server versions 7.21+ included with the SSH Client.

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.

SSH implementations have a chance of generating RSA signatures slightly smaller than expected with a small probability (e.g. 1:200). Windows CNG has been found to not validate such signatures as presented. With our software versions 7.12, this has resulted in occasional connection or login attempt failures. Our SSH Server, SSH Client, and FlowSsh now re-encode RSA signatures, so that smaller-than-expected ones can verify correctly.
Windows CNG, as used by our new cryptographic provider in versions 7.xx, has been found to return an incorrect signature size for odd-sized RSA keys (e.g. for 1023-bit or 2047-bit keys). Most SSH implementations do not generate odd-sized RSA keys, but there are old versions of PuTTY which do (e.g. version 0.62). Our SSH Server, SSH Client, and FlowSsh now take steps to support generating and validating signatures using such keys.
Certain implementations (e.g. OpenSSH version 7.2, but not 7.2p2) have been found to encode RSA signatures using the new signature methods rsa-sha2-256 and rsa-sha2-512 in a way that is not compatible with the specification of these methods. For compatibility, our SSH Server, SSH Client, and FlowSsh will now accept these alternate signature encodings.
Our SSH Server, SSH Client, and FlowSsh now have improved Windows error reporting, distinguishing NTSTATUS error messages from those associated with HRESULT.

Fixed an issue in the command line SFTP client, sftpc; and in the .NET SSH and SFTP library, FlowSshNet; which could cause the process to become unstable and to terminate abruptly on creation of an SFTP channel. The issue appears to have existed in all previous 6.xx versions, but became more visible in FlowSsh 5.37. The graphical SFTP client is not affected. This version continues to include an upgrade amnesty, so that users of previous 6.xx versions can upgrade.

SFTP GUI:
Overall transfer estimates are now available when file transfer is initiated using drag-and-drop, or via clipboard.
File selection in the local pane will no longer be reset due to icons loading in the background.
Improved performance of Select All (Ctrl+A) in Local and Remote view, and in Download and Upload tabs.
Terminal: In the November update to Windows 10, automatic line re-wrap during window resizing has been enabled in the Windows console by default. This interacts poorly with SSH, where re-wrap causes loss of synchronization between the client and server. The graphical SSH client now disables console line wrap when bvterm is started from the graphical SSH Client. Unfortunately, it is not possible to disable this in an existing console session when using stermc.
Fixed an issue in Client key manager which failed to update its list if the slot was changed for a key stored in profile.
Implemented a workaround for an issue in Windows which prevented the graphical SSH Client in versions 6.4x from running on Windows XP and Windows Server 2003 unless a Windows hotfix was applied.
The FlowSshNet DLLs now correctly target .NET Framework 4.0, instead of 4.5.2.

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.)

Installation and upgrade:
This is the first version tested on Windows 10 as part of the development process.
The SSH Client installer now supports the -activationCode parameter. This allows a license code to be applied to the SSH Client during initial installation or an upgrade. The SSH Client will operate with full functionality with or without a license code, but applying it allows users to indicate their licensed status.
On Windows Vista and newer, the installer did not auto-run correctly after the uninstaller prompted for restart during upgrade. Fixed.
Failed and incomplete installations are now detected and displayed, to help the user choose the correct installation directory.
Publisher and version information is now added for display in Add/Remove Programs.
SSH:
SHA-256 public key fingerprints, compatible with the latest OpenSSH versions, are now supported.
The 1024-bit fixed prime Diffie Hellman key exchange method, diffie-hellman-group1-sha1, is now disabled by default, due to doubts about continuing security of Diffie Hellman with a 1024-bit fixed prime. Compatibility with most older servers should be retained via the diffie-hellman-group14-sha1 method, which uses a 2048-bit fixed prime. We recommend migrating older SSH servers to new versions supporting ECDH and ECDSA.
Symmetric encryption algorithms that use CBC mode are now disabled by default. Bitvise SSH Client and Server implement defenses against attacks on CBC mode, but other implementations that still use CBC mode are unlikely to implement such defenses. Most implementations should now support encryption in CTR mode.
In past Bitvise SSH Client 6.xx versions, gssapi-keyex authentication was always unavailable. Fixed.
Graphical client:
The graphical SFTP client now maintains a list of recent locations.
Fixed an issue which prevented use of the -proxyUserName parameter with the graphical SSH Client. Command-line clients were unaffected.
Fixed an issue which caused the graphical SSH Client to send an empty response to all prompts other than the first one in keyboard-interactive authentication. This issue did not affect command-line clients.
Command-line clients:
A new retry utility is now included, which can be used to automatically retry a command based on its exit code. Run retry without parameters for help. The utility can be used with any command line program, but is intended specifically for use with sftpc.
The log utility now supports an additional parameter, -t, which will cause the utility to prefix every line of output with a timestamp. This can be used to log and timestamp the output of any command line program, and is intended specifically for use with sftpc.
The command-line SFTP client, sftpc, now supports tab expansion based on wildcard patterns.
sftpc now reports a full completion timestamp for each transfer.
sftpc now waits a maximum of one second if the server does not respond to SFTP channel close. Previously, a server that did not respond to channel close would cause sftpc to wait indefinitely.
SFTP:
In versions 6.23 - 6.31, a command such as "put directory" would not upload the contents of "directory", but instead only create an empty directory. In addition, a command such as "lrm directory -s" would always fail when the directory being removed was not empty. Fixed.
OpenSSH servers contain a flaw where a noisy shell startup script, such as a .bashrc file, will cause garbage data to be passed to an SFTP client on the SFTP channel. Previously, this would prevent establishing an SFTP session. The client now ignores such invalid data, and looks for a particular byte signature to indicate the start of the server's first packet in the SFTP session.
The Start in last directory feature in the graphical SFTP interface should work again.
Turning off the Start option did not pause new transfers in the graphical SFTP interface when they were initiated via drag-and-drop or a clipboard action. Fixed. The transfers did start paused when using the Upload and Download buttons.
When transferring files in text mode using SFTP version 4 or higher, the ignored offset is now set to an invalid 64-bit value instead of zero. This prevents an unending transfer with servers that do not ignore the offset as required by the textual transfer mode (e.g. older versions of VShell).
Fixed an issue which could cause the SFTP client to send more channel data after sending channel close.
FTP-to-SFTP bridge:
Fixed an issue that could cause the FTP-to-SFTP bridge to freeze while downloading.
When the FTP-to-SFTP Bridge was configured to listen on all interfaces (0.0.0.0), directory listings and file transfers would not work in passive mode. Fixed.
Terminal:
Double-width Chinese characters were not being properly rendered in recent SSH Client versions. This should now work properly in most cases.
Fixed problems with some Ctrl keyboard sequences: Ctrl+[, Ctrl+I, Ctrl+M, Ctrl+H, and Ctrl+J.
Fixed a scrolling problem that could occur if the last line of output was empty (e.g. when using cat).
Fixed an error that would frequently occur on Windows 10 when resizing a bvterm window in a Bitvise SSH Server terminal session. Further improved resizing on Windows 10.
If Auto close window was set to Never, and a terminal session closed successfully, the terminal window would consume 100% of a CPU core until closed. Fixed.

Windows compatibility:
Fixed a change implemented in version 6.22 which prevented the SSH Client from running on Windows XP SP1 and Windows Server 2003.
In terms of the oldest Windows versions supported, the SSH Client now officially requires Windows XP, Windows Server 2003, or later. The SSH Client no longer supports Windows 2000.
Installation:
The console output stream implementation provided by the C++ run-time library, and used by the SSH Client installer, did not properly handle Unicode characters that could not be represented in the output code page. Replaced with our own output stream implementation.
General:
The graphical client now displays the current date in the log area when the client is started, when the date changes, and when the log is cleared.
When key exchange fails due to no match in algorithms, the local and remote algorithm lists are now logged.
File transfer:
The graphical file transfer client now accepts drag and drop from other applications.
The Edit context menu option is now available for files of all extensions, including no extension. An Edit with... context menu option is now also available, and a default editor can be configured.
For compatibility with non-Bitvise servers that support SFTP version 6, the SSH Client no longer requests the flag SSH_FXF_BLOCK_WRITE when sending an SSH_FXP_OPEN request. This restores compatibility with servers including ProFTPD with mod_sftp when SFTP version 6 is used.
Terminal:
On Windows 7, an apparent bug in the Windows console implementation would cause stermc to crash when exiting. The console window itself would close shortly thereafter. We implemented a workaround for this issue.
For compatibility with nano, the SSH Client's new xterm/vt100 terminal console now attempts to make smarter decisions about what type of newlines to send when pasting from clipboard.
The SSH Client will now log any messages sent by the server as SSH_EXTENDED_DATA_STDERR before closing a successfully opened terminal channel.
Remote Desktop:
Improved the method the SSH Client uses to update the Remote Desktop window title.
Command line clients:
Implemented support for Ctrl+Left/Right to move to previous/next word, and Ctrl+Home/End to delete text until beginning/end of line.
Clients stnlc and spksc now also support Tab-completion.

File transfer:
The graphical SFTP client now supports editing of remote files. A remote file can be edited using right click > Edit. The client will automatically download the file; open it in the editor associated with its file extension in Windows; then monitor the local copy of the file for changes. When changes are saved, the file will be uploaded automatically.
The graphical SFTP client now supports right click > 'Open with...', both for local and remote files.
Further improvements to tab completion in sftpc.
The 'move' and 'lmove' commands in sftpc now support the -o (overwrite) parameter.
In command line clients, the -keypairFile parameter would only work if another keypair (even if unused) was available, either in the profile being used, or in global client settings. Fixed.
Fixed a long-standing graphical glitch which would cause edit boxes in the graphical SSH Client to temporarily lose borders whenever the Sysinternals Process Explorer was launched.

SSH:
Key exchange methods that use group exchange will now be de-prioritized when connecting to all non-Bitvise SSH server implementations. This serves to avoid a compatibility issue where most non-Bitvise SSH servers will generate weak DH groups which cannot be used with the FIPS 140-2 validated cryptographic provider used by Bitvise SSH Client. Previously, group exchange was already de-prioritized for a handful of known SSH server implementations with this issue.
It is now easier to turn compression on and off using the "Prefer zlib compression" setting on the SSH tab.
File Transfer:
The sftpc command line client now supports batch rename (using wildcards).
The sftpc command line client now supports command, path, and filename completion using the Tab key.
Remote file copy is now supported, in the graphical SFTP interface as well as the sftpc command line client, with SSH servers that implement the SFTP version 6 file copy extension (including Bitvise SSH Server).
The graphical SFTP interface now supports drag and drop, copy, cut, and paste features.
Remote Desktop:
Smart sizing - automatic adjustment of remote desktop resolution to local client window size - can now be enabled or disabled for forwarded Remote Desktop connections in the SSH Client profile.
Improved compatibility of authentication credentials with Remote Desktop servers running on Windows Server 2003 and XP.
When not using SSH login credentials, the domain name to use for Remote Desktop authentication can now be configured in a field separate from the user name.
Fixes:
Fixed a problem with newlines when pasting text into joe/nano editors.
Fixed an issue which would cause the SSH Client to stop with an assertion failure if it was configured to use a proxy of type SOCKS4 with "Resolve locally" disabled.
Fixed an issue which would cause command-line proxy parameters to not work correctly.
Fixed an issue introduced in version 6.21 which would cause the SSH Client to close a connection before sending a failure reply in the event of a connect failure when using dynamic port forwarding (the SOCKS/HTTP CONNECT proxy forwarding feature).
Fixed an issue which would cause Export and Remove buttons to not be available in the Host Key Manager unless a named (file-based) profile was opened.
Fixed an issue which would prevent the Client Key Manager from importing ECDSA private keys in OpenSSH format if they were password protected. Improved accuracy of error messages if an invalid password is entered.
The -flowDebugFile feature will no longer truncate quantum data, allowing a complete debug log of the SSH session to be recorded.

The SSH Client now supports SSH protocol obfuscation. When connecting to an SSH server that supports it, obfuscation makes it harder for an observer to determine that the protocol being used is SSH.
The sftpc command line client now supports tab completion.
If a command is configured to be run under On Login > Execute on the Options tab, the SSH Client can now also be configured to close or terminate the program launched this way after the SSH session ends.
Remote Desktop forwarding:
A username and password can now be configured for single-click Remote Desktop forwarding, separately from the credentials used to log in via SSH.
If the user name for Remote Desktop starts with ".\", it will now be communicated to the Remote Desktop client in the same way as in version 6.08 and older.
Graphical xterm console:
Block selection and copying is now supported by using the mouse to select while pressing the left Alt key.
A tooltip is now displayed when text is copied to clipboard, or pasted in the terminal window. The tooltip can be turned off through the console's system menu.
Fixed an issue which would cause a Ctrl+Alt+key event to be sent to the server in addition to a national character, when the user intended to input only a national character with AltGr+key.
Links on the SSH Client's About tab now work correctly again.
Fixed an issue that would cause the SSH session to terminate with an error after applying removal of some, but not all, client-configured C2S or S2C port forwarding rules.
To maintain installer size, an initial Bitvise SSH Client 6.22 installation no longer includes files to support the Remote Control Panel feature for WinSSHD versions older than 5.22. The files necessary to use this feature with such older versions continue to be available separately.

Profiles:
Per-profile host keys and client keypairs: Host authentication public keys, as well as client authentication keypairs, can now be stored in individual profiles. This allows a profile to contain all information needed to establish an SSH session, without requiring host key or client keypair information to be passed via command line parameters, or stored in Windows registry.
When a host key is verified by the user, and the SSH session uses a profile, a copy of the host key will now be automatically saved in the profile.
Per-profile proxy settings: Proxy settings can now be configured for individual profiles as well, allowing a profile to override globally configured proxy settings.
Implemented measures to ensure profile consistency when accessed by multiple SSH Client instances.
When opening profiles created using Bitvise SSH Client 4.xx, previous 6.xx versions would be unable to open profiles with an invalid Remote Desktop Computer field. Attempts to open such profiles would fail with a validation error, but a description of the validation error would not be displayed. Fixed.
SSH:
Delayed negotiation of zlib compression, as advertised by servers using the 'zlib@openssh.com' algorithm, is now supported. Because of an inherent race condition in the OpenSSH implementation of delayed compression, Bitvise SSH Client implements this in the same way as PuTTY - by triggering a second key exchange after successful authentication.
Authentication:
Graphical management of server-side public keys: The graphical SSH Client now supports management of the user's public keys trusted by the server using SPKS, the Secure Shell Public Key Subsystem. As in previous 6.xx versions, this functionality also continues to be available in the spksc command line client.
Agent forwarding: The SSH Client now supports agent forwarding if it is supported by the SSH Server. A remote SSH client running on the server can use agent forwarding to perform public key authentication using client keypairs managed by the local SSH Client.
Agent support: Both the graphical client, as well as the command line clients, now support public key authentication using keypairs available through the OpenSSH authentication agent (ssh-agent) or the PuTTY authentication agent (pageant).
Improved the choice of default subsequent authentication method offered when the server requires both password and public key authentication.
Fixed an issue which prevented use of public key authentication as configured in a profile supplied with the "-profile" command line parameter.
Terminal:
When using the graphical SSH Client in conjunction with a non-bvterm terminal protocol, such as xterm, the SSH Client will now use a custom terminal window with features not available with a Windows console window:
Draggable resizing
Support for xterm-256color
Support for non-block copy & paste
Improved performance
Mouse input is now supported. Supported mouse modes are X10 compatible, Normal, Cell Motion and All Motion. Supports X10, UTF8, SGR, and URXVT coordinates. Supported are all 3 main mouse buttons; combinations with Alt, Shift, and Ctrl keys; and the mouse wheel. When mouse tracking is enabled by the server, client-side text selection and copying remains possible using the left Shift key.
The terminal window color palette can now be configured.
A setting is now supported to allow the terminal window to remain open after a terminal session closes.
The terminal client will now display terminal titles received from the server via xterm. The client will append such titles to the initial title.
Characters that could not normally be entered using the currently active input method can now be entered using Alt + NumPad or using copy and paste.
File transfer:
sftpc now supports launching local commands prefixed with '!' in scripted mode. A non-zero return code is treated as an error.
sftpc can now execute "ldir" to provide expected results if the current local directory points to a network share.
Remote Desktop:
Automatic sign-on for Remote Desktop now works with Microsoft accounts, as well.
General:
Sessions that attempted to register a large number of simultaneous client-to-server port forwarding rules could be terminated by an error. Fixed.
Improved disconnection responsiveness and reliability.
Improved trace logging.
In recent 6.xx versions, a license code could not be applied unless the client was started using elevation. Fixed.

Improved reliability and responsiveness of disconnecting a session, resolving an issue where the client could hang during a disconnect.

In version 6.05, an issue was introduced that would cause the SSH session to terminate with an error during a server-to-client port forwarding failure. Fixed.
In "Reconnect always" mode, when automatically reconnecting without first being successfully authenticated, the client would display the user authentication dialog instead of proceeding with the configured initial authentication method. Fixed.
In SFTP Upload and Download panes, the individual file progress bar in the list control was always stuck at 0% when transferring. Fixed.

Implemented support for unattended password authentication via the "keyboard-interactive" method. When the SSH Client is configured to authenticate with a stored password, it will now try to pass the stored password to the "keyboard-interactive" method if "password" authentication is not available.
User authentication keypairs can now be imported and exported in the PuTTY format.
Since migrating Bitvise SSH Client to use Crypto++ as a FIPS 140-2-certified cryptographic provider in versions 6.xx, Diffie Hellman-based SSH key exchange methods that use group exchange have not been working well with servers including OpenSSH, Tectia, and IBM Sterling Connect. The issue arises because these servers generate random DH group parameters which do not pass validation by Crypto++, and we cannot disable this validation in FIPS mode. To avoid this issue, we are changing default Bitvise SSH Client settings to disable DH key exchange methods that use group exchange. We encourage use of the new ECDH key exchange methods instead.
The User keypair manager failed to show the first few characters of MD5 fingerprints below the keypair list. Fixed.

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.

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.

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.

The graphical SFTP remote files pane was incorrectly using start directory and other settings from the local pane.

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.

SFTP: For compatibility with WS_FTP servers, when attempting to verify existence of the target directory during upload, the client will now assume that a generic failure response means the directory does not exist, and will try to create it. Previously, the client acted this way only if the server's response was along the lines of "path does not exist".
When the graphical client is closed, it will no longer pop up a profile save dialog if profile contents were modified only through a command line parameter.
With newer Remote Desktop clients, the feature "Use SSH login credentials" would fail when using local accounts. Now fixed.
Terminal client for non-bvterm protocols: Fixed issue with reporting cursor position.

The support for Ctrl+Alt+[A-Z] character combinations implemented in version 4.61 was conflicting with AltGr+[A-Z] combinations on non-US keyboards. The implementation has been improved so that Left Ctrl + Left Alt + [A-Z] will send the Ctrl+Alt+[A-Z] combination, but AltGr+[A-Z] will send the special character defined by the current keyboard configuration.

Fixed an issue which caused Bitvise SSH Client 4.60 to display incorrect Bubble-Babble fingerprints.
Fixed an issue which caused the graphical SSH client to either crash, or open an incomplete dialog, when clicking the Initial Directory link on the SFTP tab.
Changed command line handling so that double backslashes ("\\") will be replaced with a single backslash only if followed by a quotation mark.
The sexec command line client no longer hangs if the exec request is rejected by the server.
Fixed an issue which could have caused the graphical SSH client to become unresponsive if a third-party application was installed that sent an unexpected GUI message.
vt100/xterm terminal client:
Implemented support for Ctrl+Alt+[A...Z] key combinations. Additionally, with xterm, Ctrl, Alt and Shift combinations are now supported with the following keys: cursor arrow keys, Home, End, Insert, Delete, PgUp, PgDn, and F1-F12. (However, Shift+PgUp and Shift+PgDn are used to scroll the history buffer, and are not sent to the server.)
Restored behavior from previous client versions so that Ctrl+Break does not end the terminal client, but instead sends the appropriate signal to the server.
The vt100/xterm terminal client will no longer exit if it receives characters from the server that are invalid with the character encoding being used.
Fixed a bug with cursor position reporting in the vt100/xterm terminal client, so it will no longer cause strange characters to appear on screen, e.g. when starting Vim.