Searched refs:privileged (Results 1 – 14 of 14) sorted by relevance
/systemd-251/docs/ |
D | GROUP_RECORD.md | 38 the `regular`, `perMachine` and `privileged` sections). 57 `privileged`/`perMachine`/`binding`/`status`/`signature`/`secret` → The 61 ## Fields in the `privileged` section 114 | `struct group` | `gr_passwd` | `privileged` | `password` | (See notes below) | 118 | `struct sgrp` | `sg_passwd` | `privileged` | `password` | (See notes below) |
|
D | USER_RECORD.md | 105 2. A number of fields are located in the `privileged` section (a sub-object of 156 except for `regular`, `privileged`, `perMachine`. Specifically, `binding`, 164 records are inquired by a client, privileged or not. This data should only 176 | privileged | yes | yes | yes | no … 198 in the LUKS2 header) a user record containing the `regular`, `privileged`, 274 `regular`, `privileged`, `perMachine` sections) was last changed. This field is 590 `privileged` → An object, which contains the fields of the `privileged` section 613 ## Fields in the `privileged` section 615 As mentioned, the `privileged` section is encoded in a sub-object of the user 616 record top-level object, in the `privileged` field. Any data included in this [all …]
|
D | USER_GROUP_API.md | 222 user record lookup should only pass the `privileged` section of user records to 224 privileged clients, for all others the section must be removed so that no 227 `privileged` section existed in the user record and was removed, and `false` if 228 no `privileged` section existed or one existed but hasn't been removed).
|
D | PASSWORD_AGENTS.md | 32 * Access to the socket is restricted to privileged users. To acquire the necessary privileges to se… 39 …` to ensure the password is asked via the agent system. Note that only privileged users may use th…
|
D | ARCHITECTURE.md | 130 orders-of-magnitude faster than `qemu`, but some tests require privileged
|
D | CGROUP_DELEGATION.md | 83 cgroup trees to less privileged processes and so on, which all are not 228 controller hierarchies. Delegation to less privileged processes is not safe 492 6. ⚡ Think twice before delegating cgroup v1 controllers to less privileged
|
D | TEMPORARY_DIRECTORIES.md | 149 `/run/` or `$XDG_RUNTIME_DIRECTORY` (the former if privileged, the latter if
|
D | PORTABLE_SERVICES.md | 76 includes system extensions otherwise sometimes called "super-privileged
|
D | ENVIRONMENT.md | 264 data when invoked privileged, or possibly only when getppid() returns 1, as
|
/systemd-251/src/hostname/ |
D | hostnamed.c | 1164 bool privileged; in method_describe() local 1185 privileged = r > 0; in method_describe() 1218 if (privileged) { in method_describe()
|
/systemd-251/src/home/ |
D | homectl.c | 1023 _cleanup_(json_variant_unrefp) JsonVariant *privileged = NULL; in apply_identity_changes() 1025 privileged = json_variant_ref(json_variant_by_key(v, "privileged")); in apply_identity_changes() 1027 r = json_variant_filter(&privileged, arg_identity_filter); in apply_identity_changes() 1031 r = json_variant_merge(&privileged, arg_identity_extra_privileged); in apply_identity_changes() 1035 if (json_variant_is_blank_object(privileged)) { in apply_identity_changes() 1040 r = json_variant_set_field(&v, "privileged", privileged); in apply_identity_changes()
|
/systemd-251/shell-completion/zsh/ |
D | _systemctl.in | 497 {-P,--privileged}'[Acquire privileges before execution]' \
|
/systemd-251/ |
D | TODO | 83 can safely put privileged stuff in. Would not be writable by the user, but 88 privileged dirs inside of unprivileged dirs, and thus containers really 93 file to move there, since it is managed by privileged code (i.e. homed) and 1766 unprivileged containers. i.e. push the truly privileged bits into machined,
|
D | NEWS | 2860 a simple mechanism to pass privileged data to services in a safe and 4972 when extracting a tarball into /tmp or /var/tmp as a privileged user, 7767 available only for privileged clients and should be helpful to watch 10300 many of PID1's privileged operations such as unit file 10774 containers is a privileged operation. 11955 * logind has gained support for facilitating privileged input 12357 * If a privileged process logs a journal message with the
|