▲ 485 ▼ Systemd preparing to comply with age verification laws (github.com) submitted 4 months ago* (last edited 4 months ago) by skyline2@lemmy.dbzer0.com to c/linux@lemmy.ml 276 comments fedilink hide all child comments Fork time? Maybe all the anti-systemd zealots were right all along... Edit: To address whether it is likely that this change will affect users: Gnome is planning a stronger dependence on userdb, the part of systemd where this change is being implemented. https://blogs.gnome.org/adrianvovk/2025/06/10/gnome-systemd-dependencies/ Final Edit: The PR has been merged into main.
[–] Internet@lemmy.dbzer0.com 2 points 4 months ago (1 child) Your system could honestly be fatter without systemd if you try to replicate everything it does with external applications. Maybe so, but systemd's bloated feature creep still leads to security vulnerabilities. Another systemd root access exploit was just discovered a couple of days ago. permalink fedilink source parent hideshow 2 child comments replies: [–] amadaluzia@discuss.tchncs.de 2 points 4 months ago* (1 child) Unfortunate. However, it seems that is snapd's fault. Here's the important part from the article: Ubuntu automatically deletes old files from the /tmp directory after a certain number of days. During this cleanup, an important directory used by snap-confine may get removed. Ubuntu configured systemd-tmpfiles to clean out /tmp after some days. That's why the issue is only present in Ubuntu systems. Therefore, systemd was doing it's job, and it just so happened to create the perfect conditions for a vulnerability in Ubuntu. permalink fedilink source parent hideshow 2 child comments replies: [–] Internet@lemmy.dbzer0.com 1 point 4 months ago That is a fair point, actually. If there were a theoretical systemd-free Ubuntu it may just tell something else like tmpreaper to clean on the same schedule and create the same vulnerability. permalink fedilink source parent
[–] amadaluzia@discuss.tchncs.de 2 points 4 months ago* (1 child) Unfortunate. However, it seems that is snapd's fault. Here's the important part from the article: Ubuntu automatically deletes old files from the /tmp directory after a certain number of days. During this cleanup, an important directory used by snap-confine may get removed. Ubuntu configured systemd-tmpfiles to clean out /tmp after some days. That's why the issue is only present in Ubuntu systems. Therefore, systemd was doing it's job, and it just so happened to create the perfect conditions for a vulnerability in Ubuntu. permalink fedilink source parent hideshow 2 child comments replies: [–] Internet@lemmy.dbzer0.com 1 point 4 months ago That is a fair point, actually. If there were a theoretical systemd-free Ubuntu it may just tell something else like tmpreaper to clean on the same schedule and create the same vulnerability. permalink fedilink source parent
[–] Internet@lemmy.dbzer0.com 1 point 4 months ago That is a fair point, actually. If there were a theoretical systemd-free Ubuntu it may just tell something else like tmpreaper to clean on the same schedule and create the same vulnerability. permalink fedilink source parent