On 5th of March the following was released:
- ISL Network Start 4.4.1806.11 for Windows (release_date=2018-03-02, os_version=0x06010000-0x7fffffff, build=5e69787a682e50974af1a988aa5458803f17e105, platform=win32)
- ISL Network Start 4.4.1806.11 for macOS (release_date=2018-03-02, os_version=0xa0c00-0xaffff, build=5e69787a682e50974af1a988aa5458803f17e105, platform=mac)
All updates have release date set to 2018-03-02. Your ESS will need to be same or higher to be able to update your server. This release is available to all countries except Japan.
Upgrading to new version
This are server side updates so hosted service users do not need to do anything.
Server license users please check Upgrading Server License
ISL Start - Raise minimal required version to Windows 7 (SPECIAL) [ISLSTART-100] More
New version of ISL Network Start no longer supports Windows versions older than Windows 7.
ISL Start - Add support for flags (FEATURE) [ISLSTART-95] More
Added support for enabling/disabling flags for ISL Start. Flags allow us to enable or disable specific features. The flags are controlled via registry entry on Windows machine and via files on Linux and macOS.
ISL Start - Add support for automatic key upgrade RSA 2048 (FEATURE) [ISLSTART-96] More
In these release, flag for enabling custom RSA keys is enabled. Flags that are enabled are:
- 2017-03-16 LIB-746 automatic key upgrade
- 2017-03-22 LIB-746 disallow cert v1 downgrade
- 2017-03-22 LIB-746 disallow invalid certs
So ISL Start will automatically use stronger key, it will prevent key downgrade (for instance, from 2048bit RSA key to 1024bit RSA key), and it will not allow invalid certs.
ISL Start - Allow more unicode characters in exe name (DEFECT) [ISLSTART-94] More
Previous version of ISL Network Start only allowed ASCII set of characters for the exe file name. Users who changed the name of the executable to a name which included UNICODE character were unable to download the executable. The new version now allows most of the UNICODE characters.
The defect was fixed.
ISL Start - Check HTTP tunnel Content-Type (DEFECT) [ISLSTART-97] More
The autotransport library which is used for creating connections accepted 200 OK text/html response ( which may include captcha, challanges, ... ) returned by the web-proxy even though it should not. The library now checks not just the status code but also the content and rejects the tunnel creation if the content is not HTML tunnel content-type.
The defect was fixed.
Flag for this ticket is enabled by default.