setpriv

Clear supplementary groups.

Dump the current privilege state. This option can be specified more than once to show extra, mostly useless, information. Incompatible with all other options.

Preserve supplementary groups. Only useful in conjunction with --rgid, --egid, or --regid.

Initialize supplementary groups using initgroups3. Only useful in conjunction with --ruid or --reuid.

List all known capabilities. This option must be specified alone.

Set the no_new_privs bit. With this bit set, execve(2) will not grant new privileges. For example, the set-user-ID and set-group-ID bits as well as file capabilities will be disabled. (Executing binaries with these bits set will still work, but they will not gain privileges. Certain LSMs, especially AppArmor, may result in failures to execute certain programs.) This bit is inherited by child processes and cannot be unset. See prctl(2) and Documentation/prctl/no_new_privs.txt in the Linux kernel source. The no_new_privs bit is supported since Linux 3.5.

Set the real, effective, or both GIDs. The gid argument can be given as a textual group name. For safety, you must specify one of --clear-groups, --groups, --keep-groups, or --init-groups if you set any primary gid.

Set the real, effective, or both UIDs. The uid argument can be given as a textual login name. Setting a uid or gid does not change capabilities, although the exec call at the end might change capabilities. This means that, if you are root, you probably want to do something like: setpriv --reuid=1000 --regid=1000 --inh-caps=-all

Keep, clear or set the parent death signal. Some LSMs, most notably SELinux and AppArmor, clear the signal when the process' credentials change. Using --pdeathsig keep will restore the parent death signal after changing credentials to remedy that situation.

When Yama’s restricted ptrace mode is in effect (that is, when /proc/sys/kernel/yama/ptrace_scope is set to 1), allow being traced via ptrace(2) by the process with the specified PID, or any process, or no process. See PR_SET_PTRACER(2const). (Note that this is not inherited by child processes, though it is preserved across execve(2).) This option has no effect when Yama is not enabled or is in a mode other than restricted ptrace.

Request a particular SELinux transition (using a transition on exec, not dyntrans). This will fail and cause setpriv to abort if SELinux is not in use, and the transition may be ignored or cause execve(2) to fail at SELinux’s whim. (In particular, this is unlikely to work in conjunction with no_new_privs.) This is similar to runcon(1).

Request a particular AppArmor profile (using a transition on exec). This will fail and cause setpriv to abort if AppArmor is not in use, and the transition may be ignored or cause execve(2) to fail at AppArmor’s whim.

Enable landlock restrictions for a specific set of system accesses. To allow specific subgroups of accesses use --landlock-rule. Block all filesystem access: setpriv --landlock-access fs Block all file deletions and directory creations: setpriv --landlock-access fs:remove-file,make-dir For a complete set of supported access categories use setpriv --help.

Allow one specific access from the categories blocked by --landlock-access. The syntax is as follows: --landlock-rule $ruletype:$access:$rulearg For example grant file read access to everything under /boot: --landlock-rule path-beneath:read-file:/boot

Load raw BPF seccomp filter code from a file. Filters can for example be created with enosys.

Clears all the environment variables except TERM; initializes the environment variables HOME, SHELL, USER, LOGNAME according to the user’s passwd entry; sets PATH to /usr/local/bin:/bin:/usr/bin for a regular user and to /usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin for root. The environment variable PATH may be different on systems where /bin and /sbin are merged into /usr. The environment variable SHELL defaults to /bin/sh if none is given in the user’s passwd entry.

Display help text and exit.

Display version and exit.