element-hq / element-hq/element-android
Settings screen shows "Private Keys on device" even if the MSK is missing
Open
T-Defect
- Dominant language
- Kotlin
- Stars
- 3.7k
- Forks
- 917
- PR merge metrics
- No merged PRs in 30d
Description
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:
"Private Keys on device" is incorrect. The listed keys are the *public* keys.
Contributor guide
Assessment
This issue has not been assessed yet.