This is the issue I quickly run into too. One would expect you go and setup the same password everywhere but this is NOT what you should do - you should set the password just in ONE place and then sync everything and enter the password once the other clients complain that they don’t have it. This is even worse as you can’t cleanup after adding a key: Delete E2EE Master Keys (well, unless you nuke everything on all clients and on the common cloud…).
vb0
3
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Issue with E2EE and syncing across Mac/Android | 2 | 504 | 27 February 2021 | |
| Set "active" E2EE key to use for encryption | 5 | 2214 | 12 February 2020 | |
| Why a new encryption key for each device? | 10 | 2113 | 20 May 2021 | |
| New master key is never discovered by other clients | 9 | 1172 | 30 October 2019 | |
| No Encryption key on 2nd computer | 1 | 452 | 8 February 2021 |