I don't think the "many clients" argument holds. If done properly, Dropbox would (deterministically) generate the keys from your username and password on the client every time you log in and encrypt/decrypt stuff there.
You're right that sharing folders between different accounts would require having a key shared between the clients and thus stored on the Dropbox servers as well.
However, they could generate the key for the shared folder, give it to you and your buddies and yet store it encrypted using your master key generated from your username and password. Then it would be accessible to you, but Drobox would not be able to decrypt it without getting your password.
It looks like they're not doing that, but hypothetically, they could. And the examples you cite would not be impossible to deal with.
Of course, this would require much more work, would be tricky to get right and they'd have Thomas Ptacek on their back for using JavaScript crypto in the browser.
You are absolutely right in terms of what is technically possible. My point was more that it’s not really realistic to use crypto like that with a Dropbox-like service.
Comments
I don't think the "many clients" argument holds. If done properly, Dropbox would (deterministically) generate the keys from your username and password on the client every time you log in and encrypt/decrypt stuff there.
You're right that sharing folders between different accounts would require having a key shared between the clients and thus stored on the Dropbox servers as well.
However, they could generate the key for the shared folder, give it to you and your buddies and yet store it encrypted using your master key generated from your username and password. Then it would be accessible to you, but Drobox would not be able to decrypt it without getting your password.
It looks like they're not doing that, but hypothetically, they could. And the examples you cite would not be impossible to deal with.
Of course, this would require much more work, would be tricky to get right and they'd have Thomas Ptacek on their back for using JavaScript crypto in the browser.
You are absolutely right in terms of what is technically possible. My point was more that it’s not really realistic to use crypto like that with a Dropbox-like service.