Hírolvasó
Xperia 1 VII: Nem adja fel a Sony a csúcsmobilokat
Tovább kapnak támogatást az Office programok Win 10 alatt
Gépi tanulással javítana az iPhone-ok üzemidején az Apple
Security updates for Tuesday
Galaxy S25 Edge: Itt a Samsung vékony mobilja
Meredeken esnek Kínában a külföldi okostelefon-márkák eladásai
Multiple security issues in Screen
The SUSE Security Team has published an article detailing several security issues it has uncovered with GNU Screen. This includes a local root exploit when Screen is shipped setuid-root, as it is in some Linux and BSD distributions. The security team also reports problems in coordinating disclosure with the upstream Screen project.
We are not satisfied with how this coordinated disclosure developed, and we will try to be more attentive to such problematic situations early on in the future. This experience also sheds light on the overall situation of Screen upstream. It looks like it suffers from a lack of manpower and expertise, which is worrying for such a widespread open source utility. We hope this publication can help to draw attention to this and to improve this situation in the future.The article includes a table of operating systems, screen versions, and which vulnerabilities they may be affected by.
Guix project migrating to Codeberg
The Guix project has announced that it is migrating all of its Git repositories, as well as bug tracking and patch tracking, from Savannah to the Codeberg Git forge.
As a user, the main change is that your channels.scm configuration files, if they refer to the git.savannah.gnu.org URL, should be changed to refer to https://codeberg.org/guix/guix.git once migration is complete. But don't worry: guix pull will tell you if/when you need to update your config files and the old URL will remain a mirror for at least a year anyway.The motivation for the move, which is spelled out in a Guix Consensus Document (GCD), is to improve the contribution experience and improve quality assurance efforts. Migration of Git repositories should be completed by June 7, though they will continue to be mirrored on Savannah until "at least" May 2026. LWN covered Guix in February 2024.
[$] The last of YaST?
The announcement of the openSUSE Leap 16.0 beta contained something of a surprise—along with the usual set of changes and updates, it informed the community of the retirement of "the traditional YaST stack" from Leap. The YaST ("Yet another Setup Tool") installation and configuration utility has been a core part of the openSUSE distribution since its inception in 2005, and part of SUSE Linux since 1996. It will not, immediately, be removed from the openSUSE Tumbleweed rolling-release distribution, but its future is uncertain and its fate is up to the larger community to decide.
Security updates for Monday
Az adatvédelemre gyúr rá a Bluetooth 6.1
XIV. Leó tulajdonképpen az AI-nak köszönheti a nevét
Megindultak a tech cégek a kínai-amerikai megegyezés hírére
erspan(4): ERSPAN Type II collection
An early version of the code, but possibly close to being ready for further development in-tree was presented by David Gwynne (dlg@) in a message to tech@:
List: openbsd-tech Subject: erspan(4): ERSPAN Type II collection From: David Gwynne <david () gwynne ! id ! au> Date: 2025-05-12 1:27:59 we were exploring how to better let us see what's happening on access networks or specific ports on a switch at work. our switches are pretty much all cisco, which has ERSPAN. ERSPAN in it's various forms ships Ethernet packets over GRE for collection and analysis on another system. There's 3 types of ERSPAN encapsulation, but Type II seems broadly implemented.
Tényleg beperelte Mexikó a Google-t
Legombolt 1,38 milliárd dollárt Texas a Google-ről
Újratárgyalja barátságát a Microsoft és az OpenAI
A Brembo első fék féklámpa-mikrokapcsolójáról ...
Kernel prepatch 6.15-rc6
Everything still looks fairly normal - we've got a bit more commits than we did in rc5, which isn't the trend I want to see as the release progresses, but the difference isn't all that big and it feels more like just the normal noise in timing fluctuation in pull requests of fixes than any real signal.
So I won't worry about it. We've got another two weeks to go in the normal release schedule, and it still feels like everything is on track.