|
|
|
|
|
|
by jerf
5082 days ago
|
|
|
In theory, they can do the encryption for you, on the client, and never send themselves the key. However, the effort required to audit a given client and verify that they are in fact doing that, doing it securely, and doing it in a way where they won't later change their minds and grab the key or whatever greatly exceeds the effort of simply handling the encryption yourself. I understand why people call for this, but it's really a very narrow window of "security concern" where that's a valid feature. Much better would be an open API, and an open source client, which does the encryption, preferably not even technically affiliated with the cloud provider. |
|
|
During installation, Dropbox asks the OS for an encrypted read/write view of "/home/user/Dropbox". The OS confirms this with the user. The user sets up the key/password for that encryption. Done.
If Dropbox is compelled in future to try and gain access to the unencrypted view of that same folder, it would have to ask the OS permission, and the OS would ask the user.
Dropbox could also ask for an unencrypted view on the initial installation, but the user should still be allowed to specify that the view it gets is of the encrypted versions of files only. This would be entirely transparent. Dropbox would have no idea if it's getting the full view or the encrypted view.