You've already forked matrix-js-sdk
mirror of
https://github.com/matrix-org/matrix-js-sdk.git
synced 2025-11-25 05:23:13 +03:00
Update comment
This commit is contained in:
@@ -974,10 +974,9 @@ export class Crypto extends EventEmitter {
|
|||||||
const backupKey = await this.getSessionBackupPrivateKey() || await getKeyBackupPassphrase();
|
const backupKey = await this.getSessionBackupPrivateKey() || await getKeyBackupPassphrase();
|
||||||
if (!backupKey) {
|
if (!backupKey) {
|
||||||
// This will require user intervention to recover from since we don't have the key
|
// This will require user intervention to recover from since we don't have the key
|
||||||
// backup key anywhere. It's possible that this is a legacy setup where the SSSS
|
// backup key anywhere. The user should probably just set up a new key backup and
|
||||||
// master key is the same as the key backup key, but we can't assume that it is:
|
// the key for the new backup will be stored. If we hit this scenario in the wild
|
||||||
// we'd have to at least check it against the backup. Alternatively, the user could
|
// with any frequency, we should do more than just log an error.
|
||||||
// just set up a new key backup and the key for the new backup will be stored.
|
|
||||||
logger.error("Key backup is enabled but couldn't get key backup key!");
|
logger.error("Key backup is enabled but couldn't get key backup key!");
|
||||||
return;
|
return;
|
||||||
}
|
}
|
||||||
|
|||||||
Reference in New Issue
Block a user