When monitoring session activity on busy servers, the Activity tab could experience repeated overflows of events from the SSH Server. Generating a new employed certificate for FTPS did not immediately update certificate information on the Server tab. When the SSH Server Control Panel was started hidden in the system notification area, it would cause a phantom Alt-Tab menu entry to appear. Improved the automatic update locking mechanisms. ![]() If the automatic update process encountered an error while downloading a new version installer from the primary download location, resulting in a partial executable being stored and if download was then successful from the secondary download location the resulting executable would be corrupted. Fixed.Ĭhanges in Bitvise SSH Server 8.45: ![]() When using the bvterm terminal on earlier versions of Windows, if the user pressed Ctrl S, this could cause the terminal server to stop accepting input. Virtual accounts created using Easy settings will continue to have a default Limit to root directory setting that restricts the user to C:\SftpRoot.įixed a situation where settings scrolling could behave incorrectly after expanding and collapsing certain help texts.Īdded optional trace log events for unsuccessful UPnP NAT forwarding add/remove actions. When a new virtual account is created using Advanced settings, it will now by default have no mount points at all. Users of Advanced settings who were unaware of this default mount point found the behavior confusing if they did not create a mount point for the virtual root in individual account settings. Newly created virtual groups no longer have a default mount point that maps the virtual root directory to C:\SftpRoot. The SSH Server will now more properly report such errors.Ĭhanges in Bitvise SSH Server 8.47: When uploading files using the SCP protocol, if an attempt to write file data or set the file time failed, the SSH Server's file transfer subsystem would abort (abruptly ending the SCP exchange) instead of properly reporting the error. The after-installation check did not function on 64-bit systems and would not detect conflicts. However, the check is also performed after installation. When multiple SSH Server instances are being installed, instance name conflicts are intended to be detected during installation. Therefore, the SSH Server will currently not attempt any UPnP actions for IPv6 addresses. However, we were unable to find any devices with which to test this for 8.xx versions. In 9.xx versions, we will be adding experimental support for UPnP IPv6 pinholes. This is not effective for IPv6, and would only generate errors. In previous versions, the SSH Server would attempt to perform the same UPnP actions for IPv6 as it does for IPv4 addresses. UPnP gateway forwarding is now disabled for IPv6 addresses. The SSH Server will now enumerate network adapters to find gateways, and will try to configure those that are suitable. For example, if the first IP address returned by Windows belonged to a Hyper-V virtual switch, this would prevent UPnP NAT forwarding from working. When UPnP NAT forwarding is enabled on a computer with multiple network adapters, the SSH Server was likely to try configuring the wrong gateway. The Log Folder Viewer now improves this by limiting the frequency of visual list updates. The Log Folder Viewer interface would perform poorly if the SSH Server was generating a large number of log files, for example due to intense server activity combined with a small log file rollover threshold. It is now possible to change a Blind drop mount point back to Limit to root directory in Easy settings. It was instead necessary to use Advanced settings to reset mount point permissions. In Easy settings, when a mount point type was set to Blind drop, it could not subsequently be changed back to Limit to root directory. ![]() The SSH Server is security-sensitive, network-facing software, and updating is the only way to receive the latest security and reliability fixes. We are aware of users still relying on versions 7.xx and 6.xx, and sometimes even older. We are at this point highly confident in the security, stability and compatibility of our latest 8.xx versions. The minimum upgrade access to use this version is October 23, 2018. The SSH Server's upgrade access amnesty continues, so that all users of previous 8.xx version can update to the latest version with accumulated fixes. We are receiving many inquiries about whether our software is affected by the recent Log4j vulnerability CVE-2021-44228.īitvise software does not use Log4j, and does not interact with it.Ĭhanges in Bitvise SSH Server 8.49: Bitvise SSH Server 9.xx Version History Bitvise SSH Server 8.xx Version History
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |