체인지로그

 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 prevented the device to successfully connect and establish a connection to the server.
  • The REST API get_license call used HMAC encoding function that is incompatible with the core SSL library used by the backend.
  • The response to the REST API get_sys_info missed a newly introduced field that caused the backend to fail.

 Features

  • Prepared support for future clients with support for IPv6.

 Bugfixes

  • Some AnyDesk clients did not have a properly working Address Book, such as version 7.1.6 for Windows and version 7.0.0 for macOS.
  • Some Android clients occasionally got stuck while connecting to the Appliance server.
  • After an upgrade to a new SSL version for improved security at the Appliance server side some SSL functions no longer worked properly.

 Bugfixes

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

 Features

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

 Bugfixes

  • Wake-on-LAN did not work on MacOS, Windows, and Linux.
  • Discovery did not work properly.
  • The field showing the online state always displayed value 'Offline' in the Clients Details tab.
  • Could not change date format for CSV exports.
  • Could not add new entries to the 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 the number of new connections per defined timeframe has been implemented to reduce the load on the appliance server when there are too 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