From 80c120b93b562f16bf1670aaf71ea1b79d260c0f Mon Sep 17 00:00:00 2001 From: "J. Ryan Stinnett" Date: Tue, 10 Dec 2019 16:47:18 +0000 Subject: [PATCH] Cross-signing storage now handled in JS SDK --- src/CrossSigningManager.js | 13 ------------- 1 file changed, 13 deletions(-) diff --git a/src/CrossSigningManager.js b/src/CrossSigningManager.js index dd77eb1f87..b158f0dfaf 100644 --- a/src/CrossSigningManager.js +++ b/src/CrossSigningManager.js @@ -20,19 +20,6 @@ import MatrixClientPeg from './MatrixClientPeg'; import { deriveKey } from 'matrix-js-sdk/lib/crypto/key_passphrase'; import { decodeRecoveryKey } from 'matrix-js-sdk/lib/crypto/recoverykey'; -// This stores the cross-signing private keys in memory for the JS SDK. They are -// also persisted to Secure Secret Storage in account data by the JS SDK when -// created. -const crossSigningKeys = {}; - -// 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? -export const getCrossSigningKey = k => crossSigningKeys[k]; -export const saveCrossSigningKeys = newKeys => Object.assign(crossSigningKeys, newKeys); - // This stores the secret storage private keys in memory for the JS SDK. This is // only meant to act as a cache to avoid prompting the user multiple times // during the same session. It is considered unsafe to persist this to normal