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

Enable key backup by default #28691

Merged
merged 22 commits into from
Dec 17, 2024
Merged

Enable key backup by default #28691

merged 22 commits into from
Dec 17, 2024

Conversation

dbkr
Copy link
Member

@dbkr dbkr commented Dec 9, 2024

When we set up cross signing, so the key backup key will be stored locally along with the cross signing keys until the user sets up recovery (4s). This will mean that a user can restore their backup if they log in on a new device as long as they verify with the one they registered on.

Replaces #28267

Checklist

  • Tests written for new code (and old code if feasible).
  • New or updated public/exported symbols have accurate TSDoc documentation.
  • Linter and other CI checks pass.
  • I have licensed the changes to Element by completing the Contributor License Agreement (CLA)

dbkr added 6 commits December 6, 2024 15:10
To make components pure and avoid react 18 dev mode problems due
to components making requests when mounted.
When we set up cross signing, so the key backup key will be stored locally along with the cross signing keys until the user sets up recovery (4s). This will mean that a user can restore their backup if they log in on a new device as long as they verify with the one they registered on.

Replaces #28267
logger.log("uploadDeviceSigningKeys unexpectedly succeeded without UI auth!");
return false;
return true;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the meat of the PR no?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not really: this actually worked before by going through the UIA flow which just worked because it didn't actually need UIA. That fails in dev mode now though. Fortunately, it was a bug that we were going via the UIA flow anyway.

@dbkr
Copy link
Member Author

dbkr commented Dec 16, 2024

Unfortunately the toast and backup by default change depended on one another, so couldn't really be split out. That just left the one-line fix for uploading keys, which I could have split out but didn't bother as I'd already split out quite a few other bits.

@dbkr dbkr requested a review from richvdh December 16, 2024 19:03
Copy link
Member

@richvdh richvdh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm otherwise

src/components/views/dialogs/LogoutDialog.tsx Outdated Show resolved Hide resolved
src/toasts/SetupEncryptionToast.ts Outdated Show resolved Hide resolved
@dbkr dbkr added this pull request to the merge queue Dec 17, 2024
Merged via the queue into develop with commit 980b922 Dec 17, 2024
33 checks passed
@dbkr dbkr deleted the dbkr/key_backup_by_default_2 branch December 17, 2024 15:06
Furka-090

This comment was marked as spam.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants