Recovery Console is updated to version 2.12.1 which includes the same core libraries and component updates as firmware 4.7.5-1.0.0.The DSOS license data in the report now includes the source of the license (e.g., content or license file), to facilitate diagnostics.This extended information is used by ARYA for improved proof of play reports. Accounting logs now have an extended mode which have extra fields, including UTC timestamps and an on/off indicator in the "close" event which tells if the screen was on during all the time the media was played or if the screen was off during all or part of the time the media was played.The Enable ARYA / Disable ARYA button in Control Center's Operations page has been removed, as it is a duplicate of the one in Control Center's main page and did not always reflect the current state of the player.Control Center and RPC now recognize licenses distributed via the content, in addition to the traditional DSOS license installed out of band.The password complexity check can no longer be disabled. All passwords must now be at least 8 characters long, and have one upper case letter, one lower case, one digit and one special character. Control Center now enforces password complexity to improve security, replacing the previous dictionary based password strength check.jSignage API updated to version 1.7.1 following the jSignage feed cache filling up fix.įirmware version number: 4.7.5-1.0.0-3dcdeed6 Improvements.bluez: solved CVE-2022-39176, which did not affect the firmware.dnsmasq: CVE-2022-0934, which did not affect the firmware.tzdata: updated from 2022b to 2022c, which does not affect any timezone.curl: solved CVE-2022-35252, which affected the firmware.gnutls: solved CVE-2021-4209, which affected the firmware.binutils : solved CVE-2022-38533, which could potentially have affected the firmware.expat: solved CVE-2022-40674, which affected the firmware.dhcp: solved CVE-2022-2928, CVE-2022-2929, none of which affected the firmware.Updated base libraries and components, the main changes are as follows. 802.1x and Wi-Fi enterprise authentication methods using client certificates with a private key (e.g., EAP-TLS) did not work due to a missing component needed to parse the certificates.In some particular conditions (unreliable network connections and feeds with large amounts of data) the jSignage feed cache could fill up resulting in an unhandled exception that would prevent retrying retrieving the feed.Streams with an incomplete description in their SDP could make the player reboot. ![]()
0 Comments
Leave a Reply. |