The correct behavior is to map the old Default value to Free, and the old Force value to Force. When previous 9.xx versions upgraded settings from versions before 9.xx, the virtual filesystem mount point setting File sharing behavior was upgraded incorrectly. The SSH Server would log an error when sending an email notification to multiple addresses that were duplicates of each other. If more than one task was triggered by the same event, tasks could be removed from the execution queue which should not be removed, and the task that should have been removed would stay in the queue. Our software does not use OpenSSL features affected by recent OpenSSL security advisories. 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. This would effectively prevent the SSH Server from handling more than about 500 concurrent connections. Previous SSH Server 9.xx versions would incorrectly and unnecessarily allocate some thread-local storage indices for each connection, instead of at startup. Improved diagnostic information when sending a test message.Ĭhanges in Bitvise SSH Server 9.27: If the feature to Move completed uploads did not succeed on the first attempt because the file already existed, environment variables were not expanded on subsequent attempts. In previous 9.xx versions, settings that accept strings could not be set to an empty string using PowerShell. When dumping settings in textual format, disabled settings could previously be included. When using BssCfg to generate a new host keypair, the -kpSize parameter did not take effect. This prevented a client from opening a new channel immediately after closing the previous one. In this circumstance, the SSH Server would refuse to open a subsequent SSH channel for a short time after the previous channel was closed. When the no-flow-control extension is enabled, the SSH connection permits only one SSH channel at a time. The SSH Server will no longer stop in this circumstance. The SSH Server would stop if the Stats subdirectory did not yet exist and could not be created. This does not affect the values in existing settings.Ĭhanges in Bitvise SSH Server 9.28: For newly created settings, and for newly created group settings entries in existing settings, the default value of Maximum forward time-steps is increased from 0 to 1, and the default value of Maximum backward time-steps is increased from 1 to 2. Improved default clock leniency for time-based one-time password authentication. Instead, the initial value was always set to Do not change Windows Firewall settings. When the Windows Firewall service is enabled, the initial value is meant to be Open port(s) to local network (subnet scope, non-Public profiles only). In previous SSH Server 9.xx versions, newly created settings would configure the Open Windows Firewall setting to an unintended initial value. The minimum upgrade access expiry date to activate this version is January 1, 2022. This version continues the upgrade access amnesty introduced in version 9.25, so it can be used with any license that is valid for a previous SSH Server 9.xx version. For issues that might arise using the latest SSH Server versions, see Known issues.Ĭhanges in Bitvise SSH Server 9.29:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |