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
3272 CLEAR(0): the command is not vendor specific
4460 CLEAR when the format is as defined in this Table 12 or when the response code is
4470 CLEAR (0): The error number is defined by a previous TPM specification. The error number is
4476 In any error number returned by a TPM, the F (bit 7) and V (bit 8) attributes shall be CLEAR
4487 CLEAR (0): The response code is defined by the TCG (a value in this specification).
4494 This attribute does not indicate a vendor-specific code unless the F attribute (bit[07]) is CLEAR.
4500 CLEAR (0): The response code indicates that the command had an error that would prevent it
4595 CLEAR (0): The error is associated with a handle or a session.
4609 If P is SET, then this field is the parameter in error. If P is CLEAR, then this field indicates the
4681 SET. Codes that are unique to Part 3 will have the F bit CLEAR but the V (version) attribute will b…
4814 a _TPM_Init and Startup(CLEAR) is required
5788 All bits SET in B are CLEAR in A. ((A&B)=0)
6054 1) Shutdown(CLEAR) followed by Startup(CLEAR)
6055 2) Startup(CLEAR) with no Shutdown()
6056 b) TPM Restart – Shutdown(STATE) followed by Startup(CLEAR)
7866 CLEAR (0): not an asymmetric algorithm
7873 CLEAR (0): not a symmetric block cipher
7880 CLEAR (0): not a hash algorithm
7887 CLEAR (0): an algorithm that is not used as an object type
7899 CLEAR (0): not a signing algorithm
7907 CLEAR (0): not an encryption/decryption algorithm
7914 CLEAR (0): not a method
7965 CLEAR (0): The hierarchy of the object may change as a result of this object or
7973 Startup(CLEAR).
7974 CLEAR (0): Saved contexts of this object may be used after a
7988 CLEAR (0): The parent of the object may change as the result of a
7998 CLEAR (0): A portion of the sensitive data, other than the authValue, was
8008 CLEAR (0): Approval of USER role actions with this object may only be done
8017 CLEAR (0): Approval of ADMIN role actions with this object may be with an
8032 CLEAR (0): The object is subject to dictionary attack protections.
8040 CLEAR (0): The object may be duplicated without an inner wrapper on the
8054 CLEAR (0): Key usage is not restricted to use on special formats.
8077 CLEAR (0): The private portion of the key may not be used to decrypt.
8084 CLEAR (0): The private portion of the key may not be used to sign.
8148 Qualified Name of the object cannot change. When CLEAR, the object’s Qualified Name may change if
8158 set to the same value in template. If fixedTPM is CLEAR in the parent, this attribute shall
8159 also be CLEAR in template.
8169 set to the same value. If fixedTPM is CLEAR in the parent, this attribute shall also be
8170 CLEAR.
8176 shall be CLEAR
8182 shall be CLEAR if both the public and sensitive portions are loaded or if fixedParent is
8183 CLEAR, otherwise may be SET or CLEAR
8202 TPM2_Startup(TPM_SU_CLEAR). If the attribute is CLEAR, then the TPM shall not invalidate the saved
8207 may be SET or CLEAR in template
8213 may be SET or CLEAR
8219 may be SET or CLEAR
8225 may be SET or CLEAR
8232 of a TPM2_Duplicate(). If this attribute is CLEAR, then this object may be the object of a
8236 may be SET or CLEAR in template
8242 may be SET or CLEAR
8248 shall be CLEAR
8254 shall be CLEAR if both the public and sensitive portions are loaded; otherwise it may be
8255 SET or CLEAR
8262 TPM2_CreatePrimary(). If CLEAR, it indicates that the sensitive part of the object (other than the
8267 the sensitive area data. If the fixedTPM attribute is CLEAR, then validation of this attribute requ…
8273 otherwise, it shall be CLEAR in the template.
8283 required to be CLEAR. A data object has type = TPM_ALG_KEYEDHASH and its sign and decrypt
8284 attributes are CLEAR.
8290 may be SET or CLEAR
8296 may be SET or CLEAR
8302 may be SET or CLEAR
8323 If this attribute is CLEAR, then then HMAC or password authorizations may not be used for USER role
8333 provide the bind value in TPM2_StartAuthSession(). However, if userWithAuth is CLEAR, then the obje…
8340 may be SET or CLEAR in template
8346 may be SET or CLEAR
8352 may be SET or CLEAR
8358 may be SET or CLEAR
8364 If CLEAR, authorization for operations that require ADMIN role may be given if the caller provides …
8375 …ribute is similar to userWithAuth but the logic is a bit different. When userWithAuth is CLEAR, the
8376 authValue may not be used for USER mode authorizations. When adminWithPolicy is CLEAR, it means
8383 may be SET or CLEAR in template
8389 may be SET or CLEAR
8395 may be SET or CLEAR
8401 may be SET or CLEAR
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
8460 If an object's parent has fixedTPM SET, and the object is duplicable (fixedParent == CLEAR), then
8461 encryptedDuplication may be SET or CLEAR in the object.
8467 If an object's parent has fixedTPM CLEAR, then the object is required to have the same setting of
8496 shall be CLEAR if fixedTPM is SET. If fixedTPM is CLEAR, then this attribute shall have
8498 case, it may be SET or CLEAR.
8504 shall be CLEAR if fixedTPM is SET. If fixedTPM is CLEAR, then this attribute shall have
8506 be SET or CLEAR.
8512 if fixedTPM is SET in the object's new parent, then this attribute may be SET or CLEAR,
8519 may be SET or CLEAR.
8528 A key with this object CLEAR may not be a parent for another object.
8532 shall be CLEAR in template if neither sign nor decrypt is SET in template.
8538 shall be CLEAR if neither sign nor decrypt is SET in the object
8544 may be SET or CLEAR
8550 shall be CLEAR
8576 decrypt and sign CLEAR).
8578 When restricted is CLEAR, there are no restrictions on the use of the private portion of the key for
8583 … with this attribute SET may be a parent for another object if restricted is SET and sign is CLEAR.
8589 may be SET or CLEAR in template
8595 may be SET or CLEAR
8601 may be SET or CLEAR
8607 may be SET or CLEAR
8619 If restricted is CLEAR, then the key may be used to sign any digest, whether generated by the TPM or
8686 CLEAR (0): In a command, this setting indicates that the TPM should close the
8691 This attribute will only be CLEAR in one response for a logical session. If the attribute
8692 is CLEAR, the context associated with the session is no longer in use and the space
8705 CLEAR (0): If audit is CLEAR, then this field is reserved but the error is
8715 CLEAR (0): If audit is CLEAR, then this field is reserved but the error is
8723 shall be CLEAR
8732 CLEAR (0): Session not used for encryption.
8736 For a password authorization, this attribute will be CLEAR in both the command and
8774 CLEAR (0): Session not used for encryption.
8775 For a password authorization, this attribute will be CLEAR in both the command and
8789 may be SET or CLEAR.
8790 CLEAR (0): Session is not used for audit.
8903 CLEAR (0): ownerAuth has not been changed since TPM2_Clear().
8911 CLEAR (0): endorsementAuth has not been changed since TPM2_Clear().
8919 CLEAR (0): lockoutAuth has not been changed since TPM2_Clear().
8928 CLEAR (0): TPM2_Clear() is enabled.
8946 CLEAR (0): The EPS was created outside of the TPM using a manufacturerspecific process.
8984 CLEAR (0): platformAuth and platformPolicy may not be used for authorizations,
8995 CLEAR (0): ownerAuth and ownerPolicy may not be used for authorizations, and
9011 CLEAR (0): endorsementAuth and endorsementPolicy may not be used for
9026 CLEAR (0): NV indices that have TPMA_PLATFORM_CREATE SET may not be
9071 CLEAR (0): TPM2_Startup(TPM_SU_CLEAR) was not preceded by a
9115 CLEAR (0): indicates that the memory used for authorization sessions is not
9124 CLEAR (0): indicates that the persistent objects and NV Index values are
9134 CLEAR (0): indicates that the TPM does not use transient-object slots when
9194 CLEAR (0): indicates that the command does not write to NV
9201 CLEAR (0): no additional changes other than indicated by the flushed attribute
9209 CLEAR (0): No context is flushed as a side effect of this command.
9226 CLEAR (0): indicates that the command is defined in a version of this
9248 CLEAR, then the TPM shall not perform an NV write as part of the command actions.
9299 context saved, but objects are not. The flushed attribute for that command shall be CLEAR.
9342 CLEAR, it indicates that the command is defined by a version of this specification.
14645 shall be CLEAR and scheme shall be
15390 SET, TPMA_NV_WRITELOCKED may not be CLEAR except by deleting and redefining the Index. If
15391 TPMA_NV_WRITEDEFINE is CLEAR, then TPMA_NV_WRITELOCK will be CLEAR on the next
15394 CLEAR on the next TPM2_Startup(TPM_SU_CLEAR).
15410 TPMA_NV_READLOCKED, TPMA_NV_WRITTEN shall all be CLEAR in the parameter that defines the
15438 CLEAR (0): Writing of the Index data cannot be authorized with
15446 CLEAR (0): Writing of the Index data cannot be authorized with
15455 CLEAR (0): Authorizations to change the Index contents that require
15464 CLEAR (0): Authorizations to change the Index contents that require
15477 CLEAR (0): The Index is not a counter.
15485 CLEAR (0): The Index is not a bit field.
15494 CLEAR (0): Index is not a PCR.
15508 CLEAR (0): Index may be deleted with proper platform or owner
15516 CLEAR (0): Index can be written.
15524 CLEAR (0): Partial writes are allowed. This setting is required if
15533 CLEAR (0): TPM2_NV_WriteLock() does not block subsequent
15542 CLEAR (0): A write to this Index with a data size of zero does not
15571 CLEAR (0): TPM2_NV_GlobalWriteLock() has no effect on the
15579 CLEAR (0): Reading of the Index data cannot be authorized with
15587 CLEAR (0): Reading of the Index data cannot be authorized with
15595 CLEAR (0): Reading of the Index data cannot be authorized with the
15603 CLEAR (0): Reading of the Index data cannot be authorized with the
15618 CLEAR (0): Authorization failures of the Index will increment the
15629 CLEAR (0): NV Index state is required to be persistent after the
15637 SET (1): TPMA_NV_WRITTEN for the Index is CLEAR by TPM
15639 CLEAR (0): TPMA_NV_WRITTEN is not changed by TPM Restart.
15651 be CLEAR by TPM Reset.
15659 CLEAR (0): Reads of the Index are allowed if proper authorization is
15667 CLEAR (0): Index has not been written.
15675 CLEAR (0): This Index may be undefined using ownerAuth but not
15679 CLEAR when the Index is defined using ownerAuth.
15706 CLEAR (0): TPM2_NV_ReadLock() has no effect on this Index.
16417 CLEAR