Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

KeyBackup / SSSS | Should get the key from SSSS instead of asking recovery Key #1163

Closed
BillCarsonFr opened this issue Mar 24, 2020 · 2 comments · Fixed by #1259
Closed

KeyBackup / SSSS | Should get the key from SSSS instead of asking recovery Key #1163

BillCarsonFr opened this issue Mar 24, 2020 · 2 comments · Fixed by #1259
Labels
A-E2EE-Cross-Signing

Comments

@BillCarsonFr
Copy link
Member

Currently if SSSS is configured with key backup, the keybackup key is in SSSS.
So the keybackup restore screen should ask for SSSS key instead of keybackup recovery key (that the user never had access to)

image
@BillCarsonFr
Copy link
Member Author

We could check for 'm.megolm_backup.v1' in account data , and in this case ask for SSSS passphrase instead of keybackup recovery key

@BillCarsonFr BillCarsonFr mentioned this issue Apr 20, 2020
Merged
@BillCarsonFr
Copy link
Member Author

Additional issue #1260

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-E2EE-Cross-Signing
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

KeyBackup / Use 4S if key in quadS element-hq/element-android
2 participants
@kittykat @BillCarsonFr