▲ 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 9 points 4 months ago (2 children) Nah this is more systemd bloat and certainly invites criticism. Other inits aren't even commenting, let alone complying. permalink fedilink source parent hideshow 4 child comments replies: [–] amadaluzia@discuss.tchncs.de 7 points 4 months ago* (last edited 4 months ago) (1 child) Other inits aren’t even commenting, let alone complying. This would be a fair point, if systemd wasn't more than an init system. While a service manager (init system) is included, systemd is a system manager. OpenRC, runit, and other init systems do not need to comment because their only task is to mount the necessary file systems, setup the device manager, and start daemons1. systemd as a system manager not only needs to manage services, but it also needs to manage devices, logs, the hostname, etc. Does this mean systemd is not bloat? Not at all, but it is not as fat as you think it is. Your system could honestly be fatter without systemd if you try to replicate everything it does with external applications. Does this mean systemd should also be justified to add an optional field for your date of birth? I guess I would say it's weird on it's own. However, given the context, I believe they are doing what they can. permalink fedilink source parent hideshow 2 child comments replies: [–] 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 [–] Eggymatrix@sh.itjust.works 0 points 4 months ago (1 child) Other inits are not relevant, because of their own choice to not do the job correctly last time they had a chance to permalink fedilink source parent hideshow 2 child comments replies: [–] amadaluzia@discuss.tchncs.de 4 points 4 months ago* (1 child) I believe those other init systems we're in the right to, but that's only because they are JUST init systems. systemd can because it doesn't just provide an init system, it provide a suite of tools for Linux system management. Something like userdb would have to be implemented by another tool, where they could actually implement BirthDate if they so choose to (and probably should for it's continued existence). permalink fedilink source parent hideshow 2 child comments replies: [–] Eggymatrix@sh.itjust.works 2 points 4 months ago Yes, I agree. The problem is such things never appeared, so alternatives to systemd never became relevant. permalink fedilink source parent
[–] amadaluzia@discuss.tchncs.de 7 points 4 months ago* (last edited 4 months ago) (1 child) Other inits aren’t even commenting, let alone complying. This would be a fair point, if systemd wasn't more than an init system. While a service manager (init system) is included, systemd is a system manager. OpenRC, runit, and other init systems do not need to comment because their only task is to mount the necessary file systems, setup the device manager, and start daemons1. systemd as a system manager not only needs to manage services, but it also needs to manage devices, logs, the hostname, etc. Does this mean systemd is not bloat? Not at all, but it is not as fat as you think it is. Your system could honestly be fatter without systemd if you try to replicate everything it does with external applications. Does this mean systemd should also be justified to add an optional field for your date of birth? I guess I would say it's weird on it's own. However, given the context, I believe they are doing what they can. permalink fedilink source parent hideshow 2 child comments replies: [–] 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
[–] 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
[–] Eggymatrix@sh.itjust.works 0 points 4 months ago (1 child) Other inits are not relevant, because of their own choice to not do the job correctly last time they had a chance to permalink fedilink source parent hideshow 2 child comments replies: [–] amadaluzia@discuss.tchncs.de 4 points 4 months ago* (1 child) I believe those other init systems we're in the right to, but that's only because they are JUST init systems. systemd can because it doesn't just provide an init system, it provide a suite of tools for Linux system management. Something like userdb would have to be implemented by another tool, where they could actually implement BirthDate if they so choose to (and probably should for it's continued existence). permalink fedilink source parent hideshow 2 child comments replies: [–] Eggymatrix@sh.itjust.works 2 points 4 months ago Yes, I agree. The problem is such things never appeared, so alternatives to systemd never became relevant. permalink fedilink source parent
[–] amadaluzia@discuss.tchncs.de 4 points 4 months ago* (1 child) I believe those other init systems we're in the right to, but that's only because they are JUST init systems. systemd can because it doesn't just provide an init system, it provide a suite of tools for Linux system management. Something like userdb would have to be implemented by another tool, where they could actually implement BirthDate if they so choose to (and probably should for it's continued existence). permalink fedilink source parent hideshow 2 child comments replies: [–] Eggymatrix@sh.itjust.works 2 points 4 months ago Yes, I agree. The problem is such things never appeared, so alternatives to systemd never became relevant. permalink fedilink source parent
[–] Eggymatrix@sh.itjust.works 2 points 4 months ago Yes, I agree. The problem is such things never appeared, so alternatives to systemd never became relevant. permalink fedilink source parent