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. Unicode code points higher than 65535.Ĭhanges in Bitvise SSH Client 9.27: The terminal window now supports 5-hexadecimal-digit Unicode characters, i.e. Fixed.ĭouble-click word selection did not work correctly on the first word of the first line in the terminal window. If the accent color was enabled for window title bars in Windows, the SSH Client's terminal window title could be hard to read. The command-line parameters -c2sFile and -s2cFile now also import comment fields, if present. 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. 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. If Install WinFsp was unchecked, the SSH Client installer would still unpack WinFsp files, without registering them. For issues that might arise using the latest SSH Client versions, see Known issues.Ĭhanges in Bitvise SSH Client 9.28:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |