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

Full harddisk kills keys and renders all chats unusable(?) #15788

Closed
c33s opened this issue Nov 21, 2020 · 1 comment
Closed

Full harddisk kills keys and renders all chats unusable(?) #15788

c33s opened this issue Nov 21, 2020 · 1 comment
Labels

Comments

@c33s
Copy link

c33s commented Nov 21, 2020

Description

had a running riot 1.6.0 installation with working keys and working chats (not backuped on server because of #13685). was away from my computer for a few hours while i made a download. have not noticed that my harddisk was running full. no error was shown from riot. another different app complained about not being able to write to disk. i freed up the space again.
later that day i received a message in riot which was showing me:

** Unable to decrypt: The sender's device has not sent us the keys for this message. **

the previous messages where still readable. thought it might was because of the full harddisk. restarted the riot. now my whole history is gone. every message now shows this error message.

looks like riot rotated some keys and has not checked there is enough space on the disk which also killed my previous keys.

think this should not be like that.

Version information

  • Platform: desktop

For the desktop app:

  • OS: Windows
  • Version: 1.6.0
@c33s c33s added the T-Defect label Nov 21, 2020
@turt2live
Copy link
Member

1.6.0 is unsupported. There's not much we can do about keeping the history when the browser (electron in the case of the desktop app) decides to purge the data - #4014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants