Bug 1712944 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

To support encryption, we need to be able to load and run libolm. There is a JS + WASM version of it available. However, it either relies on node crypto/fs/path etc. or expects a full browser environment.

Further, for cryptography to work, we need to provide a session store to the client. There is a session store implementation based on `localStorage`, so we need to create a `localStorage` for the matrix account, probably with `Services.domStorageManager.createStorage`.
To support encryption, we need to be able to load and run libolm (https://gitlab.matrix.org/matrix-org/olm/-/packages/10). There is a JS + WASM version of it available. However, it either relies on node crypto/fs/path etc. or expects a full browser environment.

Further, for cryptography to work, we need to provide a session store to the client. There is a session store implementation based on `localStorage`, so we need to create a `localStorage` for the matrix account, probably with `Services.domStorageManager.createStorage`.

Back to Bug 1712944 Comment 0