You've already forked matrix-react-sdk
mirror of
https://github.com/matrix-org/matrix-react-sdk.git
synced 2025-11-08 21:42:24 +03:00
Clarify current state of cross-signing private keys
This commit is contained in:
@@ -221,8 +221,14 @@ class MatrixClientPeg {
|
|||||||
};
|
};
|
||||||
|
|
||||||
if (SettingsStore.isFeatureEnabled("feature_cross_signing")) {
|
if (SettingsStore.isFeatureEnabled("feature_cross_signing")) {
|
||||||
// TODO: Cross-signing keys are temporarily in memory only. A
|
// This stores the cross-signing private keys in memory for the JS SDK. They
|
||||||
// separate task in the cross-signing project will build from here.
|
// are also persisted to Secure Secret Storage in account data by
|
||||||
|
// the JS SDK when created.
|
||||||
|
// XXX: On desktop platforms, we plan to store only the SSSS default
|
||||||
|
// key in a secure enclave, while the cross-signing private keys
|
||||||
|
// will still be retrieved from SSSS, so it's unclear that we
|
||||||
|
// actually need these cross-signing application callbacks for Riot.
|
||||||
|
// Should the JS SDK default to in-memory storage of these itself?
|
||||||
const keys = {};
|
const keys = {};
|
||||||
opts.cryptoCallbacks = {
|
opts.cryptoCallbacks = {
|
||||||
getCrossSigningKey: k => keys[k],
|
getCrossSigningKey: k => keys[k],
|
||||||
|
|||||||
Reference in New Issue
Block a user