Lines Matching refs:only

94 specification only with JSON implementations that provide this number range.
117    only, e.g. limiting a user's memory use to 1G only makes sense on a specific
132    part of the user record only in the local context, and is generally not
144    section is augmented during runtime only, and never persisted to disk. The
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
164    records are inquired by a client, privileged or not. This data should only
184 manage only a subset of these sections and never include the others in
187 bother with the `signature` section. A service that only defines records in a
193 the fields included therein are only useful when executing authentication
204 section — this version is only transferred via IPC and never written to
214 UNIX user name. This field is the only mandatory field, all others are
238 to contain only the real name and no other information. This field must not
262 only for the two users that have special meaning to the OS kernel itself,
265 and such, but are only defined in container context. Finally `reserved` should
375 directory to populate a new home directory from. This is only used when a home
404 directories. Note that these booleans are only honored if the home directory
586 recovery key. The only supported recovery key type at the moment is `modhex64`,
594 the user record, and thus fields to apply on specific systems only, see below.
617 object shall only be visible to the administrator and the user themselves, and
673 has two mandatory fields: `type` indicates the type of recovery key. The only
677 the computer, not chosen by the user, and are longer. Currently, the only
694 specific systems only. This is primarily interesting for resource management
723 These two are the only two fields specific to this section. All other fields
754 All fields in the `binding` section only make sense in a local context and are
788 only acquired "on-the-fly" when requested.
834 `regular` field should be used if conceptually the user record can only be
891 is optional, and only used when cryptographic validation of user records shall
901 private key was used to make the signature, in PEM format. Currently only
908 The signatures only cover the `regular`, `perMachine` and `privileged` sections
930 channels suggest a cryptographic signature mechanism where only user records
936 channels only. Or traditional UNIX users created locally in `/etc/passwd` never
946 nor transferred across machines. It is only defined in short-lived operations,