Conversation

Replying to
Process namespaces and hidepid both place restrictions on processes seeing each other, as can security modules. Unsure if that's what they're referring to and don't feel like trying to find that in a video.
1
1
Replying to
I'd understand that from normal users but root on Linux should show all pids (or have an option to show them). Yeah, need more info on this to understand fully. Watching video now but don't really want it scan back to find it either.
2
1
Replying to
Unconstrained root in the top-level namespace can see all the processes. There isn't necessarily any actual root on a system after early boot since root can restrict itself with MAC/MLS via security modules, or could set up namespaces and enter those without staying in top level.
2
2
Replying to and
I think init will always be in the top-level process namespace but there's no reason it can't spawn everything in namespaces below it. You can check if you're in the top-level namespace and then you know you probably aren't seeing everything.
2
2
Replying to and
There are a lot of variables and for example on Android, the Unix permission model is barely even relevant anymore for most things despite still being used as a basic layer since the SELinux MAC/MLS policies are so much stricter and finer grained so not that much falls through.
1
2