

Yet another critical vulnerability in systemd
This is a critical vulnerability in snapd, not systemd. It sounds like it could also be exploited if something other than systemd deleted the files in /tmp/. Or if /tmp/ was not mounted.


Yet another critical vulnerability in systemd
This is a critical vulnerability in snapd, not systemd. It sounds like it could also be exploited if something other than systemd deleted the files in /tmp/. Or if /tmp/ was not mounted.


No LLM use is benign. The effects on the environment, the internet, and society are real, and that cannot be ignored.
You can make the argument that in some cases it is justified, e.g.: for scientific research.


If your home IP does not change often, you can use a dynamic DNS service. But your services will be unavailable from the time that your IP changes and the time the DNS record is updated and the cached responses expire.


Servers are all Debian. Family member’s laptops are all Debian. I used Debian on my laptops for 20 years, but when Steam Deck switched to Arch, I switched my laptop to Arch to force me to learn it. I have a file with notes of differences between Debian and Arch. Next time I buy a new laptop, I will probably go back to Debian.
Nothing in the Qualys report nor the Ubuntu page for the CVE indicate that there is something to be fixed in systemd, only that you can create systemd-tmpfiles rules that will expose the vulnerability in snapd.
What do you think systemd-tmpfiles needs to do differently?