These logs include things like when you opened, say, the Netflix app and when you closed it on the player.Įxactly how much the device should log and transmit back to HQ is defined by Samsung in an XML logging policy file regularly fetched from this URL: This telemetry is sent to the tech giant's servers when the player's firmware is told to check for a software update.
One thing you have to understand is that these internet-connected Blu-ray players in question are programmed to log their activities and send copies of this information to Samsung. Drilling inĪ Register reader who is savvy with low-level hardware, and asked to be identified simply as Gray, provided us a detailed technical analysis of Samsung's blunder. Crucially, the XML file would be parsed before a new one could be fetched from the internet, so once the bad configuration file was fetched and stored by these particular Samsung Blu-ray players in the field, they were bricked. Upon reboot, the player parsed the XML file again from its flash storage, crashed and rebooted again. This file, when fetched and saved to the device's flash storage and processed by the equipment, crashed the system software and force a reboot. However, it's been suggested to The Register that the cause of the failure was an XML file downloaded by the network-connected devices from Samsung servers during periodic logging policy checks. It was speculated by netizens and some media reports that a HTTPS certificate error was to blame.
0 kommentar(er)
