fix: Cache ssss keys if using an existing ssss in bootstrapping
This commit is contained in:
parent
bb9f0dd98a
commit
0462863ce6
|
|
@ -308,13 +308,14 @@ class Bootstrap {
|
||||||
checkCrossSigning();
|
checkCrossSigning();
|
||||||
}
|
}
|
||||||
|
|
||||||
void openExistingSsss() {
|
Future<void> openExistingSsss() async {
|
||||||
if (state != BootstrapState.openExistingSsss) {
|
if (state != BootstrapState.openExistingSsss) {
|
||||||
throw BootstrapBadStateException();
|
throw BootstrapBadStateException();
|
||||||
}
|
}
|
||||||
if (!newSsssKey.isUnlocked) {
|
if (!newSsssKey.isUnlocked) {
|
||||||
throw BootstrapBadStateException('Key not unlocked');
|
throw BootstrapBadStateException('Key not unlocked');
|
||||||
}
|
}
|
||||||
|
await newSsssKey.maybeCacheAll();
|
||||||
checkCrossSigning();
|
checkCrossSigning();
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue