Firmware & Releases
Aylook release notes v. 9.2.5
The aylook-server release 9.2.5 strictly requires ASC v.1.2 or newer. ASC 1.2.5 is recommended, and it is the client shipped with 9.2.5.
Updating from a release older than 9.2? Read the 9.2.2 release notes first: make a backup of all your data before you update, and check the changes to passwords and user permissions.
These release notes cover the changes since 9.2.4.
Web security
- Session cookies are now marked Secure (on HTTPS), HttpOnly and SameSite.
- The web server adds security headers and no longer reveals its nginx and PHP version numbers.
- The appliance now redirects HTTP to HTTPS by default. Requests from the appliance itself and from the cloud link are not redirected. For an installation whose clients or devices still use plain HTTP, support can turn the redirect off.
- Unused legacy service ports are closed by default, and the minimum accepted TLS version is 1.2. Old TLS versions and the RC4 cipher are no longer accepted.
- With the default self-signed certificate, browsers show a warning on HTTPS. A trusted certificate can be installed from the setup.
External login (OAuth / EntraID / Azure AD)
- The identity token returned by the external provider is now fully validated before an Aylook session is created, and only accounts set for external login are accepted. Refused external logins are now recorded in the audit trail.
- Fixed external login not starting the Aylook session: with some clients, the Microsoft sign-in succeeded but no Aylook session began, because the session cookie was not set after the provider callback. The session is now created correctly.
Arm and disarm
- Arm and disarm no longer require the Arm/disarm licence module. Any Aylook can now arm and disarm; the controls appear without the licence key.
Logs
- A new logs page lets you download a system log bundle in one click, ready to send to support, with sensitive values removed.
- System logs are now kept across restarts, so a problem that caused a restart can still be examined afterwards.
Stability
- Fixed an internal service that could stop responding (and restart repeatedly) after receiving a malformed request, which could make the interface and the clients fail intermittently.
- Fixed an appliance restart loop triggered by reloading or deleting a rule.
- Fixed the network monitor failing to load its cameras and resources on some installations.
Fixes
- The firmware update page (
/update/) now asks for a login and is no longer cached.