Lines Matching refs:which

88 popular in the web communities, which hopefully should make it easy to link
119    array comes with a `matchMachineId` or `matchHostname` field which indicate
120    which systems to apply the listed settings to. Note that many fields
126    user record; an intermediary object is inserted which is keyed by the
130    necessarily on others, and which are managed automatically by some user
322 which is then inherited by all the user's processes, see
331 values, which is then inherited by all the user's processes, see
342 the UNIX epoch (1970) before which the record should be considered invalid for
345 `notAfterUSec` → Similar, but indicates the point in time *after* which logins
447 required that all groups listed exist in all contexts: any entry for which no
522 timer interval (in µs) within which to count authentication attempts. When the
590 `privileged` → An object, which contains the fields of the `privileged` section
593 `perMachine` → An array of objects, which contain the `perMachine` section of
606 `signature` → An array of objects, which contain cryptographic signatures of
610 `secret` → An object, which contains the fields of the `secret` section of the
619 takes the role of the `/etc/shadow` records for each user, which has similarly
660 the FIDO2 token, which will HMAC hash the salt with its internal secret key and
678 supported recovery key format is `modhex64`, which consists of 64
703 which case all the object's setting should be applied. If the same option is
762 machine ID the binding is intended for, which point to an object with the
772 updated to prefer `subvolume`, which however doesn't change the actual storage
773 used already which is pinned in the `binding` section).
792 which points to the object with the fields defined here. The following fields
816 derived from the underlying data storage, and indicate in which range the home
817 directory may be re-sized in, i.e. in which sensible range the `diskSize` value
832 in which `state` lives, see above. Note that this field also exists on the
833 top-level object (i.e. in the `regular` section), which it overrides. The
840 by a public key for which the private key is available locally. This means that
915 essential to restrict carefully which users may gain access to a system and
916 which ones shall not. A minimal level of trust must be established between
926 (which may be done by the various fields of the user record) is security
1104 file. This version lacks the `binding` and `status` sections which are used for