ec55258be9
Usually only room keys and forwarded room keys are sent as encrypted to-device events, those are specially handled to avoid accepting room keys coming in unencrypted. Some clients might send out other events encrypted which might lower metadata leakage and the spec doesn't disallow it. This patch handles decrypted events the same way as non-encrypted ones, we're still special casing the decryption handling to avoid decryption loops/bombs (i.e. events that are encrypted multiple times). |
||
|---|---|---|
| .github/workflows | ||
| contrib/mitmproxy | ||
| matrix_sdk | ||
| matrix_sdk_appservice | ||
| matrix_sdk_base | ||
| matrix_sdk_common | ||
| matrix_sdk_crypto | ||
| matrix_sdk_test | ||
| matrix_sdk_test_macros | ||
| .gitignore | ||
| .pre-commit-config.yaml | ||
| Cargo.toml | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| tarpaulin.toml | ||
README.md
matrix-rust-sdk
matrix-rust-sdk is an implementation of a Matrix client-server library in Rust.
Project structure
The rust-sdk consists of multiple crates that can be picked at your convenience:
- matrix-sdk - High level client library, with batteries included, you're most likely interested in this.
- matrix-sdk-base - No (network) IO client state machine that can be used to embed a Matrix client in your project or build a full fledged network enabled client lib on top of it.
- matrix-sdk-crypto - No (network) IO encryption state machine that can be used to add Matrix E2EE support to your client or client library.
Status
The library is in an alpha state, things that are implemented generally work but the API will change in breaking ways.
If you are interested in using the matrix-sdk now is the time to try it out and provide feedback.