Expand description
Uniffi based bindings for the matrix-sdk-crypto
crate.
This crate can be used to introduce E2EE support into an existing Matrix client or client library in any of the language targets Uniffi supports.
Structs§
- Backup keys and information we load from the store.
- The private part of the backup key, the one used for recovery.
- Information on why a verification flow has been cancelled and by whom.
- A result type for confirming verifications.
- A struct containing private cross signing keys that can be backed up or uploaded to the secret store.
- Struct representing the state of our private cross signing keys, it shows which private cross signing keys we have locally stored.
- An event that was successfully decrypted.
- Dehydrated device key
- An E2EE capable Matrix device.
- Settings that should be used when a room key is shared.
- A pair of outgoing room key requests, both of those are sendToDevice requests.
- The public part of the backup key.
- Struct collecting data that is important to migrate to the rust-sdk
- A high level state machine that handles E2EE for Matrix.
- Struct containing info about the way the backup key got derived from a passphrase.
- A pickled version of an
Account
. - A pickled version of an
InboundGroupSession
. - A pickled version of a
Session
. - The encryption component of PkEncryption support.
- A message that was encrypted using a
PkEncryption
object. - The
m.qr_code.scan.v1
,m.qr_code.show.v1
, andm.reciprocate.v1
verification flow. - A result type for requesting verifications.
- Struct holding the number of room keys we have.
- Room encryption settings which are modified by state events or user options
- The
m.sas.v1
verification flow. - A result type for scanning QR codes.
- Struct collecting data that is important to migrate sessions to the rust-sdk
- Take a look at
matrix_sdk_common::deserialized_responses::ShieldState
for more info. - The result of a signature verification of a signed JSON object.
- A result type for starting SAS verifications.
- Enum representing the different verification flows we support.
- The verificatoin request object which then can transition into some concrete verification method
- Build-time information about important crates that are used.
Enums§
- Error type for the decoding and storing of the backup key.
- An encryption algorithm to be used to encrypt messages sent to a room.
- Who can see a room’s history.
- Error type for the migration process.
- Error type for the decryption of backed up room keys.
- An Enum describing the state the QrCode verification is in.
- An Enum describing the state the SAS verification is in.
- Take a look at
matrix_sdk_common::deserialized_responses::ShieldState
for more info. - Enum representing cross signing identity of our own user or some other user.
- An Enum describing the state the QrCode verification is in.
Traits§
- Trait that can be used to forward Rust logs over FFI to a language specific logger.
- Callback that will be passed over the FFI to report progress
- Listener that will be passed over the FFI to report changes to a QrCode verification.
- Listener that will be passed over the FFI to report changes to a SAS verification.
- Listener that will be passed over the FFI to report changes to a verification request.
Functions§
- Migrate a libolm based setup to a vodozemac based setup stored in a SQLite store.
- Migrate room settings, including room algorithm and whether to block untrusted devices from legacy store to Sqlite store.
- Migrate sessions and group sessions of a libolm based setup to a vodozemac based setup stored in a SQLite store.
- Set the logger that should be used to forward Rust logs over FFI.