-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Cannot verify devices on account with working 4S but no published public cross-signing keys #27252
Comments
For now, I think the best workaround is to "Reset" cross-signing from the "Security & Privacy" page. |
I have the same issue. Not reproducible in 1.11.53 (can't pinpoint the breaking version, but looks like ~1.11.6x). Same is with app.element.io. I have SSO only enabled if that matters |
Two of my colleagues experienced this bug recently. The "connect to Key Backup" button resulted in an error message and Of note is that the "Reset" button under key backup in settings did not help. It creates a new recovery key, but cross-signing is still not set up after that. When you then try to set up cross signing, it wants a recovery key, but not the recovery key that was just created by resetting key backup. Very confusing. What finally helped was the "reset all" in the recovery key prompt dialog box. That created another new recovery key, but both key backup and cross-signing were working after that. |
same behavior, had to downgrade the client to 1.11.55 |
I think this is more "Element R roundoff" than "UTD fixes"; updating the workstream accordingly |
#26322 feels like a common way for real people to hit this, which would explain why we see this more in the wild and not at all in tests. |
Suppose you have a user account, where SSSS has been set up, and contains the private cross-signing keys, but the public keys have never been published. See #27253.
Now, when you log in on the account:
Console reports:
The text was updated successfully, but these errors were encountered: