Hell hath no fury like a scorned Apple user. And a situation where Roku drops Roku OS 10.5 on Roku device owners, which then promptly breaks HomeKit support and AirPlay support illustrates this. Reports of this can be found on Roku’s own forums and Reddit, and what makes matters worse is that Roku’s support people appear to have completely lost the plot by seemingly providing rather useless troubleshooting advice. That has led to lots of people being beyond mad. And take it from me, getting Apple users mad is the last thing that a company should ever do. But the problems extend beyond Apple users. Another thread on Roku’s own forums as well as a story on TechCrunch illustrate that 10.5 breaks other functionality.
To be fair to Roku is allowing users to roll back to Roku OS 10.0 which works fine. But this was being handled on a one to one basis rather than the company simply rolling back all Roku users to a stable version that works. At least until TechCrunch posted their story. All of a sudden these instructions appeared to allow users to roll back to a stable version. What’s interesting about this post is that this problem supposedly affects “A small portion of users”. Many of whom if you browse their forums complain about silence from the company when it comes to these issues. Which when a company does that, is never, ever going to end well for said company.
This is the time of year where people buy a lot of electronics including new TVs. And if someone uses the search engine of their choice to find out what the best brand of TV is for their money, I am pretty sure that they will find lots of complaints about Westinghouse, TCL, Sharp and Hisense TVs that are powered by Roku OS. Which means that sales of Westinghouse, TCL, Sharp and Hisense TVs will likely take a dive. Because people will just avoid Roku powered TVs and make a move towards Android TV products.
The bottom line is that Roku released a version of their OS that is buggy, buggy, buggy. And now their users are paying the price. There’s no end to this in sight, and the lack of real, detailed, and honest communication is hurting Roku’s cause. Frankly, the longer this goes on, the more likely that Roku who sells more streaming devices than anyone else is going to lose that marketshare to others such as Google. And they will only have themselves to blame.







The Log4j Vulnerability May Actually Far Worse Than Previously Thought
Posted in Commentary with tags Security on December 19, 2021 by itnerdOne assumption about the 10 out of 10, extremely severe, you must fix right now Log4j security vulnerability was that it was limited to exposed vulnerable servers.
That may now be an incorrect assumption.
The security company Blumira claims to have found a new Log4j attack vector:
Previously, we understood that the impact of Log4j was limited to vulnerable servers. This newly-discovered attack vector means that anyone with a vulnerable Log4j version on their machine or local private network can browse a website and potentially trigger the vulnerability. At this point, there is no proof of active exploitation.
This vector significantly expands the attack surface and can impact services even running as localhost which were not exposed to any network.
The client itself generally has no direct control over these WebSocket connections, which can silently initiate when a webpage loads. WebSocket connections within the host can be difficult to gain deep visibility into, which increases the complexity of detection for this attack.
Blumira suggests users “update all local development efforts, internal applications, and internet-facing environments to Log4j 2.16 as soon as possible, before threat actors can weaponize this exploit further”. This news makes this vulnerability which was already one of the worst ever seen, absolutely devastating.
Happy holidays sysadmins.
Leave a comment »