Interface CryptoApi

Public interface to the cryptography parts of the js-sdk

Remarks

Currently, this is a work-in-progress. In time, more methods will be added here.

interface CryptoApi {
    globalBlacklistUnverifiedDevices: boolean;
    bootstrapCrossSigning(opts): Promise<void>;
    bootstrapSecretStorage(opts): Promise<void>;
    checkKeyBackupAndEnable(): Promise<null | KeyBackupCheck>;
    createRecoveryKeyFromPassphrase(password?): Promise<GeneratedSecretStorageKey>;
    crossSignDevice(deviceId): Promise<void>;
    deleteKeyBackupVersion(version): Promise<void>;
    exportRoomKeys(): Promise<IMegolmSessionData[]>;
    exportRoomKeysAsJson(): Promise<string>;
    findVerificationRequestDMInProgress(roomId): undefined | Crypto.VerificationRequest;
    findVerificationRequestDMInProgress(roomId, userId?): undefined | Crypto.VerificationRequest;
    forceDiscardSession(roomId): Promise<void>;
    getActiveSessionBackupVersion(): Promise<null | string>;
    getCrossSigningKeyId(type?): Promise<null | string>;
    getCrossSigningStatus(): Promise<CrossSigningStatus>;
    getDeviceVerificationStatus(userId, deviceId): Promise<null | DeviceVerificationStatus>;
    getEncryptionInfoForEvent(event): Promise<null | EventEncryptionInfo>;
    getOwnDeviceKeys(): Promise<OwnDeviceKeys>;
    getSessionBackupPrivateKey(): Promise<null | Uint8Array>;
    getTrustCrossSignedDevices(): boolean;
    getUserDeviceInfo(userIds, downloadUncached?): Promise<DeviceMap>;
    getUserVerificationStatus(userId): Promise<UserVerificationStatus>;
    getVerificationRequestsToDeviceInProgress(userId): Crypto.VerificationRequest[];
    getVersion(): string;
    importRoomKeys(keys, opts?): Promise<void>;
    importRoomKeysAsJson(keys, opts?): Promise<void>;
    isCrossSigningReady(): Promise<boolean>;
    isEncryptionEnabledInRoom(roomId): Promise<boolean>;
    isKeyBackupTrusted(info): Promise<BackupTrustInfo>;
    isSecretStorageReady(): Promise<boolean>;
    prepareToEncrypt(room): void;
    requestDeviceVerification(userId, deviceId): Promise<Crypto.VerificationRequest>;
    requestOwnUserVerification(): Promise<Crypto.VerificationRequest>;
    requestVerificationDM(userId, roomId): Promise<Crypto.VerificationRequest>;
    resetKeyBackup(): Promise<void>;
    setDeviceVerified(userId, deviceId, verified?): Promise<void>;
    setTrustCrossSignedDevices(val): void;
    storeSessionBackupPrivateKey(key): Promise<void>;
    storeSessionBackupPrivateKey(key, version): Promise<void>;
    userHasCrossSigningKeys(userId?, downloadUncached?): Promise<boolean>;
}

Hierarchy (view full)

Properties

globalBlacklistUnverifiedDevices

Methods

bootstrapCrossSigning bootstrapSecretStorage checkKeyBackupAndEnable createRecoveryKeyFromPassphrase crossSignDevice deleteKeyBackupVersion exportRoomKeys exportRoomKeysAsJson findVerificationRequestDMInProgress forceDiscardSession getActiveSessionBackupVersion getCrossSigningKeyId getCrossSigningStatus getDeviceVerificationStatus getEncryptionInfoForEvent getOwnDeviceKeys getSessionBackupPrivateKey getTrustCrossSignedDevices getUserDeviceInfo getUserVerificationStatus getVerificationRequestsToDeviceInProgress getVersion importRoomKeys importRoomKeysAsJson isCrossSigningReady isEncryptionEnabledInRoom isKeyBackupTrusted isSecretStorageReady prepareToEncrypt requestDeviceVerification requestOwnUserVerification requestVerificationDM resetKeyBackup setDeviceVerified setTrustCrossSignedDevices storeSessionBackupPrivateKey userHasCrossSigningKeys

Properties

globalBlacklistUnverifiedDevices

globalBlacklistUnverifiedDevices: boolean

Global override for whether the client should ever send encrypted messages to unverified devices. This provides the default for rooms which do not specify a value.

If true, all unverified devices will be blacklisted by default

Methods

bootstrapCrossSigning

  • bootstrapCrossSigning(opts): Promise<void>

  • Bootstrap cross-signing by creating keys if needed.

    If everything is already set up, then no changes are made, so this is safe to run to ensure cross-signing is ready for use.

    This function:

    • creates new cross-signing keys if they are not found locally cached nor in secret storage (if it has been set up)
    • publishes the public keys to the server if they are not already published
    • stores the private keys in secret storage if secret storage is set up.

    Parameters

    Returns Promise<void>

bootstrapSecretStorage

  • bootstrapSecretStorage(opts): Promise<void>

  • Bootstrap the secret storage by creating a new secret storage key, add it in the secret storage and store the cross signing keys in the secret storage.

    • Generate a new key GeneratedSecretStorageKey with createSecretStorageKey. Only if setupNewSecretStorage is set or if there is no AES key in the secret storage
    • Store this key in the secret storage and set it as the default key.
    • Call cryptoCallbacks.cacheSecretStorageKey if provided.
    • Store the cross signing keys in the secret storage if
      • the cross signing is ready
      • a new key was created during the previous step
      • or the secret storage already contains the cross signing keys

    Parameters

    Returns Promise<void>

checkKeyBackupAndEnable

  • checkKeyBackupAndEnable(): Promise<null | KeyBackupCheck>

  • Force a re-check of the key backup and enable/disable it as appropriate.

    Fetches the current backup information from the server. If there is a backup, and it is trusted, starts backing up to it; otherwise, disables backups.

    Returns Promise<null | KeyBackupCheck>

    null if there is no backup on the server. Otherwise, data on the backup as returned by the server, and trust information (as returned by isKeyBackupTrusted).

createRecoveryKeyFromPassphrase

  • createRecoveryKeyFromPassphrase(password?): Promise<GeneratedSecretStorageKey>

  • Create a recovery key (ie, a key suitable for use with server-side secret storage).

    The key can either be based on a user-supplied passphrase, or just created randomly.

    Parameters

    • Optional password: string

      Optional passphrase string to use to derive the key, which can later be entered by the user as an alternative to entering the recovery key itself. If omitted, a key is generated randomly.

    Returns Promise<GeneratedSecretStorageKey>

    Object including recovery key and server upload parameters. The private key should be disposed of after displaying to the use.

crossSignDevice

  • crossSignDevice(deviceId): Promise<void>

  • Cross-sign one of our own devices.

    This will create a signature for the device using our self-signing key, and publish that signature. Cross-signing a device indicates, to our other devices and to other users, that we have verified that it really belongs to us.

    Requires that cross-signing has been set up on this device (normally by calling bootstrapCrossSigning).

    Note: Do not call this unless you have verified, somehow, that the device is genuine!

    Parameters

    • deviceId: string

      ID of the device to be signed.

    Returns Promise<void>

deleteKeyBackupVersion

  • deleteKeyBackupVersion(version): Promise<void>

  • Deletes the given key backup.

    Parameters

    • version: string

      The backup version to delete.

    Returns Promise<void>

exportRoomKeys

exportRoomKeysAsJson

  • exportRoomKeysAsJson(): Promise<string>

  • Get a JSON list containing all of the room keys

    This should be encrypted before returning it to the user.

    Returns Promise<string>

    a promise which resolves to a JSON string encoding a list of session export objects, each of which is an IMegolmSessionData

findVerificationRequestDMInProgress

  • findVerificationRequestDMInProgress(roomId): undefined | Crypto.VerificationRequest

  • Finds a DM verification request that is already in progress for the given room id

    Parameters

    • roomId: string

      the room to use for verification

    Returns undefined | Crypto.VerificationRequest

    the VerificationRequest that is in progress, if any

    Deprecated

    prefer userId parameter variant.

  • findVerificationRequestDMInProgress(roomId, userId?): undefined | Crypto.VerificationRequest

  • Finds a DM verification request that is already in progress for the given room and user.

    Parameters

    • roomId: string

      the room to use for verification.

    • Optional userId: string

      search for a verification request for the given user.

    Returns undefined | Crypto.VerificationRequest

    the VerificationRequest that is in progress, if any.

forceDiscardSession

  • forceDiscardSession(roomId): Promise<void>

  • Discard any existing megolm session for the given room.

    This will ensure that a new session is created on the next call to prepareToEncrypt, or the next time a message is sent.

    This should not normally be necessary: it should only be used as a debugging tool if there has been a problem with encryption.

    Parameters

    • roomId: string

      the room to discard sessions for

    Returns Promise<void>

getActiveSessionBackupVersion

  • getActiveSessionBackupVersion(): Promise<null | string>

  • Get the current status of key backup.

    Returns Promise<null | string>

    If automatic key backups are enabled, the version of the active backup. Otherwise, null.

getCrossSigningKeyId

  • getCrossSigningKeyId(type?): Promise<null | string>

  • Get the ID of one of the user's cross-signing keys.

    Parameters

    • Optional type: CrossSigningKey

      The type of key to get the ID of. One of CrossSigningKey.Master, CrossSigningKey.SelfSigning, or CrossSigningKey.UserSigning. Defaults to CrossSigningKey.Master.

    Returns Promise<null | string>

    If cross-signing has been initialised on this device, the ID of the given key. Otherwise, null

getCrossSigningStatus

getDeviceVerificationStatus

  • getDeviceVerificationStatus(userId, deviceId): Promise<null | DeviceVerificationStatus>

  • Get the verification status of a given device.

    Parameters

    • userId: string

      The ID of the user whose device is to be checked.

    • deviceId: string

      The ID of the device to check

    Returns Promise<null | DeviceVerificationStatus>

    null if the device is unknown, or has not published any encryption keys (implying it does not support encryption); otherwise the verification status of the device.

getEncryptionInfoForEvent

getOwnDeviceKeys

getSessionBackupPrivateKey

getTrustCrossSignedDevices

getUserDeviceInfo

  • getUserDeviceInfo(userIds, downloadUncached?): Promise<DeviceMap>

  • Get the device information for the given list of users.

    For any users whose device lists are cached (due to sharing an encrypted room with the user), the cached device data is returned.

    If there are uncached users, and the downloadUncached parameter is set to true, a /keys/query request is made to the server to retrieve these devices.

    Parameters

    • userIds: string[]

      The users to fetch.

    • Optional downloadUncached: boolean

      If true, download the device list for users whose device list we are not currently tracking. Defaults to false, in which case such users will not appear at all in the result map.

    Returns Promise<DeviceMap>

    A map {@link DeviceMap}.

getUserVerificationStatus

getVerificationRequestsToDeviceInProgress

getVersion

  • getVersion(): string

  • Return the current version of the crypto module. For example: Rust SDK ${versions.matrix_sdk_crypto} (${versions.git_sha}), Vodozemac ${versions.vodozemac}.

    Returns string

    the formatted version

importRoomKeys

importRoomKeysAsJson

  • importRoomKeysAsJson(keys, opts?): Promise<void>

  • Import a JSON string encoding a list of room keys previously exported by exportRoomKeysAsJson

    Parameters

    • keys: string

      a JSON string encoding a list of session export objects, each of which is an IMegolmSessionData

    • Optional opts: ImportRoomKeysOpts

      options object

    Returns Promise<void>

    a promise which resolves once the keys have been imported

isCrossSigningReady

  • isCrossSigningReady(): Promise<boolean>

  • Checks whether cross signing:

    • is enabled on this account and trusted by this device
    • has private keys either cached locally or stored in secret storage

    If this function returns false, bootstrapCrossSigning() can be used to fix things such that it returns true. That is to say, after bootstrapCrossSigning() completes successfully, this function should return true.

    Returns Promise<boolean>

    True if cross-signing is ready to be used on this device

    Throws

    May throw ClientStoppedError if the MatrixClient is stopped before or during the call.

isEncryptionEnabledInRoom

  • isEncryptionEnabledInRoom(roomId): Promise<boolean>

  • Check if we believe the given room to be encrypted.

    This method returns true if the room has been configured with encryption. The setting is persistent, so that even if the encryption event is removed from the room state, it still returns true. This helps to guard against a downgrade attack wherein a server admin attempts to remove encryption.

    Parameters

    • roomId: string

    Returns Promise<boolean>

    true if the room with the supplied ID is encrypted. false if the room is not encrypted, or is unknown to us.

isKeyBackupTrusted

isSecretStorageReady

  • isSecretStorageReady(): Promise<boolean>

  • Checks whether secret storage:

    • is enabled on this account
    • is storing cross-signing private keys
    • is storing session backup key (if enabled)

    If this function returns false, bootstrapSecretStorage() can be used to fix things such that it returns true. That is to say, after bootstrapSecretStorage() completes successfully, this function should return true.

    Returns Promise<boolean>

    True if secret storage is ready to be used on this device

prepareToEncrypt

  • prepareToEncrypt(room): void

  • Perform any background tasks that can be done before a message is ready to send, in order to speed up sending of the message.

    Parameters

    • room: Room

      the room the event is in

    Returns void

requestDeviceVerification

  • requestDeviceVerification(userId, deviceId): Promise<Crypto.VerificationRequest>

  • Request an interactive verification with the given device.

    This is normally used on one of our own devices, when the current device is already cross-signed, and we want to validate another device.

    If a verification for this user/device is already in flight, returns it. Otherwise, initiates a new one.

    To control the methods offered, set ICreateClientOpts.verificationMethods when creating the MatrixClient.

    Parameters

    • userId: string

      ID of the owner of the device to verify

    • deviceId: string

      ID of the device to verify

    Returns Promise<Crypto.VerificationRequest>

    a VerificationRequest when the request has been sent to the other party.

requestOwnUserVerification

requestVerificationDM

resetKeyBackup

setDeviceVerified

  • setDeviceVerified(userId, deviceId, verified?): Promise<void>

  • Mark the given device as locally verified.

    Marking a device as locally verified has much the same effect as completing the verification dance, or receiving a cross-signing signature for it.

    Parameters

    • userId: string

      owner of the device

    • deviceId: string

      unique identifier for the device.

    • Optional verified: boolean

      whether to mark the device as verified. Defaults to 'true'.

    Returns Promise<void>

    Throws

    an error if the device is unknown, or has not published any encryption keys.

    Remarks

    Fires CryptoEvent#DeviceVerificationChanged

setTrustCrossSignedDevices

  • setTrustCrossSignedDevices(val): void

  • Set whether to trust other user's signatures of their devices.

    If false, devices will only be considered 'verified' if we have verified that device individually (effectively disabling cross-signing).

    true by default.

    Parameters

    • val: boolean

      the new value

    Returns void

storeSessionBackupPrivateKey

  • storeSessionBackupPrivateKey(key): Promise<void>

  • Store the backup decryption key.

    This should be called if the client has received the key from another device via secret sharing (gossiping). It is the responsability of the caller to check that the decryption key is valid for the current backup version.

    Parameters

    Returns Promise<void>

    Deprecated

    prefer the variant with a version parameter.

  • storeSessionBackupPrivateKey(key, version): Promise<void>

  • Store the backup decryption key.

    This should be called if the client has received the key from another device via secret sharing (gossiping). It is the responsability of the caller to check that the decryption key is valid for the given backup version.

    Parameters

    • key: Uint8Array

      the backup decryption key

    • version: string

      the backup version corresponding to this decryption key

    Returns Promise<void>

userHasCrossSigningKeys

  • userHasCrossSigningKeys(userId?, downloadUncached?): Promise<boolean>

  • Check if the given user has published cross-signing keys.

    • If the user is tracked, a /keys/query request is made to update locally the cross signing keys.
    • If the user is not tracked locally and downloadUncached is set to true, a /keys/query request is made to the server to retrieve the cross signing keys.
    • Otherwise, return false

    Parameters

    • Optional userId: string

      the user ID to check. Defaults to the local user.

    • Optional downloadUncached: boolean

      If true, download the device list for users whose device list we are not currently tracking. Defaults to false, in which case false will be returned for such users.

    Returns Promise<boolean>

    true if the cross signing keys are available.

Settings

Member Visibility

Theme

On This Page

Generated using TypeDoc