“Ptrace is being restricted by default. This doesn't break strace, but if you're trying to trace an already running process, then you're going to need to change a system setting. What they're doing, which is kind of clever, is they ship scope zero, where a process can only do it to its own threads. But if you install a debugging tool that might need this functionality legitimately, it ships a linked package which sets that system setting back to one. So hopefully you won't notice it.”

Yeah, unsigned packages are going to fail unless you actually have dash dash note signature there. There's various other escape patches. There's also things coming in DNF5, per repo GPG check equals zero. If you're just using already signed repos, you're probably not going to notice. But if you're using unsigned stuff, it's going to get, you're going to have to do a little more actively to tell the system that's okay and not a security problem. A few other things like Ptrace is being restricted by default. This doesn't break S-Trace, but if you're trying to trace an already running process, then you're going to need to change a system setting. Or what they're doing, which is kind of clever, is like they start it to this scope zero, which is you can only do it to your own processes and threads. Like a process can do it to its own threads, but it can't do it to a separate process. The scope one means you can. And so they're going to ship scope zero, but then if you install anything like a debugging tool, something that might need this functionality legitimately, then it ships a linked package, which then sets that system setting back to one. So hopefully you won't notice it. You might in some esoteric use cases. That's the thing to check for.