Agreguesi i feed

Bank of England Governor Andrew Bailey is warning that advanced "frontier" AI models could materially increase cyber risk across the global financial system by making attacks faster, cheaper, and more scalable. In a letter to G20 finance officials, he said financial firms need stronger defenses and contingency plans for simultaneous disruptions. CNBC reports: Writing in his capacity as chair of the Financial Stability Board, an international body that coordinates policy and makes recommendations to national authorities, Bailey identified the potential impact of frontier AI -- which refers to the most advanced AI models -- on cyber risk as "the most immediate concern" for the financial system. "Frontier AI may have the ability materially to alter the speed, scale and economics of cyber risk, which could undermine market confidence system-wide, especially due to highly concentrated third-party service providers," Bailey said. "Recent developments have also highlighted to me that many jurisdictions do not have the protocols in place to manage the development, release, and deployment of advanced frontier AI models, heightening risks for the financial sector and beyond," he added. [...] Financial institutions and technology providers will need to improve vulnerability management, response and recovery capabilities -- "and prepare for more severe scenarios involving simultaneous disruption across multiple firms or shared technology dependencies," Bailey said. Alongside new AI models, Bailey cited "fragilities" in sovereign debt markets, the growing use of debt by investors in equity markets and stretched asset valuations, particularly AI-related investments, as among his concerns.

Read more of this story at Slashdot.

An anonymous reader quotes a report from 9to5Mac: Today is Tim Cook's last day as Apple CEO, with John Ternus set to take over tomorrow. To mark his last day in the role, Cook penned an emotional memo to Apple employees today. In the memo sent to employees this morning and obtained by 9to5Mac, Cook reflects on his time at Apple and thanks employees for all of their work. He also says he takes "enormous comfort in handing the helm to someone as brilliant and wonderful and capable" as John Ternus. "Few people understand what it takes to build products that change the world the way John does and I could not be more excited for his leadership," Cook writes. "There is something truly special about Apple," writes Cook. "I am most proud of what an annual report could never capture. This place is proof that culture triumphs over everything. We share a belief that what we build matters, and that we have both the opportunity and the responsibility to leave the world better than we found it. That purpose is part of what makes this place extraordinary. Apple helps nurture it, but I believe it lived within each of you long before you arrived here. It is what brought you to this company and what continues to drive the work you do every day." He continues: "Together, we have created something far greater than any one of us could have imagined or accomplished alone. And that's the secret to our success. We bring out the best in each other. We lift each other up. We have made it possible to leave our 'dent in the universe,' as Steve once described it, because of who we are and what we believe, because of what we value and how we see the world. How fortunate we are. How fortunate I am..." Cook also thanked the Apple community in a post on social media, writing: "Sending lots of love to the Apple community on my last day as CEO. My title changes tomorrow, but the love I have for the Apple community never will. Thank you for being a constant source of inspiration. My gratitude is endless, and I'm excited for the next chapter!"

Read more of this story at Slashdot.

MapQuest's refusal to rename Lake Ontario as "Lake America" has sent its app surging up the charts, making it the No. 1 navigation app in the U.S. and driving "hundreds of thousands" of new downloads. In contrast, Google Maps announced on Saturday that it was complying with the Trump administration's name change. TechCrunch reports: The "OG of online mapping," as the company calls itself, announced on Thursday that it would not change the name of Lake Ontario on its maps to Lake America, despite Trump's executive order directing the U.S. Department of the Interior to update the lake's name in the U.S. geographic naming service. As a result, MapQuest's mobile app downloads soared, sending the iOS app to the No. 4 position on the U.S. App Store's Top Charts for apps (not including games) as of Monday morning on the U.S. east coast. MapQuest also reached the No. 8 position overall in the U.S. App Store across both apps and games, and it became the No. 1 Navigation app in the United States. In Canada's App Store, the app reached No. 2 overall as of Sunday evening. The 30-year-old company remarked that it received "hundreds of thousands" of new downloads since its decision to keep the name Lake Ontario in place, and saw its app's usage climb to 50 times above its normal levels. "We took the same approach we did with the Gulf of Mexico: be part of the conversation, and give people an app that keeps the names they're familiar with," said Doug Berger, general manager of MapQuest, in a statement. "Hundreds of thousands of people signaled to us this weekend that we got it right by downloading our app."

Read more of this story at Slashdot.

A massive 12TB archive of old Steam2 content has surfaced online, apparently containing nearly every version of games uploaded to Valve's servers between 2003 and 2013, including unreleased prototypes, playtest builds, and cut content. Early discoveries include deleted Portal 2 material, files tied to Half-Life 2: Episode 3, and beta builds of games like Left 4 Dead 2, CS: GO, Spore, and Dragon Age: Origins. Researchers claim much of the material was once accessible through an unsecured public API. Ars Technica reports: The reason this weekend's leaked content cuts off abruptly in 2013 is because that's when Valve updated its content distribution system from "Steam2" to the current SteamPipe system. In moving from a proprietary file distribution format to standard HTTP file trees, the new system removed various update approval bottlenecks on Valve's end and streamlined update and patch downloads so they only reflected file differentials. Publicly accessible early versions of some games released before this SteamPipe transition had been considered lost content by archivists, no longer accessible from Valve itself and living on only as local downloads on aging machines. Apparently all that content wasn't as lost as many thought, though. Longtime Valve watcher and data miner Gabe Follower (previously) wrote on social media this weekend that he had "verified that everything in Steam2 Teraleak was obtained via a publicly accessible [API] endpoint. It's Valve's fault..." Spanish-language Valve streamer and analyst Scolcer also said on social media (via machine translation) that the teraleak was "obtained from a site that was 100% accessible to the public. It was there for everyone to download. No passwords. Nothing. Hidden in plain sight, but with no protection whatsoever." What's unclear right now if that API and publicly available Steam2 server content were accessed recently or if this weekend's leak represents content that was privately archived before the 2013 server transition and is just now being made public. "It could more-so be a collection of different people that knew about it and accumulated whatever people had downloaded back then into this massive archive," said The One Epicplayer, a moderator on the Valve Cut Content (VCC) Discord, which has long followed Valve betas and leaks. "I haven't been filled in on the full details but my suspicion is that these depot [files] were downloaded a long time ago and sat in a private collection," CrazyBubba, another VCC Discord moderator, told Ars. "There were a lot of leaks a few years back and many folks hoarded files for years. ... historically there have been issues with people lording content over other members." A readme file included with the leak offers "warm n good wishes to all hoarders who had stuff from this collection" and encourages users to mirror and share it as widely as possible. On the VCC Discord, a user purporting to be the original uploader of the teraleak (who offered screenshots of a 22TB server upload log among their evidence) wrote that "getting this out really took a significant amount of effort from me and I would like it if it didn't go to waste."

Read more of this story at Slashdot.

Version:next-20260831 (linux-next) Released:2026-08-31

An anonymous reader quotes a report from the BBC: Berlin is being blackmailed by hackers who were able to compromise city systems and steal data earlier this month, its mayor has said. Kai Wegner said officials would not cave in to the ransom demand, which came on Thursday evening. He did not say how much was being sought, though Der Spiegel reports the hackers are demanding 30 bitcoin, worth around 2 million euros. Some of the German capital's online systems were forced to close down as a result of the attack, while investigators were working to understand what data had been taken. The Rhysida group, which is thought to operate from Russia and eastern Europe, and was behind a previous attack on the British Museum, has reportedly taken responsibility. It has said on its website it intends to begin auctioning the 5.79 terabytes of data it was able to steal from Berlin in seven days' time, according to news agency Reuters. [...] Officials for the city-state said an initial data leak occurred between August 7 and 12. Then, on August 14, two department networks were shut down, making applications for housing benefits and payments impossible for several days. "Berlin will not be blackmailed," Wegner said on Friday. He said state police, prosecutors and federal security services were working to investigate the suspected perpetrators "with the utmost urgency," adding that inquiries into the "content and scope of the compromised data are being pursued with great intensity."

Read more of this story at Slashdot.

I realized that deleting local copies of files early and often is better than keeping them forever.

I'm the kind of person who will work on something, share their work, and then just let the file I had linger around indefinitely. You never know, it's better to have a local copy, it can save the day. Or you keep it at hand when you're offline. And do I really need a reason to keep a copy of the file I was working on anyway? Hoarding files and keeping them forever is tempting.

The one thing I've overlook in the past is context. When I produce or get a file, I do so in a specific context. But if I want to do some cleanup later I will certainly have lost that context, or have fragments of it. I won’t know if I can delete it safely or not, so I will keep it forever. The longer a file has been around, the more difficult it becomes to delete it.

The best thing I can do in a work context is to make it not a me-problem. Whenever I get or produce a file, I make sure there is a copy of it in a company shared drive, and I delete it from my machine as soon as possible.

Throwing it over the fence is bad behavior of course, so I make sure it’s stored somewhere with as much context as possible for people who need to use it. My machine stays decluttered, and if it’s stolen I "just" lose hardware, I have a safe copy of my work data, and there is little to leak on my (encrypted) disk.

Note: this is true for documents because all versioning systems are terrible. This is not true for code thanks to git and the like.

California's age-verification bill has passed in its legislature — but with its open-source carve-out intact, reports the blog Linuxiac: Back in May, we reported that California lawmakers amended Assembly Bill 1856 to carve open-source operating systems out of the state's upcoming age verification requirements. Three months later, that exemption survived the legislative process intact, and the bill has cleared both chambers of the California Legislature... sending the measure to Engrossing and Enrolling, the final legislative preparation stage before it can be presented to Governor Gavin Newsom... For operating systems that are covered, AB 1856 builds on California's Digital Age Assurance Act, which is scheduled to take effect on January 1, 2027. Under the current text, when an operating system runs on a device and includes an account setup feature, its provider must offer an interface that asks the account holder for the birth date, age, or both, of the device's primary user during account setup. The operating system must then be capable of providing a digital age signal to covered application stores and application developers through a reasonably consistent real-time API. Instead of exposing a precise birth date, the signal identifies one of four age ranges: under 13, 13 through 15, 16 through 17, or 18 and older... Covered application stores must request the signal from the operating system and make it available to developers.

Read more of this story at Slashdot.

For a while now, the fingerprint management UI in GNOME Settings (gnome-control-center) has felt outdated. While it worked, the layout and enrollment flow hadn’t kept up with the rest of GNOME’s modern interface updates.

I am happy that during the GNOME 51 development cycle we managed to address that. Allan Day, Marco Trevisan, and myself worked on modernizing the interface. There’s still more work to do in the UI and in fprintd, but what we will ship in 51 is already a great step forward.

Historically, the fingerprint dialog in User Settings was stuck on a GTK3-style design. Even after being ported to GTK4, conceptually it remained unchanged. Beyond looking out of place alongside Libadwaita-based settings panels, it suffered from responsiveness and accessibility issues that made it difficult for some users to enroll their prints.

Screenshot of the Fingerprint Authentication dialog

The new fingerprint management dialog uses a standard boxed list displaying your enrolled fingers. From here, each enrolled finger can be removed individually.

Clicking the “Add Fingerprint” button starts the finger enrollment process. First, you choose one of the unused finger options to enroll. From there, an assistant guides you through the scanning process. As you place your finger on the reader, the UI detects the touch and provides feedback on whether it was read correctly. You continue touching the reader until enough samples have been collected (the exact number depends on your reader’s driver). Once the progress bar fills, your finger is ready for authentication.

Screenshot of a fingerprint enrollment

This is only one of the improvements that GNOME 51 is bringing. As with everything in GNOME, we will continue gathering user feedback and making iterations over time. There are already more fingerprint features in the pipeline, such as renaming enrolled fingers and verifying individual prints. Stay tuned!

A Kubernetes workload can run with more Linux capabilities than its code needs. When capability settings are missing or broad, that excess authority may remain invisible because the application still works.

Removing a Linux trace instance should end its lifetime. An open tracefs reader can currently keep using that instance after another task removes it, creating a kernel use-after-free path in the tracing subsystem.

A Linux service may need broad system-call access while it starts, then only a smaller set while it handles requests. A single policy loaded before startup often has to keep every required call available for the service's entire lifetime.