Lines Matching refs:allowed

938 allowed types. These decorations are described in this clause.
968 indicates that the parameter is allowed to use the “null” value of the data type (see "Conditional
976 If a handle does not have this symbol, then an authorization session is not allowed.
1073 If the handle references an NV Index, then the allowed authorizations are determined by the
1327 3) If the maximum allowed number of sessions have been unmarshaled and fewer octets than
1352 Only one session is allowed for:
1427 If adminWithPolicy is CLEAR, then any type of authorization session is allowed .
1665 the value of a size parameter is larger or smaller than allowed
1684 a parameter does not have one of its allowed values
1687 …ver, the unmarshaling code is required to validate that all parameters have values that are allowed
1717 one session was used for parameter encryption of the response and that the command allowed
1750 A special case exists when the command tag parameter is not an allowed value (TPM_ST_SESSIONS or
1762 that the logic associated with dictionary attack protection is allowed to be modified when an autho…
1810 are not allowed at this time because the TPM is in DA lockout mode. The remedy
1834 NV memory is currently not available and the command is not allowed to proceed
1843 allocated. However, other implementations are allowed to assign each object a
1853 TPM2_ContextLoad()). However, the TPM implementation is allowed to use
1856 slots are previously occupied, the TPM may return this value. A TPM is allowed
1919 However, the TPM implementation is allowed to use object slots for other
2175 TPM2_Startup() commands are not allowed after it has completed successfully. If a TPM requires
3520 If symmetric specifies a block cipher, then TPM_ALG_CFB is the only allowed value for the mode fiel…
4496 hash object is larger than is allowed for the scheme
4869 inPulblic attributes are not allowed with selected parent
4885 KDF selection not allowed
5115 If both the public and private portions of an object are loaded, the object is not allowed to appea…
5313 hierarchy is turned off, or only NULL hierarchy is allowed when
6796 It is allowed that policySesion→nameHash and policySession→cpHash share the same memory
8216 implemented in the TPM. Many of these commands are only allowed if the asymmetric key is an
8236 The three types of allowed padding are:
8434 than allowed for keyHandle.
8682 larger than allowed for a TPM2B_DATA.
10488 hierarchy to use for the ticket (TPM_RH_NULL allowed)
11807 In all TPM, a buffer size of 1,024 octets is allowed.
12550 PCR extension is not allowed at the current locality
12641 // see if extend of the PCR is allowed at the locality of the command,
14837 However, this could consume a large amount of memory. To limit the memory size, the TPM is allowed …
14843 To further reduce the memory requirements for the ephemeral private keys, the TPM is allowed to use
14851 Since the TPM is allowed to restrict the number of pending ephemeral keys, the array size can be li…
15940 As long as it is no larger than allowed, the digest parameter is not required to have any specific …
16122 the value to sign is larger than allowed for the type of keyHandle
16671 The pcrHandle parameter is allowed to reference TPM_RH_NULL. If so, the input parameters are
16823 current command locality is not allowed to extend the PCR
16862 // Check if the extend operation is allowed by the current command locality
17075 current command locality is not allowed to extend the PCR
17336 etc. In the response to this command, the TPM returns the maximum number of PCR allowed for any
17342 After this command, TPM2_Shutdown() is only allowed to have a startupType equal to TPM_SU_CLEAR.
17985 The definition of TPMI_DH_PCR in Part 2 indicates that if pcrHandle is out of the allowed range for
18115 current command locality is not allowed to reset the PCR referenced
18133 // Check if the reset operation is allowed by the current command locality
20259 // NOTE: A trial policy session is not allowed to use this command.
21006 Then policySession→commandLocality is updated to indicate which localities are still allowed after
21057 the allowed localities for the policy
21624 // NV Read access check. NV index should be allowed for read. A
22586 the allowed commandCode
23462 When an object is created when the list of allowed duplication targets is known, the policy would be
23487 It is allowed that policySesion→nameHash and policySession→cpHash share the same memory
23517 approve a policyDigest that allowed duplication to a specific new parent. The authorizing entity may
24980 Any type of object and attributes combination that is allowed by TPM2_Create() may be created by th…
25190 hash object is larger than is allowed for the scheme
25324 // before anything in the template is allowed to be changed.
26222 In the reference implementation, ehProof is a non-volatile value from the RNG. It is allowed that t…
27230 Only one authorization failure is allowed for this command during a lockoutRecovery interval (set u…
27404 Only one authorization failure is allowed for this command during a lockoutRecovery interval.
27470 of lockoutAuth is allowed
28088 Because no additional data is allowed when the res ponse code is not TPM_RC_SUCCESS, the TPM
28662 No authorization sessions of any type are allowed with this command and tag is required to be
29167 No authorization sessions of any type are allowed with this command and tag is required to be
29637 No sessions of any type are allowed with
30241 // Other auth is not allowed in this command and should be filtered out
30287 No authorization sessions of any type are allowed with this command and tag is required to be
31003 octet (MSO) of the property). Any of the defined handle types is allowed
31015 allowed. Requesting handles with a handle type of TPM_HT_LOADED_SESSION will return handles
31673 TPMA_NV_AUTHREAD, or TPMA_NV_POLICYREAD is allowed as long as at least one is SET.
31675 TPMA_NV_AUTHWRITE, or TPMA_NV_POLICYWRITE is allowed as long as at least one is SET.
32215 // The index is allowed to have one of GLOBALLOCK or WRITEDEFINE SET
33052 not allowed to write to the Index referenced by nvIndex
33237 An allowed implementation would keep a counter value in NV and a resettable counter in RAM. The
33239 past the maximum allowed value (MAX_ORDERLY_COUNT), the non-volatile version of the count is
33645 not allowed to write to the Index referenced by nvIndex
33950 not allowed to write to the Index referenced by nvIndex
34271 not allowed to write to the Index referenced by nvIndex
34695 not allowed to read from the Index referenced by nvIndex
34809 Only an entity that may read an Index is allowed to lock the NV Index for read.
34976 not allowed to read from the Index referenced by nvIndex
35417 not allowed to read from the Index referenced by nvIndex
35480 inScheme is not an allowed value for the key definition