hi there, arash from dropbox here. all data is (as we state in the referenced help article) encrypted before it's stored on the backend. all data on dropbox can be made shareable and is web viewable. as a consequence, we do need the ability to decrypt in the cloud. re. employee access to files - there are controls to prevent this. for example, even drew (founder/CEO), doesn't have physical access to our storage serve…
Everything on your website that in any way addresses "Dropbox's security" should make absolutely clear the extent to which users can expect their data to be "secure". In Dropbox's case, users can expect the following: - Data is probably secure from sniffers That's it. It matters little whether "Drew has physical access to our storage servers anymore". Your code obviously has easy access to the keys used to encrypt an…
Dropbox Lack of Security
71–80 of 193 posts
Re: Dropbox Lack of Security
#72Earlier quoted context omitted.
The authentication token can be generated and managed by the software. It would then be protected by the account password, if any (Windows and MacOS X offer this feature). Doable, and even better, you can make that a 30 € / month corporate option. ;)
If the key file is stored on Dropbox servers, then Dropbox has access to all of your files. This defeats the original purpose (security). If the key file is not stored on Dropbox servers, then you can't easily use Dropbox across several different computers. This defeats the other purpose (accessibility).
Re: Dropbox Lack of Security
#73forgive me if I'm naive, but can file hashes be spoofed in any way? I'm thinking upload a bunch of files that hash to random numbers, then download the de-duplicated original files. could someone more knowledgable in this area tell me if this is a credible threat?
In general, solving for f1 and f2 (i.e., you get to control both) such that h(f1)=h(f2) is called finding collisions in hash functions and hash functions like SHA are considered collision-resistant. It is very difficult to find collisions. http://en.wikipedia.org/wiki/Collision_resistance
Of course, if f1=f2, then you've magically guessed the original file, so that is highly unlikely. What you're asking for is something stronger than collision resistance; you're asking for a second preimage, given a first. This is for all practical purposes (requires at least 2^120 or more computations) impossible for any well designed hash function.
Re: Dropbox Lack of Security
#74It is possible to design a Dropbox-like system with the following properties: 1. Files are stored encrypted. 2. The service provider does not have the ability to arbitrarily decrypt the files. By "arbitrarily decrypt" I mean decrypt at any time they wish. They will be able to decrypt if the owner's client is actively connected. 3. When someone uploads a file that is identical to an existing file, it initially is stor…
Re: Dropbox Lack of Security
#75It is possible to design a Dropbox-like system with the following properties: 1. Files are stored encrypted. 2. The service provider does not have the ability to arbitrarily decrypt the files. By "arbitrarily decrypt" I mean decrypt at any time they wish. They will be able to decrypt if the owner's client is actively connected. 3. When someone uploads a file that is identical to an existing file, it initially is stor…
This system already exists. * Wuala (using encryption but somewhat insecure deduplication) * SpiderOak (using more secure deduplication: https://spideroak.com/blog/20100827150530-why-spideroak-does... )
Re: Dropbox Lack of Security
#76Earlier quoted context omitted.
The authentication token can be generated and managed by the software. It would then be protected by the account password, if any (Windows and MacOS X offer this feature). Doable, and even better, you can make that a 30 € / month corporate option. ;)
Isn't one of the major cool things about dropbox that if your computer hard drive gets smashed (and thus the key is destroyed), you can still access your files somewhere else?
Re: Dropbox Lack of Security
#77Earlier quoted context omitted.
If the key file is stored on Dropbox servers, then Dropbox has access to all of your files. This defeats the original purpose (security). If the key file is not stored on Dropbox servers, then you can't easily use Dropbox across several different computers. This defeats the other purpose (accessibility).
You can store a key escrow on the dropbox server protected by a password or a token. Just a matter of designing something secure and useable. Not easy, but possible.
Re: Dropbox Lack of Security
#78This is the first time I've heard someone on HN actually ask for more security theatre. Sure, Dropbox could spend seven figures to get a ISOxxxx whatever consultancy to draw up a 125 page document describing their internal checks, do the obligatory all-hands yearly mandatory training where you have to get 10/10 questions right and question 1 is "A user has uploaded naked pictures of themselves to their account. True…
I might have misunderstood what you meant, but #1 is invalid. If I can look at my data any time I want, I just need the key to it. Dropbox just gives me access to the encrypted stream. Giving access to my data to someone else would therefore just be a question of sharing the key with that person, again, without Dropbox ever having access to this key. Your killer argument is to me #3. If you don't trust a company, don…
Re: Dropbox Lack of Security
#79Earlier quoted context omitted.
What about allowing government access to files? Do you require a warrant? Under what circumstances?
we take as firm as stance as possible on user privacy (google faces and fights these very issues) the government needs to comply with the provisions of the electronic communications privacy act by obtaining a warrant supported by probable cause (or in some cases a court order from a judge). these safeguards protect user privacy, even when the government is involved.
This is why encryption of data in the cloud, where the keys are not held by the provider, is essential.
Re: Dropbox Lack of Security
#80Earlier quoted context omitted.
we take as firm as stance as possible on user privacy (google faces and fights these very issues) the government needs to comply with the provisions of the electronic communications privacy act by obtaining a warrant supported by probable cause (or in some cases a court order from a judge). these safeguards protect user privacy, even when the government is involved.
Assuming you store files as a combination of a hash digest function as a key and file data as a value; what controls do you have in place to handle situations where law enforcement discovers some sort of 'illegal' file data on one users account subsequently requests details on users with hash digests that match the data in that file?
See: "How Dropbox sacrifices user privacy for cost savings"
http://paranoia.dubfire.net/2011/04/how-dropbox-sacrifices-u...