News for hackers. Stuff that matters.
Re:SELinux is unmanageable; just turn it off if it gets in y... by dale_glass on Wednesday April 27, 2022 @10:07AM (#31180075)
You said it yourself. LD_LIBRARY_PATH, and a myriad other knobs.

Think of all the stuff you can do: mess with filehandles, signal handlers, chroot, resource limits, seccomp, capabilities, program arguments... and more appear over time. You can't defend yourself from things that didn't exist at the time the code was written.

Polkit recently got exploited this way: https://blog.qualys.com/vulnerabilities-threat-research/2022...

Putting it on a socket is a good way to make sure the client has no control over the environment.

Re:SELinux is unmanageable; just turn it off if it gets in y... by Asooka on Wednesday April 27, 2022 @07:27PM (#31187084)
Yeah but that means we need to have a way of securely running binaries, not move a simple program to a service. Something like taking a snapshot of the system at various stages during init and have the binary start in a known context. This would also help a lot for desktop users - many programs need to start in a specific environment and having the option to configure per-user per-program launch environment would help a lot.