I read the great news in this blog post: https://nextcloud.com/blog/production-ready-end-to-end-encryption-and-new-user-interface-arrive-with-nextcloud-desktop-client-3-0/ but somehow run into a problem.
I am hosting my own nextcloud server and upgraded all components:
- nextcloud server was already 19.0
- e2e encryption app upgraded to 1.5.2 from a previous version and additionally followed those instructions: https://github.com/nextcloud/end_to_end_encryption/releases/tag/v1.5.2-beta1
- updated my ubuntu desktop client to 3.0.0
- updated my phone android app to 3.13.0
Where I run into a problem:
- I started with a freshly encrypted directory by creating a folder in ubuntu.
- Then I enabled e2e encryption for the folder within ubuntu client.
- After that I put a file into the folder and synced the contents to the nextcloud server.
- Everything looks fine in the server web interface: folder shows the locked symbol, filename is encrypted and not accessible.
- I completely wiped the Nextcloud app from my android phone and re-added the account.
- I see the encrypted folder and when opening it asks for my old android device e2e mnemonic/passphrase and does not accept my ubuntu client passphrase.
- It opens the folder but shows encrypted filenames like in the web view.
Did I miss something? Should the app have asked me for the ubuntu client mnemonic (that was my impression from the blog post)? How do I tell my Android app to use the same decryption method/key/mnemonic? Also did not find any option for the other way round (creating the folder in android and using the same decryption in ubuntu).
Currently a bit bummed, that I cannot access e2e encrypted content from both of my client devices.