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

Recovered accounts can miss the encryption keys for the community #5057

Closed
jrainville opened this issue Apr 15, 2024 · 0 comments
Closed

Recovered accounts can miss the encryption keys for the community #5057

jrainville opened this issue Apr 15, 2024 · 0 comments

Comments

@jrainville
Copy link
Member

jrainville commented Apr 15, 2024

Problem

I recovered my account using the seed phrase. While it recovered correctly the Status community and the tokens, I found that all the permissioned channels had no member list.
It was discovered that I was missing the encryption keys for those, because I had the latest community description and I could confirm, once I skipped the cache, that I had logs saying I couldn't decrypt.

The reason why it happened is most likely because the community was updated with new encryption keys and since the back up of keys only happens every 8 hours, my account didn't backup those new keys.

So once I reimported the account, it got the previous batch of back up, which had outdated keys.

Implementation

The way to fix is to be determined/analyzed.

One option is to have the member node ask the control node or even a privileged member.

Acceptance Criteria

When a user reimports their account with a permissioned community, the community keys for the channels are re-acquired in a timely manner (less than 5 minutes?)

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

No branches or pull requests

2 participants