Lines Matching refs:CLEAR

1979 CLEAR (0): what to do if bit is 0
1986 CLEAR (0): what to do if bit is 0
1998 CLEAR (0): what to do if bit is 0
3266 CLEAR(0): the command is not vendor specific
4454 CLEAR when the format is as defined in this Table 12 or when the response code is
4464 CLEAR (0): The error number is defined by a previous TPM specification. The error number is
4470 In any error number returned by a TPM, the F (bit 7) and V (bit 8) attributes shall be CLEAR
4481 CLEAR (0): The response code is defined by the TCG (a value in this specification).
4488 This attribute does not indicate a vendor-specific code unless the F attribute (bit[07]) is CLEAR.
4494 CLEAR (0): The response code indicates that the command had an error that would prevent it
4589 CLEAR (0): The error is associated with a handle or a session.
4603 If P is SET, then this field is the parameter in error. If P is CLEAR, then this field indicates the
4675 SET. Codes that are unique to Part 3 will have the F bit CLEAR but the V (version) attribute will b…
4808 a _TPM_Init and Startup(CLEAR) is required
5782 All bits SET in B are CLEAR in A. ((A&B)=0)
6030 1) Shutdown(CLEAR) followed by Startup(CLEAR)
6031 2) Startup(CLEAR) with no Shutdown()
6032 b) TPM Restart – Shutdown(STATE) followed by Startup(CLEAR)
7894 CLEAR (0): not an asymmetric algorithm
7901 CLEAR (0): not a symmetric block cipher
7908 CLEAR (0): not a hash algorithm
7915 CLEAR (0): an algorithm that is not used as an object type
7927 CLEAR (0): not a signing algorithm
7935 CLEAR (0): not an encryption/decryption algorithm
7942 CLEAR (0): not a method
7993 CLEAR (0): The hierarchy of the object may change as a result of this object or
8001 Startup(CLEAR).
8002 CLEAR (0): Saved contexts of this object may be used after a
8016 CLEAR (0): The parent of the object may change as the result of a
8026 CLEAR (0): A portion of the sensitive data, other than the authValue, was
8036 CLEAR (0): Approval of USER role actions with this object may only be done
8045 CLEAR (0): Approval of ADMIN role actions with this object may be with an
8060 CLEAR (0): The object is subject to dictionary attack protections.
8068 CLEAR (0): The object may be duplicated without an inner wrapper on the
8082 CLEAR (0): Key usage is not restricted to use on special formats.
8105 CLEAR (0): The private portion of the key may not be used to decrypt.
8112 CLEAR (0): The private portion of the key may not be used to sign.
8176 Qualified Name of the object cannot change. When CLEAR, the object’s Qualified Name may change if
8186 set to the same value in template. If fixedTPM is CLEAR in the parent, this attribute shall
8187 also be CLEAR in template.
8197 set to the same value. If fixedTPM is CLEAR in the parent, this attribute shall also be
8198 CLEAR.
8204 shall be CLEAR
8210 shall be CLEAR if both the public and sensitive portions are loaded or if fixedParent is
8211 CLEAR, otherwise may be SET or CLEAR
8230 TPM2_Startup(TPM_SU_CLEAR). If the attribute is CLEAR, then the TPM shall not invalidate the saved
8235 may be SET or CLEAR in template
8241 may be SET or CLEAR
8247 may be SET or CLEAR
8253 may be SET or CLEAR
8260 of a TPM2_Duplicate(). If this attribute is CLEAR, then this object may be the object of a
8264 may be SET or CLEAR in template
8270 may be SET or CLEAR
8276 shall be CLEAR
8282 shall be CLEAR if both the public and sensitive portions are loaded; otherwise it may be
8283 SET or CLEAR
8290 TPM2_CreatePrimary(). If CLEAR, it indicates that the sensitive part of the object (other than the
8295 the sensitive area data. If the fixedTPM attribute is CLEAR, then validation of this attribute requ…
8301 otherwise, it shall be CLEAR in the template.
8311 required to be CLEAR. A data object has type = TPM_ALG_KEYEDHASH and its sign and decrypt
8312 attributes are CLEAR.
8318 may be SET or CLEAR
8324 may be SET or CLEAR
8330 may be SET or CLEAR
8351 If this attribute is CLEAR, then then HMAC or password authorizations may not be used for USER role
8361 provide the bind value in TPM2_StartAuthSession(). However, if userWithAuth is CLEAR, then the obje…
8368 may be SET or CLEAR in template
8374 may be SET or CLEAR
8380 may be SET or CLEAR
8386 may be SET or CLEAR
8392 If CLEAR, authorization for operations that require ADMIN role may be given if the caller provides …
8403 …ribute is similar to userWithAuth but the logic is a bit different. When userWithAuth is CLEAR, the
8404 authValue may not be used for USER mode authorizations. When adminWithPolicy is CLEAR, it means
8411 may be SET or CLEAR in template
8417 may be SET or CLEAR
8423 may be SET or CLEAR
8429 may be SET or CLEAR
8439 may be SET or CLEAR in template
8445 may be SET or CLEAR
8451 may be SET or CLEAR
8457 may be SET or CLEAR
8488 If an object's parent has fixedTPM SET, and the object is duplicable (fixedParent == CLEAR), then
8489 encryptedDuplication may be SET or CLEAR in the object.
8495 If an object's parent has fixedTPM CLEAR, then the object is required to have the same setting of
8524 shall be CLEAR if fixedTPM is SET. If fixedTPM is CLEAR, then this attribute shall have
8526 case, it may be SET or CLEAR.
8532 shall be CLEAR if fixedTPM is SET. If fixedTPM is CLEAR, then this attribute shall have
8534 be SET or CLEAR.
8540 if fixedTPM is SET in the object's new parent, then this attribute may be SET or CLEAR,
8547 may be SET or CLEAR.
8556 A key with this object CLEAR may not be a parent for another object.
8560 shall be CLEAR in template if neither sign nor decrypt is SET in template.
8566 shall be CLEAR if neither sign nor decrypt is SET in the object
8572 may be SET or CLEAR
8578 shall be CLEAR
8604 decrypt and sign CLEAR).
8606 When restricted is CLEAR, there are no restrictions on the use of the private portion of the key for
8611 … with this attribute SET may be a parent for another object if restricted is SET and sign is CLEAR.
8617 may be SET or CLEAR in template
8623 may be SET or CLEAR
8629 may be SET or CLEAR
8635 may be SET or CLEAR
8647 If restricted is CLEAR, then the key may be used to sign any digest, whether generated by the TPM or
8714 CLEAR (0): In a command, this setting indicates that the TPM should close the
8719 This attribute will only be CLEAR in one response for a logical session. If the attribute
8720 is CLEAR, the context associated with the session is no longer in use and the space
8733 CLEAR (0): If audit is CLEAR, then this field is reserved but the error is
8743 CLEAR (0): If audit is CLEAR, then this field is reserved but the error is
8751 shall be CLEAR
8760 CLEAR (0): Session not used for encryption.
8764 For a password authorization, this attribute will be CLEAR in both the command and
8802 CLEAR (0): Session not used for encryption.
8803 For a password authorization, this attribute will be CLEAR in both the command and
8817 may be SET or CLEAR.
8818 CLEAR (0): Session is not used for audit.
8931 CLEAR (0): ownerAuth has not been changed since TPM2_Clear().
8939 CLEAR (0): endorsementAuth has not been changed since TPM2_Clear().
8947 CLEAR (0): lockoutAuth has not been changed since TPM2_Clear().
8956 CLEAR (0): TPM2_Clear() is enabled.
8974 CLEAR (0): The EPS was created outside of the TPM using a manufacturerspecific process.
9012 CLEAR (0): platformAuth and platformPolicy may not be used for authorizations,
9023 CLEAR (0): ownerAuth and ownerPolicy may not be used for authorizations, and
9039 CLEAR (0): endorsementAuth and endorsementPolicy may not be used for
9054 CLEAR (0): NV indices that have TPMA_PLATFORM_CREATE SET may not be
9099 CLEAR (0): TPM2_Startup(TPM_SU_CLEAR) was not preceded by a
9143 CLEAR (0): indicates that the memory used for authorization sessions is not
9152 CLEAR (0): indicates that the persistent objects and NV Index values are
9162 CLEAR (0): indicates that the TPM does not use transient-object slots when
9222 CLEAR (0): indicates that the command does not write to NV
9229 CLEAR (0): no additional changes other than indicated by the flushed attribute
9237 CLEAR (0): No context is flushed as a side effect of this command.
9254 CLEAR (0): indicates that the command is defined in a version of this
9276 CLEAR, then the TPM shall not perform an NV write as part of the command actions.
9327 context saved, but objects are not. The flushed attribute for that command shall be CLEAR.
9370 CLEAR, it indicates that the command is defined by a version of this specification.
15379 SET, TPMA_NV_WRITELOCKED may not be CLEAR except by deleting and redefining the Index. If
15380 TPMA_NV_WRITEDEFINE is CLEAR, then TPMA_NV_WRITELOCK will be CLEAR on the next
15383 CLEAR on the next TPM2_Startup(TPM_SU_CLEAR).
15399 TPMA_NV_READLOCKED, TPMA_NV_WRITTEN shall all be CLEAR in the parameter that defines the
15427 CLEAR (0): Writing of the Index data cannot be authorized with
15435 CLEAR (0): Writing of the Index data cannot be authorized with
15444 CLEAR (0): Authorizations to change the Index contents that require
15453 CLEAR (0): Authorizations to change the Index contents that require
15466 CLEAR (0): The Index is not a counter.
15474 CLEAR (0): The Index is not a bit field.
15483 CLEAR (0): Index is not a PCR.
15497 CLEAR (0): Index may be deleted with proper platform or owner
15505 CLEAR (0): Index can be written.
15513 CLEAR (0): Partial writes are allowed. This setting is required if
15522 CLEAR (0): TPM2_NV_WriteLock() does not block subsequent
15531 CLEAR (0): A write to this Index with a data size of zero does not
15560 CLEAR (0): TPM2_NV_GlobalWriteLock() has no effect on the
15568 CLEAR (0): Reading of the Index data cannot be authorized with
15576 CLEAR (0): Reading of the Index data cannot be authorized with
15584 CLEAR (0): Reading of the Index data cannot be authorized with the
15592 CLEAR (0): Reading of the Index data cannot be authorized with the
15607 CLEAR (0): Authorization failures of the Index will increment the
15618 CLEAR (0): NV Index state is required to be persistent after the
15626 SET (1): TPMA_NV_WRITTEN for the Index is CLEAR by TPM
15628 CLEAR (0): TPMA_NV_WRITTEN is not changed by TPM Restart.
15640 be CLEAR by TPM Reset.
15648 CLEAR (0): Reads of the Index are allowed if proper authorization is
15656 CLEAR (0): Index has not been written.
15664 CLEAR (0): This Index may be undefined using ownerAuth but not
15668 CLEAR when the Index is defined using ownerAuth.
15695 CLEAR (0): TPM2_NV_ReadLock() has no effect on this Index.
16400 CLEAR