Extract callbacks to a new module
This commit is contained in:
parent
9f1c2cd3e1
commit
7446bcdedb
2 changed files with 67 additions and 44 deletions
|
@ -1,7 +1,8 @@
|
|||
/*
|
||||
Copyright 2015, 2016 OpenMarket Ltd
|
||||
Copyright 2017 Vector Creations Ltd.
|
||||
Copyright 2017 New Vector Ltd
|
||||
Copyright 2017, 2018, 2019 New Vector Ltd
|
||||
Copyright 2019 The Matrix.org Foundation C.I.C.
|
||||
|
||||
Licensed under the Apache License, Version 2.0 (the "License");
|
||||
you may not use this file except in compliance with the License.
|
||||
|
@ -30,8 +31,7 @@ import {verificationMethods} from 'matrix-js-sdk/lib/crypto';
|
|||
import MatrixClientBackedSettingsHandler from "./settings/handlers/MatrixClientBackedSettingsHandler";
|
||||
import * as StorageManager from './utils/StorageManager';
|
||||
import IdentityAuthClient from './IdentityAuthClient';
|
||||
import { deriveKey } from 'matrix-js-sdk/lib/crypto/key_passphrase';
|
||||
import { decodeRecoveryKey } from 'matrix-js-sdk/lib/crypto/recoverykey';
|
||||
import * as CrossSigningManager from './CrossSigningManager';
|
||||
|
||||
interface MatrixClientCreds {
|
||||
homeserverUrl: string,
|
||||
|
@ -222,48 +222,9 @@ class MatrixClientPeg {
|
|||
identityServer: new IdentityAuthClient(),
|
||||
};
|
||||
|
||||
opts.cryptoCallbacks = {};
|
||||
if (SettingsStore.isFeatureEnabled("feature_cross_signing")) {
|
||||
// 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 keys = {};
|
||||
opts.cryptoCallbacks = {
|
||||
// XXX: This flow should maybe be reworked to allow retries in
|
||||
// case of typos, etc.
|
||||
getSecretStorageKey: async keyInfos => {
|
||||
const keyInfoEntries = Object.entries(keyInfos);
|
||||
if (keyInfoEntries.length > 1) {
|
||||
throw new Error("Multiple storage key requests not implemented");
|
||||
}
|
||||
const [name, info] = keyInfoEntries[0];
|
||||
const AccessSecretStorageDialog =
|
||||
sdk.getComponent("dialogs.secretstorage.AccessSecretStorageDialog");
|
||||
const { finished } = Modal.createTrackedDialog("Access Secret Storage dialog", "",
|
||||
AccessSecretStorageDialog, {
|
||||
keyInfo: info,
|
||||
},
|
||||
);
|
||||
const [input] = await finished;
|
||||
if (!input) {
|
||||
throw new Error("Secret storage access canceled");
|
||||
}
|
||||
let key;
|
||||
const { passphrase } = info;
|
||||
if (passphrase) {
|
||||
key = await deriveKey(input, passphrase.salt, passphrase.iterations);
|
||||
} else {
|
||||
key = decodeRecoveryKey(input);
|
||||
}
|
||||
return [name, key];
|
||||
},
|
||||
// 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?
|
||||
getCrossSigningKey: k => keys[k],
|
||||
saveCrossSigningKeys: newKeys => Object.assign(keys, newKeys),
|
||||
};
|
||||
Object.assign(opts.cryptoCallbacks, CrossSigningManager);
|
||||
}
|
||||
|
||||
this.matrixClient = createMatrixClient(opts);
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue