![]() 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.Fixed an issue where streaming sources which used MPEG-2 Transport Stream (TS) could freeze momentarily every few seconds, this occurred when the MPEG-2 TS only included PCR values every few seconds (violating MPEG-2 TS requirements) and the stream had variable bitrate this is now avoided by using a more robust stream clock estimator.Synchronization of audio and video could be off by a noticeable amount, in particular for streaming sources which use long-delay codecs.The player would reboot when the content referenced the player's own hostname, for instance to trigger an RPC command. ![]()
0 Comments
Leave a Reply. |