You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The Rust SDK crypto crate recently dropped support for the Sled-based crypto store (matrix-org/matrix-rust-sdk@3e2bc3a51). Thus, any release of the Node bindings made since then won't be able to use a Sled crypto store & must use SQLite instead.
As such, anything that uses the bot-sdk with crypto may need to convert an existing Sled crypto store it may have to a SQLite one.
This isn't a problem for bots/appservices that don't need historical access to encrypted events, which can start a new crypto store from scratch (and register brand new crypto-enabled devices). But not all projects that are out there may be as lucky.
Describe the solution you'd like
There should be a utility (like a yarn script) for converting an existing Sled crypto store to a SQLite one.
The FFI crypto bindings provide an example on how to achieve this. From a discussion in #matrix-rust-sdk:matrix.org:
there's a general purpose migrate() method in the crypto-ffi bindings, but that was used to migrate from whatever Element iOS and Element Android use to the SQLite crypto store
so technically you could use that method to migrate from anything to the SQLite store, but there isn't a nice convenience method that achieves that for the sled store
Describe alternatives you've considered
An alternative is to forego all this and hope that no one is relying on a Sled crypto store.
Additional context
The bulk of the work to achieve this may be in the Node bindings, not here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The Rust SDK crypto crate recently dropped support for the Sled-based crypto store (matrix-org/matrix-rust-sdk@3e2bc3a51). Thus, any release of the Node bindings made since then won't be able to use a Sled crypto store & must use SQLite instead.
As such, anything that uses the bot-sdk with crypto may need to convert an existing Sled crypto store it may have to a SQLite one.
This isn't a problem for bots/appservices that don't need historical access to encrypted events, which can start a new crypto store from scratch (and register brand new crypto-enabled devices). But not all projects that are out there may be as lucky.
Describe the solution you'd like
There should be a utility (like a yarn script) for converting an existing Sled crypto store to a SQLite one.
The FFI crypto bindings provide an example on how to achieve this. From a discussion in #matrix-rust-sdk:matrix.org:
Describe alternatives you've considered
An alternative is to forego all this and hope that no one is relying on a Sled crypto store.
Additional context
The bulk of the work to achieve this may be in the Node bindings, not here.
The text was updated successfully, but these errors were encountered: