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

Settings screen shows "Private Keys on device" even if the MSK is missing #8994

Open
richvdh opened this issue Jan 29, 2025 · 1 comment
Open
Labels
T-Defect Something isn't working: bugs, crashes, hangs and other reported problems

Comments

@richvdh
Copy link
Member

richvdh commented Jan 29, 2025

Suppose you have a device which (for historical reasons) has the private user-signing and self-signing keys, but not the private master key.

In that case, the "cross signing" tab in settings will look like this:

Image

"Private Keys on device" is incorrect. The listed keys are the public keys.

@richvdh richvdh added the T-Defect Something isn't working: bugs, crashes, hangs and other reported problems label Jan 29, 2025
@richvdh
Copy link
Member Author

richvdh commented Jan 29, 2025

This then causes other problems when you try to verify against this device: we will happily accept the verification request, but that still leaves the other device in an "out of sync" state: element-hq/element-meta#2642.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-Defect Something isn't working: bugs, crashes, hangs and other reported problems
Projects
None yet
Development

No branches or pull requests

1 participant