revoking a linked Matrix account also deletes its key-backup passphrase; a plain unlink keeps it for a relink
This commit is contained in:
parent
87dc4c5533
commit
6b3e1f0fb2
1 changed files with 287 additions and 16 deletions
|
|
@ -46,5 +46,14 @@ logout fails because the homeserver no longer recognises the token, the delete
|
|||
goes ahead as if it had worked. Any other failed logout, or an account with no
|
||||
homeserver stored, leaves the account in place and the dialog says why.
|
||||
|
||||
The checkbox also decides what happens to the account's key-backup passphrase,
|
||||
the secret its end-to-end key backup opens with. With it off, the passphrase
|
||||
stays, so linking the same account again finds the passphrase its backup was
|
||||
enabled with and the agent can recover its keys. With it on, the passphrase is
|
||||
deleted after the account, and a later link gets a new one, which cannot open a
|
||||
backup made with the old one. Tick it when the account is gone for good. If the
|
||||
passphrase can't be deleted, the account is already gone and the dialog says
|
||||
so; deleting the account again with the box ticked finishes the job.
|
||||
|
||||
The agent isn't told about a delete. Its matrix daemon drops the account the
|
||||
next time it lists the accounts, within two minutes.
|
||||
|
|
|
|||
Loading…
Reference in a new issue