DeviceVerificationStatus
Defined in: src/crypto-api/index.ts:947
Constructors
Section titled “Constructors”Constructor
Section titled “Constructor”new DeviceVerificationStatus(
opts):DeviceVerificationStatus
Defined in: src/crypto-api/index.ts:978
Parameters
Section titled “Parameters”Partial<DeviceVerificationStatus> & object
Returns
Section titled “Returns”DeviceVerificationStatus
Properties
Section titled “Properties”crossSigningVerified
Section titled “crossSigningVerified”
readonlycrossSigningVerified:boolean
Defined in: src/crypto-api/index.ts:961
True if this device has been verified via cross signing.
This does not take into account trustCrossSignedDevices.
localVerified
Section titled “localVerified”
readonlylocalVerified:boolean
Defined in: src/crypto-api/index.ts:971
True if the device has been marked as locally verified.
signedByOwner
Section titled “signedByOwner”
readonlysignedByOwner:boolean
Defined in: src/crypto-api/index.ts:954
True if this device has been signed by its owner (and that signature verified).
This doesn’t necessarily mean that we have verified the device, since we may not have verified the owner’s cross-signing key.
readonlytofu:boolean
Defined in: src/crypto-api/index.ts:966
TODO: tofu magic wtf does this do?
Methods
Section titled “Methods”isVerified()
Section titled “isVerified()”isVerified():
boolean
Defined in: src/crypto-api/index.ts:1003
Check if we should consider this device “verified”.
A device is “verified” if either:
- it has been manually marked as such via CryptoApi.setDeviceVerified.
- it has been cross-signed with a verified signing key, and the client has been configured to trust cross-signed devices via CryptoApi.setTrustCrossSignedDevices.
Returns
Section titled “Returns”boolean
true if this device is verified via any means.