Kalakshar US

The team behind Rabbitude, the community-formed reverse engineering project for the Rabbit R1, has revealed finding a security issue with the company’s code that leaves users’ sensitive information accessible to everyone. In an update posted on the Rabbitude website, the team said it gained access to the Rabbit codebase on May 16 and found “several critical hardcoded API keys.” Those keys allow anybody to read every single response the R1 AI device has ever given, including those containing the users’ personal information. They could also be used to brick R1 devices, alter R1’s responses and replace the device’s voice. 

The API keys they found authenticate users’ access to ElevenLabs’ text-to-speech service, Azure’s speech-to-text system, Yelp (for review lookups) and Google Maps (for location lookups) on the R1 AI device. In a tweet, one of Rabbitude’s members said that the company has known about the issue for the past month and “did nothing to fix it.” After they posted, they said Rabbit revoked Elevenlabs’ API key, though the update broke R1 devices for a bit. 

In a statement sent to Engadget, Rabbit said it was only made aware of an “alleged data breach” on June 25. “Our security team immediately began investigating it,” the company continued. “As of right now, we are not aware of any customer data being leaked or any compromise to our systems. If we learn of any other relevant information, we will provide an update once we have more details.” It didn’t say if it revoked the keys the Rabbitude team said it found in the company’s code. 

Rabbit’s R1 is a standalone AI assistant device designed by Teenage Engineering. It’s meant to help users accomplish certain tasks, like placing food delivery orders, as well as to quickly look up information like the weather. We gave it a pretty low score in our review, because we found that its AI functionality often didn’t work. Further, users can simply use their phone instead of having to spend an extra $199 to buy the device.

This article originally appeared on Engadget at https://www.engadget.com/rabbit-r1-security-issue-allegedly-leaves-sensitive-user-data-accessible-to-anybody-120024215.html?src=rss 

Verizon has agreed to pay a $1.05 million penalty to settle a Federal Communications Commission investigation into whether the company broke the agency’s rules after a 911 outage. Over a period of one hour and 44 minutes in December 2022, the outage prevented hundreds of emergency calls from going through in Alabama, Florida, Georgia, North Carolina, South Carolina and Tennessee, the FCC said.

The agency added that the outage was akin to one that occurred two months earlier. Although Verizon carried out mitigation efforts to help prevent similar outages to the one in October 2022, “certain failures recurred,” according to the FCC. As part of the settlement, Verizon has committed to implementing a compliance plan to make sure it abides by the FCC’s 911 rules and to adhere to best practices, which include risk assessments and security-related measures.

“When you call 911 in an emergency, it’s critical that your call goes through,” FCC Chairwoman Jessica Rosenworcel said in a statement. “Today’s action is part of the FCC’s ongoing effort to ensure that the public has reliable communications, including access to 911.”

This article originally appeared on Engadget at https://www.engadget.com/verizon-will-pay-a-1-million-fine-to-settle-a-911-outage-investigation-123052358.html?src=rss 

Julian Assange has formally pleaded guilty to violating the Espionage Act at a federal courthouse in Saipan, the capital of Northern Mariana Islands. The WikiLeaks founder was released from prison on June 24 after reaching a plea deal with the US government and quickly boarded a plane at Stansted Airport to make his way to Saipan. While the deal required Assange to plead guilty to “conspiring to unlawfully obtain and disseminate classified information relating to the national defense of the United States,” he still defended himself in court. 

According to The Washington Post, Assange argued that he should’ve been protected by the First Amendment as a journalist. “Working as a journalist, I encouraged my source to provide information that was said to be classified in order to publish that information,” he said. “I believe the First Amendment protected that.” He also said that he believes the First Amendment and the Espionage Act are in contradiction of each other, but he accepts that his actions were in “violation of an espionage statute” and that it would be “difficult to win such a case given all the circumstances.” 

A lawyer for the US government, however, accused him of encouraging personnel with high security clearances to expose classified military information and threaten national security. If you’ll recall, WikiLeaks published classified information related to the wars in Afghanistan and Iraq, which was obtained by whistleblower and former Army intelligence officer Chelsea Manning, under his leadership. 

Lawyers from both sides argued about the time Assange served in prison, but around three hours after the proceeding started, Chief Judge Ramona V. Manglona declared that the 62 months he spent in Belmarsh Prison was reasonable and on par with the time served by Manning. Assange will not spend any time in US custody, but he has to leave the US Northern Mariana Islands immediately. As of this writing, the same private jet that flew him from London to Saipain is waiting to take him to Canberra, Australia. 

This article originally appeared on Engadget at https://www.engadget.com/julian-assange-pleads-guilty-to-espionage-but-defends-himself-in-court-030516412.html?src=rss 

Meta just made an important update for Threads users who are sharing posts to the fediverse. The company began allowing users to opt-in to sharing their Threads posts to Mastodon and other ActivityPub-powered services back in March. But the integration has been fairly limited, with Threads users unable to view replies and most other interactions to their posts without switching over to a Mastodon client or other app.

That’s now changing. The Threads app will now be able to show replies and likes from Mastodon and other services, Meta announced. The change marks the first time Threads users who have opted into fediverse sharing will be able to see content that originated in the fediverse directly on Threads.

There are still some limitations, though. Meta says that, frustratingly, Threads users won’t be able to respond directly to replies from users in the fediverse. It also notes that “some replies may not be visible,” so Threads’ notifications still won’t be the most reliable place to track your engagement.

Meta also announced that it’s expanding the fediverse sharing options to more users, with the feature live in more than 100 countries. (Instagram chief Adam Mosseri said the company is hoping to turn the fediverse beta features on everywhere “soon.”)

The changes are an important step for anyone who cares about the future of decentralized social media. Though Meta has been somewhat slow to deliver on its promises to support ActivityPub in Threads, the app has the potential to bring tens of millions of people into the fediverse.

This article originally appeared on Engadget at https://www.engadget.com/threads-can-now-show-replies-from-mastodon-and-other-fediverse-apps-224127213.html?src=rss