![]() SSH Server Remote Control Panel: - When using the SSH Client to remotely administer Bitvise SSH Server, the SSH Server Remote Control Panel would exit unexpectedly when trying to manually apply an update. The SSH Client's terminal window did not work on Windows XP. This indicates that the terminal window is in a special state and explains why scrolling is disabled. The SSH Client's terminal window now displays a padlock icon in the title bar when the alternate screen is enabled. This is correct behavior, and it avoids confusing users, but it has confused other users, who were used to scrolling in the alternate screen. ![]() Terminal: - Since version 9.23, the SSH Client's terminal window disables client-side scrolling when the server switches to the alternate screen. Currently, these are chacha20-poly1305 and on older Windows versions, the elliptic curve secp256k1. We use OpenSSL for specific cryptographic algorithms not supported by Windows. Bitvise software primarily uses Windows CNG for cryptography. Cryptography: - OpenSSL version updated to 1.1.1s. However, the SSH Client now tries to use them. We cannot guarantee reliability or performance when using such other versions of WinFsp. ![]() The SSH Client can now use WinFsp installed from another source, such as the official WinFsp distribution, or installed by a third-party application, instead of installing its own. WinFsp is required to use the SSH Client's SFTP drive feature, but is not needed for other functions. Installation: - The SSH Client installer now offers the option whether to install WinFsp. Bitvise SSH Client 9.26 EULA: - We updated our EULAs to formalize our existing practices regarding the nature and behavior of our software (it is a product, not a service the data it handles is not sent to Bitvise risk tradeoffs with updates) and the way we provide support (via email and our case management system, in written form). Terminal: - The key combination Alt+Backspace would incorrectly open the terminal window's system menu. Our software does not use OpenSSL features affected by recent OpenSSL security advisories. Unicode code points higher than 65535 Bitvise SSH Client 9.27 Cryptography: - OpenSSL version updated to 1.1.1t. Port forwarding: - The command-line parameters -c2sFile and -s2cFile now also import comment fields, if present Terminal: - If the accent color was enabled for window title bars in Windows, the SSH Client's terminal window title could be hard to read - Double-click word selection did not work correctly on the first word of the first line in the terminal window - The terminal window now supports 5-hexadecimal-digit Unicode characters, i.e. For compatibility with this agent, the SSH Client no longer checks pipe ownership, but implements more validation of information received over the pipe. The SSH Client previously refused to connect to the Windows named pipe created by 1Password because the pipe owner is not a member of the Administrators group or Local System. SSH: - The SSH Client is now compatible with the OpenSSH-style authentication agent in 1Password. The installer will no longer unpack WinFsp files unless Install WinFsp is selected. Bitvise SSH Client 9.31 Fixed: Command-line clients: - Even when output was redirected, the command-line clients sftpc, sexec, stermc, stnlc and spksc would not run unless the process was associated with a console window User interface: - Names and strings containing the & character were not properly displayed in lists File transfer: - When using the Move to dialog in the SFTP window, the SSH Client could crash Bitvise SSH Client 9.28 Installation: - If Install WinFsp was unchecked, the SSH Client installer would still unpack WinFsp files, without registering them.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |