Aylook release notes v. 9.2.2
The aylook-server release 9.2.2 strictly requires ASC v.1.2 or newer.
WARNING: before you update make a backup of all your data.
The update process changes the user database and an older version of the program does not understand the new format, so the only simple way to restore the old system consists in restoring everything.
Passwords and user permissions work differently after this update. Read the two relevant sections below before updating a system that is in use.
NOTICE: users who had the right to arm/disarm an alarm panel now require a specific privilege.
These release notes cover four releases: 9.1.24, 9.1.25, 9.2.0 and 9.2.2.
The most understandable/visible parts that have been changed are listed here.
Many other dozens of invisible issues have been fixed, that cannot be easily described and understood.
All users are URGED to update, because the current release contains necessary - not only important! - Cybersecurity protections.
Cryptosecurity and Passwords
- Passwords are now managed in a much stronger, state-of-the-art way. Each one is protected individually. Existing passwords are converted automatically the first time each user logs in.
There is no need to re-enter any password. - The shared starting password is void. New users no longer begin with a default key. The administrator enters the user’s initial password when adding him to the users’ group. Users are invited to eventually choose their personal secure password using the relevant option of the login page.
- passwords must now consist of at least 11 characters, mix at least three kinds of character (small letters, capital letters, digits, symbols), contain no spaces, no more than three identical characters in a row, and must not be a common word.
- User passwords are no longer used as the ID of any session.
- Logging into the web interface now works with the new password protection. Passwords are no longer stored anywhere. This change also fixes an earlier problem where the activity log stopped recording events.
User accounts
- An account can now be disabled (suspended), so that it can be enabled again at a later time. See the relevant check-box in the user settings.
- An account can be enabled temporarily, till to a specific expiry date («valid until...»). After that date the account is automatically disabled. He can no longer open new sessions.
- Deactivating an account also results in the immediate termination of any currently open sessions servicing him.
- Access requests from inactive accounts are rejected and the unsuccessful attempt is logged in the Security-Log.
- All the events relevant to logging into the System is now traced in the Security-Log.
System arming
- The Aylook can now be armed and disarmed as a whole. When the system is disarmed, the cameras keep detecting motion and recording, and the timeline keeps showing motion, but no motion events are raised: rules, notifications and alarms based on motion are not triggered. Arming or disarming the Aylook does not arm or disarm a connected alarm panel.
- Two arming modes are available in Setup > Advanced Sensors. In Manual mode all cameras follow the system’s armed state. In Panel mode each camera follows the alarm-panel partition it is linked to, and cameras with no linked partition stay armed.
- Arm/Disarm feature: in order to be available, this function requires the Arm/disarm licence module, activated with a specific activation key released on demand by Anteklab. If the function does not become available after entering the key, restart the Aylook.
- Arming and disarming is only possible for users with the arm/disarm privilege, which can be assigned per user group. By default only the Administrators group has it.
- In ASC 1.2.2 or newer the Armed/Disarmed button appears in the main toolbar only in Manual mode and only when the licence module is active. Armed cameras are marked with a lock icon in the resources list, and the motion bar under the video is red for armed cameras and yellow for disarmed ones.
Alarm panels
- Every command sent to a control-panel is now recorded together with the name of the user who sent it, and the buttons the user presses are recorded as well.
- INIM Prime panels (new series): zones, partitions and outputs are now working. INIM fixed the device-protocol format. BTW: INIM Prime panels accept both the old and the new message format.
- In the cameras-list of the alarm-zone settings now it is possible to select cameras belonging to a slave Aylook.
Car-Number recognition and access control
- Car-Numbers’ verification is now less strict, it ignores dashes and spaces. A registered Number is now matched, instead of being treated as unknown.
- Car-Number readings from Hikvision cameras are no longer lost.
- Event-Notifications showing no Number are simply skipped, do not produce an error notice.
- DB diagnostics following a permission check are now reported instead of being kept hidden.
Cameras and recording
- Recordings to disk that for any reason fail are now traced in the Exceptions-Log and retried.
- Connections to external devices (cameras, panels and I/O devices) are now automatically supervised and restarted in the event that they are lost. In the past they remained stuck until the next System-restart.
- inconsistent or unexpected messages from external devices no longer prevent that the devices are discovered or that the relevant control-panel goes stuck.
Hard disks, backup and licences
- Archive disks are now recognised by a signature of their own, written in the same disk. They were recognised with their serial/number written in the hardware. In the past, if an archive disk was detected as having an unexpected serial/number, it was no longer understood as authorised, then it was removed and the whole startup-process was shut down without any notice for the SysAdmin!
The purpose is to avoid that - in the event that an Archive disk is replaced - the Aylook’s start-up is unreasonably stopped. Now Aylook waits for the archive disks to appear and if something was changed simply updates its record. - Backup Operations no longer reconnect over and over to a backup store.
- Restoring a saved configuration no longer removes the activation of the IDL agent. The removal previously caused video-streams to fall back to simple motion-detection, thus producing false alerts.
System’s startup and stability
- Restart/Reboot: Aylook is no longer starting services too early and it does no longer reboot without sufficient practical reasons. The repeated restart/reboot loop is fixed.
- Network Monitor: the ASC page will no longer be black. The task managing the monitor is constantly watched and is automatically restarted if for any reason it is stopped. The reason why is logged in the Exceptions-Log of the Aylook server..
- The connection of Aylook-Server to the configured AyCloud and/or AyCloudPro servers is constantly checked and is automatically reopened if it drops. In the event that the connection cannot be reopened after N trials, the relevant issue is recorded in the Exceptions-Log of the Aylook server.
- release builds are faster to install. Unused settings are no longer requested.
- Now the client component and the AI accelerator are bound to specific versions, so a new build cannot bind objects in the wrong way.
- Automated tests and code formatting were cleaned up, and the documentation of the release procedure was rewritten in full.
Logging and traceability
- The Security log, the Exceptions-Log and the audit log (the log of administrator’s actions) can be sent out using a standardised protocol, so that a customer's monitoring system can receive and understand them.
- Since fw. 9.2, Log-services are part of the standard Aylook-server installation. Hence receiving, forwarding and recording kernel-messages no longer require any special care.
- Since fw. 9.2, every software upgrade leaves in the System’s-Log a permanent record of which system-partition the appliance was started from.
- The “activity” Log of privileged actions is now complete and not vanishing: entries are no longer dropped.
- Events and Diagnostics notified to connected clients now carry the identifier and the name of the action that generated them.
Languages
- All texts in messages and screens are now fully translated into the selected language (currently Italian and English).