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
Get a list containing all of the room keys
This should be encrypted before returning it to the user.
a promise which resolves to a list of session export objects
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.
the room to discard sessions for
Get the verification status of a given device.
The ID of the user whose device is to be checked.
The ID of the device to check
Verification status of the device, or null
if the device is not known
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.
The users to fetch.
Optional
downloadUncached: booleanIf 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.
A map {@link DeviceMap}
.
Perform any background tasks that can be done before a message is ready to send, in order to speed up sending of the message.
the room the event is in
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.
the new value
Checks if the user has previously published cross-signing keys
This means downloading the devicelist for the user and checking if the list includes the cross-signing pseudo-device.
true if the user has previously published cross-signing keys
Generated using TypeDoc
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.