-
Notifications
You must be signed in to change notification settings - Fork 773
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
End-to-End Encryption enabled automatically #917
Comments
Just to clarify: on the server e2ee app was enabled again (was disabled in a past upgrade). |
normally the key creation has to be triggered by the client and the client should only trigger it once I set at least one folder to e2e not just because the app was enabled on the server |
This should not be possible right now, as it is not supported at all. |
Discussing this with @tobiasKaminsky I think the client detects the new capability and tries to fetch an existing key from the server, which makes sense, because if the user has some encrypted folders they want to access it. But in case there is no existing key, the initial creation should not be triggered and instead postponed until the user enabled encryption for one folder. |
Now it happened to me also. |
There is a ticket already about this somewhere. This was how is was specified: We could improve here sure. But it is not high on the list of things to fix. |
@tobiasKaminsky had the same confusion about the mnemonics: #753 |
Also, this should not just pop up, but only when it’s relevant. For me it showed when I connected the account, where it’s very irrelevant. It should show only when I either want to encrypt a folder myself, or receive an encrypted folder as a share and want to open it. Otherwise we ask people to write something down that they will not care about at that moment and then not have anymore when they really need it. |
Hello, I think this issue is properly addressed with PR #1241 so closing now. Regards. |
I'm just sitting in front of my computer and without interacting with the sync client this window pops up:
I didn't enabled any end-to-end encryption. Could it be triggered by someone else enabled end-to-end encryption on a shared folder?
The text was updated successfully, but these errors were encountered: