RSS 생중계
Samsung Acquires Masimo's Audio Business For $350 Million
Read more of this story at Slashdot.
Home Assistant 2025.5 released
Trump Will Rescind Biden-Era AI Chip Export Curbs
Read more of this story at Slashdot.
Apple's Eddy Cue: 'You May Not Need an iPhone 10 Years From Now'
Read more of this story at Slashdot.
VMware Perpetual License Holders Receive Cease-And-Desist Letters From Broadcom
Read more of this story at Slashdot.
Curl Battles Wave of AI-Generated False Vulnerability Reports
Read more of this story at Slashdot.
Seagate Working To Develop a 100TB Hard Drive By 2030
Read more of this story at Slashdot.
[$] Hash table memory usage and a BPF interpreter bug
Anton Protopopov led a short discussion at the 2025 Linux Storage, Filesystem, Memory-Management, and BPF Summit about amount of memory used by hash tables in BPF programs. He thinks that the current memory layout is inefficient, and wants to split the structure that holds table entries into two variants for different kinds of maps. When that proposal proved uncontroversial, he also took the chance to talk about a bug in BPF's call instruction.
Apple Working To Move To AI Search in Browser Amid Google Fallout
Read more of this story at Slashdot.
DEA Ends Body Camera Program
Read more of this story at Slashdot.
AI Chatbots Are 'Juicing Engagement' Instead of Being Useful, Instagram Co-founder Warns
Read more of this story at Slashdot.
Uber Says Waymo Autonomous Vehicles Outperforming 99% of Human Drivers in Austin
Read more of this story at Slashdot.
[$] Debian's AWKward essential set
The Debian project has the concept of essential packages, which provide the bare minimum functionality considered absolutely necessary (or "essential") for a system to function. Packages tagged as essential, and the packages that are required by the set of essential packages, are always installed as part of a Debian system. However, Debian's packaging rules do not require developers to explicitly declare dependencies on that set of packages (the essential set) but they can simply rely on the fact that those will always be present. That means that changing the essential set, as the project may wish to do occasionally, is more complicated than it should be. This came to light recently when a Debian developer asked what might be required to remove mawk to slim down the project's container images.
IBM CEO Says AI Has Replaced Hundreds of Workers But Created New Programming, Sales Jobs
Read more of this story at Slashdot.
Deepin Desktop removed from openSUSE
The SUSE Security Team has announced the removal of the Deepin Desktop from openSUSE due to violations of the project's packaging policy.
The discovery of the bypass of the security whitelistings via the deepin-feature-enable package marks a turning point in our assessment of Deepin. We don't believe that the openSUSE Deepin packager acted with bad intent when he implemented the "license agreement" dialog to bypass our whitelisting restrictions. The dialog itself makes the security concerns we have transparent, so this does not happen in a sneaky way, at least not towards users. It was not discussed with us, however, and it violates openSUSE packaging policies. Beyond the security aspect, this also affects general packaging quality assurance: the D-Bus configuration files and Polkit policies installed by the deepin-feature-enable package are unknown to the package manager and won't be cleaned up upon package removal, for example. Such bypasses are not deemed acceptable by us.
The combination of these factors led us to the decision to remove the Deepin desktop completely from openSUSE Tumbleweed and from the future Leap 16.0 release. In openSUSE Leap 15.6 we will remove the offending deepin-feature-enable package only. It is a difficult decision given that the Deepin desktop has a considerable number of users. We firmly believe the Deepin packaging and security assessment in openSUSE needs a reboot, however, ideally involving new people that can help get the Deepin packages into shape, establish a relationship with Deepin upstream and keep an eye on bugfixes, thus avoiding fruitless follow-up reviews that just waste our time. In such a new setup we would be willing to have a look at all the sensitive Deepin components again one by one.
The announcement goes into detail about the bypass of openSUSE packaging policy and the history of security reviews of Deepin components. It also offers guidance on continuing to use Deepin Desktop on openSUSE.
Security updates for Wednesday
FTC Bans Hidden Fees For Live Events and Short-Term Rentals
Read more of this story at Slashdot.
Scientists Identify New Mutation That Enables Three-Hour Sleepers
Read more of this story at Slashdot.
Pentagon Targets Open Source Security Risks in Software Procurement Overhaul
Read more of this story at Slashdot.
The state of SSL stacks
OpenSSL 3.0 performs significantly worse than alternative SSL libraries, forcing organizations to provision more hardware just to maintain existing throughput. This raises important questions about performance, energy efficiency, and operational costs.
Examining alternatives—BoringSSL, LibreSSL, WolfSSL, and AWS-LC—reveals a landscape of trade-offs. Each offers different approaches to API compatibility, performance optimization, and QUIC support. For developers navigating the modern SSL ecosystem, understanding these trade-offs is crucial for optimizing performance, maintaining compatibility, and future-proofing their infrastructure.
페이지
