0635b40729
The spec says that the required signatures for a signed event is the signature of sender's server (unless is a third party invite) and the `event_id` server (in v1 and v2 room versions). This changes the previous behaviour, which tried to verify the signatures for all the servers in the `PublicKeyMap`, instead of checking only the required signatures. Relevant spec section: https://matrix.org/docs/spec/server_server/r0.1.4#validating-hashes-and-signatures-on-received-events
Ruma – Your home in Matrix.
A set of Rust crates (libraries) for interacting with the Matrix chat network.
Status
As of 2020-09-29, we support the vast majority of endpoints in all of the various Matrix APIs.
As long as they are still at version 0.x though, only the latest API revision is considered supported. This may change after 1.x releases.
Contributing
See CONTRIBUTING.md.
Minimum Rust version
Ruma currently requires Rust 1.43. In general, we will never require beta or nightly for crates.io releases of our crates, and we will try to avoid releasing crates that depend on features that were only just stabilized.
There are two exceptions to this:
- ruma-signatures (and hence ruma with the federation-api feature) since it depends on ring, which is only guaranteed to work on the latest stable.
- ruma-client depends on some I/O libraries (and also on ring, conditionally), so it is also only guaranteed to work on the latest stable.