https://security-tracker.debian.org/tracker/CVE-2024-47176, archive
As of 10/1/24 3:52 UTC time, Trixie/Debian testing does not have a fix for the severe cupsd security vulnerability that was recently announced, despite Debian Stable and Unstable having a fix.
Debian Testing is intended for testing, and not really for production usage.
https://tracker.debian.org/pkg/cups-filters, archive
So the way Debian Unstable/Testing works is that packages go into unstable/ for a bit, and then are migrated into testing/trixie.
Issues preventing migration:
∙ ∙ Too young, only 3 of 5 days old
Basically, security vulnerabilities are not really a priority in testing, and everything waits for a bit before it updates.
I recently saw some people recommending Trixie for a "debian but not as unstable as sid and newer packages than stable", which is a pretty bad idea. Trixie/testing is not really intended for production use.
If you want newer, but still stable packages from the same repositories, then I recommend (not an exhaustive list, of course).:
- Opensuse Leap (Tumbleweed works too but secure boot was borked when I used it)
- Fedora
If you are willing to mix and match sources for packages:
- Flatpaks
- distrobox — run other distros in docker/podman containers and use apps through those
- Nix
Can get you newer packages on a more stable distros safely.
Not sure if anyone else will think it's good enough but I do.
Redhat as a company acts like a parasite on open source, producing a product that is garbage which they then charge money for their support plans. Have an issue with their offering? Fuck you. In addition to that, I absolutely beyond a doubt HATE how they do their filesystem and just willy nilly do whatever the fuck they think is best instead of following community established patterns and designs. Top it off with, who was the first to adopt systems? Redhat.
Stepping away slightly from that, have you dug into ansible's internal before? Actual fucking idiot decisions. Have an issue with tower or AAP (stupid fucking name) good luck getting it fixed. According to their documentation you can have vaulted vars in a cars file with plaintext cars. According to reality, that's causes intermittent failures and has for the past 8 years. There have been SEVERAL GitHub issues submitted but it's still not fixed.
Fuck redhat and fuck their bullshit like fedora. If I wanted to use a garbage distro, I'd at least want to use one that isn't pretending to be decent.
Ever heard of Rocky?
It's new to me, reading up on it now. Seems cool given the goals and it's the OG CentOS guy. I wasn't the biggest CentOS fan, but I liked it more than fedora for sure. It does still have similar issue like FHS violations but given it's not a redhat product I'd be more willing to use it.
More specifically, what issue do you have with their "filesystem"? Not using ansible, but i think fedora is miles ahead of arch for example.
Layout of where they put their files had (the last one I actually had to dig into a fedora system) multiple violations of the FHS. I'm very big on standards since things work well when you're not violating standards.
Obviously, people don't have to follow the FHS and redhat definitely doesn't but doing so gives more of a nice consistent experience to any technician, sys admin or sys engineer.
Mostly my reasons for avoiding Fedora as well. But if someone else ends up on Linux due to Fedora then it's still better than Windows.
I might not like it but it might, sadly, be perfect for someone else.
That's a fair way to think about it and I think I'd agree with you on it's better that someone is on Linux even fedora than Windows but for myself I'd take windows over fedora. Appreciate you engaging respectfully.