Changelog

 Bugfixes

  • A new paid2 flag has been introduced to support the iOS clients

 Bugfixes

  • Some Android devices, mostly Samsung, failed to decrypt data read from backend storage. This prevents the device to successfully connect and establish a connection to the server.
  • The REST API get_license call uses HMAC encoding function that is incompatible with the core SSL library being used by the backend.
  • The response to the REST API get_sys_info missed a newly introduced field that causes the backend to fail.

 Features

  • This release prepapares steps needed to start supporting IPv6 clients in the future.

 Bugfixes

  • Some AnyDesk clients don't work properly with Address Book feature, such as version 7.1.6 for Windows and version 7.0.0 on macOS. This release fixed that.
  • Android clients hang occasionally during connection establishment to Appliance server. This bug has been fixed.
  • A new SSL version has been updated to be more secured at the Appliance server side. This leads to some SSL functions outdated and not functioning properly. This release updated them.

 Bugfixes

  • Several crashes have been fixed, 'Waiting for image' problem that occurred in several customer environments with v2.1.0 has been fixed

 Features

  • Added support for feature 'Session Invitation', which was introduced with AnyDesk Version 7.0

 Bugfixes

  • Wake-on-LAN not working on MacOS, Windows, Linux, Discovery functionality not working properly, 'Online' field always displays value 'Offline' in the Clients Details tab, Date format for CSV-Export cannot be changed, Cannot add new entries to address book

 Other changes

  • Updated appliance core components to newer version to improve stability and support newer features, Log rotation configuration now includes appliance-crit.log too, default configuration values have been adjusted to reduce the amount of required disk space especially for larger installations, Functionality to limit new connections per defined time frame has been implemented to reduce the load on the appliance server when there is many clients connecting at once (e. g. after a restart of the appliance), Sessions to invalid destinations are not displayed any longer in the Web UI

Registrieren Sie sich für Neuigkeiten, Tipps und mehr

Loading captcha...