Lines Matching refs:used

86 JSON is nicely extensible and widely used. In particular it's easy to
146    resource usage (for example: currently used disk space of the user), that
152    reduced version of the user record. This is used to ensure that only user
158    covered by the signature. This section is optional, and is only used when
197 purposes. Inside the home directories (and if the LUKS2 backend is used, also
205 disk. Finally the `secret` section is used during authentication operations via
239 contain control characters (such as `\n`) or colons (`:`), since those are used
261 similar) this should be `system`. The `intrinsic` disposition should be used
263 i.e. the `root` and `nobody` users. The `container` string should be used for
264 users that are used by an OS container, and hence will show up in `ps` listings
266 be used for any users outside of these use-cases. Note that this property is
275 used when comparing two records of the same user to identify the newer one, and
276 is used for example for automatic updating of user records, where appropriate.
359 mounted from a Windows File Share. The five latter types are primarily used by
360 `systemd-homed` when managing home directories, but may be used if other
361 managers are used too. If this is not set, `classic` is the implied default.
375 directory to populate a new home directory from. This is only used when a home
409 use. This is generally useful, but particularly when `cifs` is used as storage
414 useful when `cifs` is used as storage mechanism for the user's home directory,
420 the top-level directory of the CIFS share is used.
427 storage is used, this refers to the loopback file or block device node to store
452 when the storage mechanism used is `luks` as a file system to use inside the
457 relevant when the storage mechanism used is `luks`.
461 relevant when the storage mechanism used is `luks`.
465 primarily relevant when the storage mechanism used is `luks`.
467 `luksDiscard` → A boolean. If true and `luks` storage is used, controls whether
468 the loopback block devices, LUKS and the file system on top shall be used in
470 storage. If false and `luks` storage is used turns this behavior off. In
494 time cost for the PBKDF operation, when the LUKS storage mechanism is used, in
498 memory cost for the PBKDF operation, when LUKS storage is used, in bytes.
501 required parallel threads for the PBKDF operation, when LUKS storage is used.
507 (as dictated by used disk space and file system constraints) on logout.
518 used for this.
573 associated with the user and may be used for authentication. The URI is used to
574 search for an X.509 certificate and associated private key that may be used to
575 decrypt an encrypted secret key that is used to unlock the user's account (see
578 private key found with it it is used.
581 credential ID that shall be used for authentication with FIDO2 devices that
646 Base64-encoded decrypted key may also be used to unlock further resources
662 used as string password for the further layers of the stack. The
695 properties as they tend to require a per-system focus, however they may be used
700 should be used. Then this array should be iterated in order, and the various
719 object are honored. If both `matchHostname` and `matchMachineId` are used
724 that may be used in this section are identical to the equally named ones in the
747 record, that bind it to the local system. These fields are generally used by a
773 used already which is pinned in the `binding` section).
795 `diskUsage` → An unsigned 64bit integer. The currently used disk space of the
799 directory/subvolume/fscrypt storage this is the current disk space used as
804 reported by `diskSize` and the used already as reported in `diskFree`, but
834 `regular` field should be used if conceptually the user record can only be
874 determined the home directory is in internal built-in media. (This is used by
891 is optional, and only used when cryptographic validation of user records shall
892 be used. Specifically, all user records managed by `systemd-homed.service` will
901 private key was used to make the signature, in PEM format. Currently only
1104 file. This version lacks the `binding` and `status` sections which are used for