Fitbit is active in only 23 countries after leaving Mexico, South Africa, and all Latin American countries. “We communicated that we will stop selling Fitbit products in select countries in order to align our hardware portfolio to map closer to Pixel’s regional availability,” a Google spokesperson confirmed to Cord Cutters News via email. From the report: The move marks a phasing out of Fitbit products after the Big Tech company acquired wearable company in 2021. Last month, Fitbit said it would remove itself from Asian markets Hong Kong, Korea, Malaysia, Thailand, and the Philippines, along with European markets Croatia, Czech Republic, Estonia, Hungary, Latvia, Lithuania, Luxembourg, Poland, Portugal, Romania, and Slovakia. It’s possible Google is removing Fitbit and Nest from the European markets because they don’t have a Google Store support. If that changes, Fitbit products and Nest Aware subscriptions could return. New products like the Pixel Watch could also arrive for the first time. “We remain committed to our customers and have not made any changes that impact the existing Fitbit devices they already own. Existing Fitbit customers will continue to have access to the same customer support, warranties will still be honored, and products will continue to receive software and security updates,” the Google spokesperson said.

Read more of this story at Slashdot.

Source: Slashdot – Google Stopped Selling Its Fitbit Products In Almost 30 Countries

An anonymous reader quotes a report from Ars Technica: Intel on Tuesday pushed microcode updates to fix a high-severity CPU bug that has the potential to be maliciously exploited against cloud-based hosts. The flaw, affecting virtually all modern Intel CPUs, causes them to “enter a glitch state where the normal rules don’t apply,” Tavis Ormandy, one of several security researchers inside Google who discovered the bug, reported. Once triggered, the glitch state results in unexpected and potentially serious behavior, most notably system crashes that occur even when untrusted code is executed within a guest account of a virtual machine, which, under most cloud security models, is assumed to be safe from such faults. Escalation of privileges is also a possibility.

The bug, tracked under the common name Reptar and the designation CVE-2023-23583, is related to how affected CPUs manage prefixes, which change the behavior of instructions sent by running software. Intel x64 decoding generally allows redundant prefixes — meaning those that don’t make sense in a given context — to be ignored without consequence. During testing in August, Ormandy noticed that the REX prefix was generating “unexpected results” when running on Intel CPUs that support a newer feature known as fast short repeat move, which was introduced in the Ice Lake architecture to fix microcoding bottlenecks. The unexpected behavior occurred when adding the redundant rex.r prefixes to the FSRM-optimized rep mov operation. […]

Intel’s official bulletin lists two classes of affected products: those that were already fixed and those that are fixed using microcode updates released Tuesday. An exhaustive list of affected CPUs is available here. As usual, the microcode updates will be available from device or motherboard manufacturers. While individuals aren’t likely to face any immediate threat from this vulnerability, they should check with the manufacturer for a fix. People with expertise in x86 instruction and decoding should read Ormandy’s post in its entirety. For everyone else, the most important takeaway is this: “However, we simply don’t know if we can control the corruption precisely enough to achieve privilege escalation.” That means it’s not possible for people outside of Intel to know the true extent of the vulnerability severity. That said, anytime code running inside a virtual machine can crash the hypervisor the VM runs on, cloud providers like Google, Microsoft, Amazon, and others are going to immediately take notice.

Read more of this story at Slashdot.

Source: Slashdot – Intel Fixes High-Severity CPU Bug That Causes ‘Very Strange Behavior’

A bloc of 48 nations have developed the Crypto-Asset Reporting Framework (CARF), aimed at standardizing reporting requirements for crypto assets to address concerns related to money laundering and tax evasion. It’s set to be implemented by 2027. The Register reports: Developed by the Organisation for Economic Co-operation and Development (OECD), the CARF was developed under the 168-member Global Forum on Transparency and Exchange of Information for Tax Purposes, with the G20 and the Organisation for Economic Co-operation and Development looking on approvingly and lending a hand. As the name implies, that Forum is all about sharing data so that each nation’s tax authorities have the information they need to understand money movements and make sure they can see what they’re allowed to tax. The Forum and the legislative instruments it has fostered include reporting requirements that ensure relevant information is collected by those who facilitate transactions and will be shared.

CARF brings similar reporting requirements to crypto assets. Note the term “crypto assets.” That’s important, because cryptocurrency is not the only blockchain-based instrument that worries authorities. Some, like non-fungible tokens, rely on the same “greater fool” theory that pumped up cryptocurrency prices, and can attract – ahem – interesting investors. But others are far less contentious or speculative, and instead aim to speed transaction processing. Stablecoins, for example, are often suggested as a means for faster and cheaper cross-border transactions than is possible with dominant transaction processing services. Tokenized assets can also be more easily integrated into applications to ease automated money movements.

That speed and flexibility is increasingly appreciated. But unless transactions made with those instruments can be observed, the potential for their use to evade tax authorities is high. CARF’s use of the term “crypto assets” therefore signals an effort to cover the weird world of cryptocurrencies and the emerging classes of classier tokenized assets. The Framework was signed off in March 2023, and in the time since OECD members and other interested nations have been dotting the Is and crossing the Ts to prepare for its implementation. The Framework can be found here.

Read more of this story at Slashdot.

Source: Slashdot – 48-Nation Bloc To Crack Down On Using Crypto Assets To Avoid Tax

Sarah Perez reports via TechCrunch: YouTube today announced how it will approach handling AI-created content on its platform with a range of new policies surrounding responsible disclosure as well as new tools for requesting the removal of deepfakes, among other things. The company says that, although it already has policies that prohibit manipulated media, AI necessitated the creation of new policies because of its potential to mislead viewers if they don’t know the video has been “altered or synthetically created.” One of the changes that will roll out involves the creation of new disclosure requirements for YouTube creators. Now, they’ll have to disclose when they’ve created altered or synthetic content that appears realistic, including videos made with AI tools. For instance, this disclosure would be used if a creator uploads a video that appears to depict a real-world event that never happened, or shows someone saying something they never said or doing something they never did.

It’s worth pointing out that this disclosure is limited to content that “appears realistic,” and is not a blanket disclosure requirement on all synthetic video made via AI. “We want viewers to have context when they’re viewing realistic content, including when AI tools or other synthetic alterations have been used to generate it,” YouTube spokesperson Jack Malon told TechCrunch. “This is especially important when content discusses sensitive topics, like elections or ongoing conflicts,” he noted. […] The company also warns that creators who don’t properly disclose their use of AI consistently will be subject to “content removal, suspension from the YouTube Partner Program, or other penalties.” YouTube says it will work with creators to make sure they understand the requirements before they go live. But it notes that some AI content, even if labeled, may be removed if it’s used to show “realistic violence” if the goal is to shock or disgust viewers. […]

Other changes include the ability for any YouTube user to request the removal of AI-generated or other synthetic or altered content that simulates an identifiable individual — aka a deepfake — including their face or voice. But, the company clarifies that not all flagged content will be removed, making room for parody or satire. It also says that it will consider whether or not the person requesting the removal can be uniquely identified or whether the video features a public official or other well-known individual, in which case “there may be a higher bar,” YouTube says. Alongside the deepfake request removal tool, the company is introducing a new ability that will allow music partners to request the removal of AI-generated music that mimics an artist’s singing or rapping voice.

Read more of this story at Slashdot.

Source: Slashdot – YouTube Adapts Its Policies For the Coming Surge of AI Videos

An anonymous reader quotes a report from Electrek: On Monday, Rivian released an incremental software update 2023.42, which bricked the infotainment system in R1Ses and R1Ts. The company is frantically working on a fix, but it might not be an OTA. […] The vehicles are drivable, but software and displays go black. It appears that the 2023.42 software update hangs at 90% on the vehicle screen or 50% on the app screen, and then the vehicle screens black out. All systems appear to still work except for the displays. At the moment, it appears that Amazon vans are not impacted. Update: The company has acknowledged the issue with affected customers but has yet to issue a fix or plan to fix. Rivian’s vice president of software engineering, Wassim Bensaid, took to Reddit to update users on the situation, writing: “Hi All, We made an error with the 2023.42 OTA update — a fat finger where the wrong build with the wrong security certificates was sent out. We cancelled the campaign and we will restart it with the proper software that went through the different campaigns of beta testing. Service will be contacting impacted customers and will go through the resolution options. That may require physical repair in some cases. This is on us — we messed up. Thanks for your support and your patience as we go through this.

*Update 1 (11/13, 10:45 PM PT): The issue impacts the infotainment system. In most cases, the rest of the vehicle systems are still operational. A vehicle reset or sleep cycle will not solve the issue. We are validating the best options to address the issue for the impacted vehicles. Our customer support team is prioritizing support for our customers related to this issue. Thank you.”

Read more of this story at Slashdot.

Source: Slashdot – Rivian Software Update Bricks Infotainment System, Fix Not Obvious