An anonymous reader quotes a report from BuzzFeed News: Noises linked to mysterious injuries among US diplomats in Cuba were most likely caused by crickets — not microwave weapons — according to a declassified scientific review commissioned by the US State Department and obtained by BuzzFeed News. The State Department report was written by the JASON advisory group, an elite scientific board that has reviewed US national security concerns since the Cold War. It was completed in November of 2018, two years after dozens of US diplomats in Cuba and their families reported hearing buzzing noises and then experiencing puzzling neurological injuries, including pain, vertigo, and difficulty concentrating. Originally classified as “secret,” the report concluded that the sounds accompanying at least eight of the original 21 Havana syndrome incidents were “most likely” caused by insects. That same scientific review also judged it “highly unlikely” that microwaves or ultrasound beams — now widely proposed by US government officials to explain the injuries — were involved in the incidents. And though the report didn’t definitively conclude what caused the injuries themselves, it found that “psychogenic” mass psychology effects may have played a role.

“No plausible single source of energy (neither radio/microwaves nor sonic) can produce both the recorded audio/video signals and the reported medical effects,” the JASON report concluded. “We believe the recorded sounds are mechanical or biological in origin, rather than electronic. The most likely source is the Indies short-tailed cricket.” The report’s findings fly in the face of a medical report commissioned by the State Department and published by a National Academies of Sciences panel last year, which found that microwaves were the “most plausible” cause of the symptoms. That panel was not provided with the JASON report as part of its assessment, the NAS told BuzzFeed News.

Read more of this story at Slashdot.

Source: Slashdot – A Declassified State Department Report Says Microwaves Didn’t Cause ‘Havana Syndrome’

Researchers have demonstrated that someone could use a stolen, unlocked iPhone to pay for thousands of dollars of goods or services, no authentication needed. Threatpost reports: An attacker who steals a locked iPhone can use a stored Visa card to make contactless payments worth up to thousands of dollars without unlocking the phone, researchers are warning. The problem is due to unpatched vulnerabilities in both the Apple Pay and Visa systems, according to an academic team from the Universities of Birmingham and Surrey, backed by the U.K.’s National Cyber Security Centre (NCSC). But Visa, for its part, said that Apple Pay payments are secure and that any real-world attacks would be difficult to carry out.

The team explained that fraudulent tap-and-go payments at card readers can be made using any iPhone that has a Visa card set up in “Express Transit” mode. Express Transit allows commuters around the world, including those riding the New York City subway, the Chicago El and the London Underground, to tap their phones on a reader to pay their fares without unlocking their devices. “An attacker only needs a stolen, powered-on iPhone,” according to a writeup (PDF) published this week. “The transactions could also be relayed from an iPhone inside someone’s bag, without their knowledge. The attacker needs no assistance from the merchant.”

This attack is made possible by a combination of flaws in both Apple Pay and Visa’s systems, the academic team noted. “The details of this vulnerability have been disclosed to Apple (Oct 2020) and to Visa (May 2021),” according to the writeup. “Both parties acknowledge the seriousness of the vulnerability, but have not come to an agreement on which party should implement a fix.” “Variations of contactless-fraud schemes have been studied in laboratory settings for more than a decade and have proven to be impractical to execute at scale in the real world,” Visa said in a statement to the BBC, adding that its fraud-detection systems would flag any suspicious transactions. Apple meanwhile shifted the responsibility to Visa and told the outlet, “We take any threat to users’ security very seriously. This is a concern with a Visa system, but Visa does not believe this kind of fraud is likely to take place in the real world given the multiple layers of security in place. In the unlikely event that an unauthorized payment does occur, Visa has made it clear that their cardholders are protected by Visa’s zero-liability policy.” The researchers say users can protect themselves by not using Visa as a transport card in Apple Pay, and if they do, by remotely wiping the device if lost or stolen. The bug does not affect other types of payment cards or payment systems.

Read more of this story at Slashdot.

Source: Slashdot – Apple Pay With Visa Hacked To Make Payments Via Unlocked iPhones

Carmaker Opel, which is part of the Stellantis group, said on Thursday it will close one of its plants in Germany until at least the end of the year due to chip shortages. Reuters reports: Production at the Eisenach plant, which makes internal combustion engine and hybrid electric cars, should start again in 2022, although an Opel spokesperson could not specify a date. Some 1,300 workers employed at the plant will be temporarily laid off, Opel said, with a separate plant in France picking up some of the production. Stellantis has halted production at other plants, including in Europe and Canada, forecasting that it would make 1.4 million fewer vehicles this year due to the chip shortage.

Read more of this story at Slashdot.

Source: Slashdot – Chip Shortage Leads Carmaker Opel To Shut German Plant Until 2022

New submitter thegreatnick writes: The next generation of Fairphone — an attempt to make an ethical smartphone — has been announced with the Fairphone 4. The base specs include a Qualcomm Snapdragon 750G SoC, 6GB of RAM, and 128GB of storage (upgradeable to 8GB and 256GB). On the front, you’ll get a 6.3-inch, 2340×1080 LCD display with slimmer bezels (compared to the Fairphone 3 design) and a teardrop notch for the 25-megapixel front camera. The 3,905mAh battery is Qualcomm Quick Charge 4.1 compatible, so if you have a compatible USB-C charger (not included in the box to reduce waste) you can take the battery from 0-50% in 30 minutes. The phone ships with Android 11 and has a side-mounted fingerprint reader in the power button, a MicroSD slot, and the option for dual-SIM usage via one physical nanoSIM and an eSIM. Continuing Fairphone’s progress in making a “fair” supply chain — both ethically-clean raw materials and paying workers a fair wage — it also describes the 4 as “e-waste neutral.” This is a neat way of summing up the idea that the company will recycle one device for every Fairphone 4 it sells. In addition, Fairphone can boast that it now uses 70% “fair” materials inside the handset, including FairTrade Gold and Silver, aluminum from ASI-certified vendors, and a backplate made from 100% post-consumer recycled polycarbonate. In an upgrade to previous models, the Fairphone 4 has dual cameras, though it loses the headphone jack. The company says this was to achieve an IP54 waterproof rating (light splashes) — a first for the Fairphone brand. It’s also been announced that it will come with an industry-leading 5-year warranty and aims to get 6 years of software updates for the phone.

Read more of this story at Slashdot.

Source: Slashdot – Fairphone’s Latest Sustainable Smartphone Comes With a Five-Year Warranty

An anonymous reader shares an excerpt from a ZDNet article, written by Liam Tung: [A] survey has come up with another reason why your engineers might want to quit — their fellow developers’ terrible code. Software engineers have long struggled with ‘technical debt’ created by past coding practices that might have been clever but also were undocumented and exotic. At a high level, technical debt is the price paid by supporting legacy systems rather than overhauling them or implementing a better, new system. The term can span everything from a major IT implementation, such as a core banking system that requires a decade of bug fixes, to the choice of programming language to build backend systems. In the latter case, subsequent language updates can require today’s developers to rewrite old code written by long-gone developers who wrote under different conditions and who might not have documented what they did and why they did it. That’s a big problem for companies that have millions of lines of code written in a language.

Stepsize, a firm that focuses on technical debt by tracking development issues in major code editors such as VS Code, conducted a fairly small survey of 200 software engineers to find out why they leave their jobs. The company said that 51% of engineers in its survey have considered leaving or left a job because of technical debt. Of that group who feel irked by technical debt issues, some 20% said that type of debt is the main reason they left a company. The results should be taken in context: the company’s key selling point is trying to solve technical debt challenges that organizations face, but at the same time, technical debt could be one area worthy of attention considering how hard it is to hire and retain software engineers.

Technical debt, or ‘code quality and codebase health’, was the fourth most important issue cited by respondents. Salary still trumped it, with 82% citing it as one of the “most important factors” when interviewing for a new role. The survey allowed respondents to choose several primary factors. “Technical challenges and growth opportunities” was the second priority, with 75% choosing it as the one of the most important factors. Some 68% of respondents said remote work was the most important actor, while 62% put said ‘code quality and codebase health’ was one of those prime factors. Slashdot reader ellithligraw first shared the report, adding: “Yet another reason developers are quitting… to escape the technical debt, or schlock code, or code rot. COBOL anyone?”

Read more of this story at Slashdot.

Source: Slashdot – Developers Are Quitting To Escape From Your Bad Code