sligtly unrelated, but the portable way to execute stuff is via `/usr/bin/env`, not `/bin/bash`.

I did try fixing the path to use nixos paths, but it was still unsuccessful. Did not really check further.

? This is related to a vulnerability that was introduced to the Linux kernel in 2017.

What?

Blatant bot

So no external libraries for anything? Billions of lines of code that duplicate the same thing n-times across an organization?

And the benefit is the obscurity of "no one will know how to exploit them"?

No, thanks.

LLMs have been used to scan binary blobs for exploits already. What would be more effective is a system designed with multiple layers of security so any one exploit is largely useless.

Next: the back doors are written by the LLM!

I have had none of those issues on Fedora 44, FWIW.

If this is still the same install that you've been using since 38, you might find a clean install resolves some issues (whether or not your upgrade got botched). Also helps me get rid of software I installed that I don't use anymore, which I feel is relevant to this article. But part of why I love Silverblue so much is I don't have to worry about upgrades getting botched and fwiw as well, I haven't noticed any of those bugs on 44 across several very different machines.

I had a day 1 crashloop with KWin on the 2nd desktop, but on day 2 some package update fixed it. Honestly it isn't the first time Fedora upgrades have messed something up for me either but I do think it's more stable than the average Ubuntu release, not that I've upgraded ubuntu in like 5 yrs.

Fedora 44 here, no issues.