-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Enable key backup by default #28691
Conversation
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; |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm otherwise
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
public
/exported
symbols have accurate TSDoc documentation.