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

E2EE unusable due to cloud backup unlock broken #137

Closed
krille-chan opened this issue Jul 15, 2023 · 6 comments
Closed

E2EE unusable due to cloud backup unlock broken #137

krille-chan opened this issue Jul 15, 2023 · 6 comments
Labels
stale The item is going to be closed soon because of inactivity

Comments

@krille-chan
Copy link
Owner

Description

Since a recent update, the E2EE became unusable due to cloud backup unlock now being broken. See the steps to reproduce.

To Reproduce

  1. Have an account with E2EE cloud backup, possibly needs to be on matrix.org homeserver
  2. Uninstall fluffychat flatpak if present, and wipe ~/.var/app/im.fluffychat.Fluffychat (deletes all your session data!!!!)
  3. Reinstall fluffychat flatpak
  4. Login
  5. Go to Settings > Security and the Cloud backup button. Since this is a fresh session, it should show cloud backup currently being off.
  6. Hit cloud backup and wait for prompt to enter your backup restore password
  7. Enter your cloud backup restore password

--> "Oops, something went wrong..." every single time. All DMs remain encrypted even though it claims cloud backup is on after, so clearly it didn't work.

Additional information:

  • Device: PinePhone
  • OS and OS version: Mobian bookworm
  • Installed version of FluffyChat: latest arm64 flatpak
  • (Android only) Which store are you using:
  • (Android only) Are Google Services available:
@Lunaphied
Copy link

Having this on the iOS App Store version on an iPhone 15 and iOS 17, also happened on previous iPhone 13.

Syncing with another device seemed to work, but that's not always an option and sometimes that's broken too

Copy link

github-actions bot commented Mar 6, 2024

This issue is stale because it has been open for 120 days with no activity.

@github-actions github-actions bot added the stale The item is going to be closed soon because of inactivity label Mar 6, 2024
Copy link

This issue was closed because it has been inactive for 14 days since being marked as stale.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 21, 2024
@Lunaphied
Copy link

What no this is still relevant

Copy link

This issue is stale because it has been open for 120 days with no activity.

@github-actions github-actions bot added the stale The item is going to be closed soon because of inactivity label Jul 21, 2024
Copy link

github-actions bot commented Aug 4, 2024

This issue was closed because it has been inactive for 14 days since being marked as stale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale The item is going to be closed soon because of inactivity
Projects
None yet
Development

No branches or pull requests

3 participants