Sonos CEO Says the Old App Can’t Be Rereleased

The old Sonos app won’t be making a return to replace the buggy new version. According to Sonos CEO Patrick Spence, rereleasing the old app would make things worse now that updated software has already been sent out to the company’s speakers and cloud infrastructure. The Verge reports: In a Reddit AMA response posted Tuesday, Sonos CEO Spence says that he was hopeful “until very recently” that the company could rerelease the app, confirming a report from The Verge that the company was considering doing so. […] Since the new app was released on May 7th, Spence has issued a formal apology and announced in August that the company would be delaying the launch of two products “until our app experience meets the level of quality that we, our customers, and our partners expect from Sonos.” “The trick of course is that Sonos is not just the mobile app, but software that runs on your speakers and in the cloud too,” writes Spence in the Reddit AMA. “In the months since the new mobile app launched we’ve been updating the software that runs on our speakers and in the cloud to the point where today S2 is less reliable & less stable then what you remember. After doing extensive testing we’ve reluctantly concluded that re-releasing S2 would make the problems worse, not better. I’m sure this is disappointing. It was disappointing to me.”

Read more of this story at Slashdot.

‘Something Has Gone Seriously Wrong,’ Dual-Boot Systems Warn After Microsoft Update

Ars Technica’s Dan Goodwin writes: Last Tuesday, loads of Linux usersâ”many running packages released as early as this year — started reporting their devices were failing to boot. Instead, they received a cryptic error message that included the phrase: “Something has gone seriously wrong.” The cause: an update Microsoft issued as part of its monthly patch release. It was intended to close a 2-year-old vulnerability in GRUB, an open source boot loader used to start up many Linux devices. The vulnerability, with a severity rating of 8.6 out of 10, made it possible for hackers to bypass secure boot, the industry standard for ensuring that devices running Windows or other operating systems don’t load malicious firmware or software during the bootup process. CVE-2022-2601 was discovered in 2022, but for unclear reasons, Microsoft patched it only last Tuesday. […]

With Microsoft maintaining radio silence, those affected by the glitch have been forced to find their own remedies. One option is to access their EFI panel and turn off secure boot. Depending on the security needs of the user, that option may not be acceptable. A better short-term option is to delete the SBAT Microsoft pushed out last Tuesday. This means users will still receive some of the benefits of Secure Boot even if they remain vulnerable to attacks that exploit CVE-2022-2601. The steps for this remedy are outlined here (thanks to manutheeng for the reference).

Read more of this story at Slashdot.