encryption library
Matrix SDK encryption specific extension
Classes
- Bootstrap
- Bootstrapping SSSS and cross-signing
- DbInboundGroupSessionBundle
- DerivedKeys
- EncryptedContent
- Encryption
- GenerateUploadKeysArgs
- KeyFromPassphraseArgs
- KeyManager
- KeyVerification
- KeyVerificationEmoji
- OpenSSSS
- QRCode
- RoomKeyRequest
- SSSS
- SSSS: Secure Secret Storage and Sharing Read more about SSSS at: https://matrix.org/docs/guides/implementing-more-advanced-e-2-ee-features-such-as-cross-signing#3-implementing-ssss
Constants
- base58 → const Base58Codec
- base58Alphabet → const String
-
cacheTypes
→ const Set<
String> -
knownHashes
→ const List<
String> -
knownHashesAuthentificationCodes
→ const List<
String> -
knownKeyAgreementProtocols
→ const List<
String> - megolmKey → const String
-
olmRecoveryKeyPrefix
→ const List<
int> - pbkdf2DefaultIterations → const int
- pbkdf2SaltLength → const int
- ssssKeyLength → const int
- zeroStr → const String
Functions
-
generateKeyFromPassphrase(
KeyFromPassphraseArgs args) → Future< Uint8List> - you would likely want to use NativeImplementations and Client.nativeImplementations instead
-
generateUploadKeysImplementation(
GenerateUploadKeysArgs args) → RoomKeys - you would likely want to use NativeImplementations and Client.nativeImplementations instead
-
isQrSupported(
List knownVerificationMethods, List possibleMethods) → bool
Enums
- BootstrapState
- KeyVerificationMethod
- KeyVerificationState
-
QR key verification
You create possible methods from
client.verificationMethodson device A and send a request usingrequest.start()which callssendRequest()your client now is inwaitingAcceptstate, where ideally your client would now show some waiting indicator. - QRMode