Post #1539641
2025-11-17 14:45 UTC
@daandemeyer
Yeah I felt the pain of a sudo-ed process not wanting to die too.
But then I wonder - were those protections there for a reason?
I've never used run0 and from a quick look at the manpage it's unclear to me whether it's all-or-nothing, or if it can be limited to only specific commands like sudo.
But if the latter, then I'd be worried that the user will be able to mess with that process using SIGSTOP, those two SIGRTs that glibc uses for its internal purposes, etc
Replies (1)
-
@daandemeyer@mastodon.social 2025-11-17 15:01
@wolf480pl Effectively it's up to the user to decide if they're OK with their application running under "run0 --empower". If you're in an environment where you don't want the user to be able to mess with the empowered session via signals, then you should not use the --empower switch.