

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
