You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
System information exposed in various proc files such as cmdline, kallsyms, ... can contain sensitive information. A lot of programs work w/o them.
Describe the solution you'd like
Mount proc with subset=pid. On older kernels were subset=pid isn't supported we should ignore it if it was requested in a profile an proceed without it; if it was requested on the cli, we should harderror.
This need to be opt-in so suggestions for the command name are welcome (for crabjail I currently use the bulky fs._proc-exposes-system-information to turn it off and --mount-proc-subset=pid in crablock to turn it on, systemd uses ProcSubset=pid to turn it on).
Describe alternatives you've considered
We have disable-proc.inc, but enumerating badness does not work as good as subset=pid does.
Also some programs fail on EACCES but have fallback for ENOENT.
Downside: subset=pid is all or nothing. You can not mkdir/mknod in proc and bind something on it.
While it would be a nice to have, it us not very useful because of the unshared pid namespace. So you need processes with different uids running in the sandbox.
Is your feature request related to a problem? Please describe.
System information exposed in various proc files such as
cmdline
,kallsyms
, ... can contain sensitive information. A lot of programs work w/o them.Describe the solution you'd like
Mount proc with
subset=pid
. On older kernels weresubset=pid
isn't supported we should ignore it if it was requested in a profile an proceed without it; if it was requested on the cli, we should harderror.This need to be opt-in so suggestions for the command name are welcome (for crabjail I currently use the bulky
fs._proc-exposes-system-information
to turn it off and--mount-proc-subset=pid
in crablock to turn it on, systemd usesProcSubset=pid
to turn it on).Describe alternatives you've considered
We have
disable-proc.inc
, but enumerating badness does not work as good assubset=pid
does.Also some programs fail on
EACCES
but have fallback forENOENT
.Downside:
subset=pid
is all or nothing. You can notmkdir
/mknod
in proc and bind something on it.Additional context
Previous discussions:
The text was updated successfully, but these errors were encountered: