Skip to content

Conversation

@dbkr
Copy link
Member

@dbkr dbkr commented Jul 8, 2021

If the account has both a key backup and SSSS enabled but the key
backup key isn't stored in SSSS, try to save it there by getting
it from either the cache or the user (if perhaps it's the same as
their security passphrase but lost a passthrough entry).

Fixes element-hq/element-web#17886

If the account has both a key backup and SSSS enabled but the key
backup key isn't stored in SSSS, try to save it there by getting
it from either the cache or the user (if perhaps it's the same as
their security passphrase but lost a passthrough entry).

Fixes element-hq/element-web#17886
@dbkr dbkr requested a review from a team July 8, 2021 20:17
dbkr added a commit to matrix-org/matrix-react-sdk that referenced this pull request Jul 8, 2021
The device listener checks for a megolm key stored in SSSS but didn't
update when one was added, so the encryption upgrade toast would not
disappear after the key was fixed by matrix-org/matrix-js-sdk#1776
dbkr added 2 commits July 8, 2021 21:20
Mostly because that's what the test tests, so let's keep that
behaviour the same.
@dbkr dbkr merged commit 2d67a35 into develop Jul 9, 2021
@t3chguy t3chguy deleted the dbkr/rescue_lost_megolm_key branch May 10, 2022 14:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Spurious 'upgrade encryption' toast

3 participants