Slashdot Mirror


Dropbox Head Responds To Snowden Claims About Privacy

First time accepted submitter Carly Page writes When asked for its response to Edward Snowden's claims that "Dropbox is hostile to privacy", Dropbox told The INQUIRER that users concerned about privacy should add their own encryption. The firm warned however that if users do, not all of the service's features will work. Head of Product at Dropbox for Business Ilya Fushman says: "We have data encrypted on our servers. We think of encryption beyond that as a users choice. If you look at our third-party developer ecosystem you'll find many client-side encryption apps....It's hard to do things like rich document rendering if they're client-side encrypted. Search is also difficult, we can't index the content of files. Finally, we need users to understand that if they use client-side encryption and lose the password, we can't then help them recover those files."

38 of 176 comments (clear)

  1. umm duh? by Noah+Haders · · Score: 3, Insightful

    Search is also difficult, we can't index the content of files.

    umm duh, that's the point? sucks when your customers can't trust you.

    1. Re:umm duh? by AudioEfex · · Score: 5, Insightful

      Yeah, uh, because all "cloud" services aren't inherently ridiculous for anyone to consider secure or anything...

    2. Re:umm duh? by Anonymous Coward · · Score: 3, Interesting

      Hehe, I have some clients from New Zealand and they were inquiring about some of my company's cloud service offerings. I talked a bit about them but mentioned that they would be better served by hardware that they owned. I asked if they had heard of Mega and what happened to them. They said it was on the news ALL THE TIME in New Zealand. So then I said "Well then you know that law enforcement raided Mega's servers, took them, and have since refused to give all of that data back to its owners. Would you trust your data when that is one of the consequences?" They bought new servers.

    3. Re:umm duh? by Anonymous Coward · · Score: 5, Funny

      me too. i was the guy who wasn't wearing pants.

    4. Re:umm duh? by TheRaven64 · · Score: 5, Interesting
      There are techniques that allow searching within encrypted files, but they rely on the client creating the index. You can then search the index for an encrypted search term and, if you know the keys, interpret the answer. Getting this right is quite tricky (there are several research papers about it), so he's right, but it's not impossible.

      The main reason that I suspect DropBox discourages encryption is that they rely a lot on deduplication to reduce their costs. If everyone encrypted their files, then even two identical files would have different representations server-side if owned by different users, so their costs would go up a lot.

      --
      I am TheRaven on Soylent News
    5. Re:umm duh? by Charliemopps · · Score: 5, Insightful

      Yea, we use a very expesnsive cloud service that per the contract is encrypted at rest and in transit. After 5yrs I happened to have a networking issue and did a packet capture on the stream... no encryption. So we approached them... "Encryption? No, we don't do that..." We explained that it was in the contract and they HAD to do that. So after 2 months they had to move us to a "Special" server and we were encrypted. I checked the packets again and we were at least encrypted in transit. A few months later we had another trouble ticket with them. One of their techs was working on it and explained how he logged in an edited the table raw to fix it. So I asked how he could do that if the data was encrypted. "Encryption? No, we don't do that..." ugh... so now we're supposedly "really" encrypted.

      The problem with cloud services is they can lie cheat and steal with your data and there's nothing you can do about it. You can't verify it, you can't test it, and if anything happens to it you wouldn't have a clue. You're entirely at the mercy of the provider and as time goes on their internal staff can turn over, competence can wane, controls can get lax, and you'll have no idea any of that is happening.

    6. Re:umm duh? by hsmith · · Score: 3, Informative

      You do realize there are several flavors of encryption, right? Microsoft SQL Server TDE is an example. You can login, perform queries, update data in any table, but all data is encrypted - it is - transparent as the name indicates.

      That also ignores things like encrypted volumes, etc. Just because individual files aren't encrypted with unique keys, doesn't mean that encryption isn't there.

    7. Re:umm duh? by Immerman · · Score: 4, Insightful

      So, when you contracted with these folks did they issue you a kilobyte-long encryption key with a warning not to lose it or your data would be permanently inaccessible? And did you have to use that key every time you stored or retrieved data with them? If not, then that's your glaring red flag that any encryption they might offer is a sham. Even if it were stored encrypted on their servers, if you can access it without supplying the encryption key that means they're essentially storing the keys in the lock to the safe.

      Which is why, honestly, I'm okay with folks like Dropbox being a bit lax about security, provided they're open about it. Encryption in transit is nice if you just want to keep idle prying eyes off your not-terribly-sensitive data, and SSH provides a convenient way to implement it. But if you want real security on the stored data the *only* way to get it is if you do just what they're suggesting and exercise total personal control over the encryption. That data should be securely encrypted before it ever leaves your computers, and you are the only one who should possess the keys to decrypt it. If you want people in your organization to have easy access without worrying about encryption then establish a local proxy that will transparently handle the encryption and decryption as data flows through it to your cloud provider.

      Actually that could be a great internet appliance - it could even perform indexing of the data if you wanted it to, while providing near-perfect security for *any* remote data-server offering. If anyone decides to market such a thing I want 1% for the idea - we can make each other rich.

      --
      --- Most topics have many sides worth arguing, allow me to take one opposite you.
    8. Re:umm duh? by nine-times · · Score: 2

      Also, Dropbox is quite popular because of the capability to share files. So I upload a file to Dropbox, and then at some point I want to make it available to my coworker. I can either share it so that it appears in my coworker's Dropbox, or I can just create a public link and allow anyone to access it if I want.

      The simplest model of client-side encryption would not allow for that kind of sharing. I'd encrypt the files with an encryption key, and then I'd need that private encryption key to be able to decrypt it. The next simplest scheme would be standard public-key encryption, which would mean that when the file was encrypted in the first place, I'd have to already know who should be allowed access, and I'd have to use their public key for encryption.

      Now I'm not saying that the problem is insurmountable, but it certainly increases the complexity of the system required. The simplest solution that I can think of would be to set it up so that, when you changed the permissions on the file, it would need to be downloaded, decrypted, rencrypted, and reuploaded. If it came to that, I'd generally rather forgo the encryption, since my data doesn't really require that much privacy. The other option that I could see would be that, when you want to share your data, you pass a private encryption key to the person you're sharing with. However, that would mean that you're either giving them the encryption key to your entire Dropbox, or you're going to end up managing a different encryption key for each file.

      Maybe I'm missing a simpler solution, but in the end, it doesn't seem like a trivial problem.

  2. Our stuff is encrypted!!!! by Y2K+is+bogus · · Score: 5, Insightful

    With the keys we readily hand over when warranted.... o_O

    1. Re:Our stuff is encrypted!!!! by Anonymous Coward · · Score: 4, Interesting

      I wouldn't expect anything more than that from services that are aimed at businesses, and I think you've got to be an idiot if you view a free (or dirt cheap) storage service like Dropbox as anything other than temporary space some stranger's letting you use for a while. You've got to expect that you can't rely on the data to persist when you want it, and that it'll always be there if the government or hackers or anyone besides you wants it. I don't really have a problem with that. At zero dollars, it's been handy to have around and their API is probably the simplest and best of the cloud services I've used (even though their handling of file-type-based app permissions is bizarre).

    2. Re:Our stuff is encrypted!!!! by Mr+44 · · Score: 2
  3. Duh by backslashdot · · Score: 5, Insightful

    Dropbox has Condoleeza Rice on its board of directors. If anyone remembers, she was Secretary of State and also the president's National Security Advisor during the Bush administration. She basically allowed torture, and is responsible for Guantanamo. She had no problem with torturing people without even doing a basic check to see if the person being tortured was guilty of the crime he was being tortured for. And you want to talk about spying? She was part of the administration that developed the PATRIOT Act. The justification being "it's ok to spy on foreigners" .. Oh and we can DECLARE you a foreigner without any due process by making you prove your Americanness. She was cool with torturing foreigners without giving them any sort of due process, so why would you assume that she wont torture citizens if she was scared into doing so? We already know she doesn't think people need privacy.

    1. Re:Duh by rsborg · · Score: 2

      Why is this comment rated so low? If anything, having such a politically invested person on the board of directors really does say something about Dropbox and their views on privacy and security (yes, I do think the same about Apple and Al Gore - his values did seem to align with the company's).

      Ever since 1Password moved to iCloud sync, I've stopped using Dropbox for even stashing an encrypted file. For everything else there're more targeted cloud services.

      --
      Make sure everyone's vote counts: Verified Voting
    2. Re:Duh by operagost · · Score: 3, Insightful

      Good thing she's not a Democrat, or we'd all be calling you racist and sexist.

      --

      Gamingmuseum.com: Give your 3D accelerator a rest.
    3. Re:Duh by towermac · · Score: 2

      Dude, the election is long over, and your guy won.

      "She basically allowed torture"

      Huh. I remember Bush being in charge during that time.

      "is responsible for Guantanamo"

      I don't even know what to do with that.

      "torture"

      I guess she held the garden hose eh?

      "She was part of the administration that developed the PATRIOT Act."

      the Act passed the House 357 to 66; passed the Senate by 98 to 1. But somehow her fault..

      People hate on her because she's a black female Democrat that switched parties, which is not allowed. That racist crap really pisses me off. The fact is; she's a badass, and the only thing she did wrong was to come of age at the same time Bush got elected.

  4. Re:Worst Response of all Time by Anonymous Coward · · Score: 5, Insightful

    It's not stupid; it's just a fact. Obviously they can't do any of that crap if they can't decrypt your data, but that's fine by me.

  5. Re:Worst Response of all Time by AudioEfex · · Score: 5, Insightful

    It's not stupid; it's just a fact. Obviously they can't do any of that crap if they can't decrypt your data, but that's fine by me.

    Exactly. Gotta love the knee-jerk, I can't have a logical thought because I'm just so ready to rant about "the man" bullshit. Especially since it sounds like it's coming from someone who doesn't even use or understand the service.

    Dropbox is file storage, plain and simple. I use it to make a few music files and some reading material available across my devices. That's it's main function, to store/share files.

    All that other shit he is talking about that encryption won't work with is all fluff and ancillary stuff - I name my files properly, for example, so I don't need them to search within them for me. The service works just fine with encrypted files - you just can't use the fancy doodads that you don't really need anyway.

    I applaud him for being honest - if this was certain other companies they'd be telling you "oh trust us. It's secure!" He's being honest - it's a dumping spot for files, if you want encryption, BYO.

    Christ some of the folks around these parts don't know their heads from their asses - use the words encryption or privacy and they don't even listen or understand wtf is being talked about they just automatically jump to tired fear mongering rhetoric. Just like the folks who take rifles strapped across their backs to Starbucks - I want to say, WTF are you so scared of? And if you do have something to be scared of - stay the fuck home, or in this case, don't be a complete retard and use a "cloud" service to begin with.

  6. Re:Worst Response of all Time by Kardos · · Score: 5, Insightful

    So, you would have preferred a positive sounding statement indicating that they are aware that some users have privacy concerns and a vague reference to ongoing efforts to address these concerns?

    I didn't find that response "worst of all time". It came across as lacking in the bullshit department, almost refreshingly so, actually.

  7. Trust No One = TNO by Streetlight · · Score: 5, Insightful

    Steve Gibson's mantra: TNO. If the host has your encryption password/key, then they can't be trusted. If you don't believe that, ask Snowden's email provider, Lavabit's founder Ladar Levison: http://www.wired.com/2014/04/l...

    --
    In a time of universal deceit, telling the truth is a revolutionary act. George Orwell
  8. No big deal (except the encryption part) by scottbomb · · Score: 2, Insightful

    I don't need them to do "rich document rendering" (whatever the hell that is) nor do I need them (or anyone else to) index the contents of my files. All I want is for someone to STORE the shit and keep it synced between all my machines. Dropbox does this very well.

    As for encryption, I don't have time for that nonsense. Anything sensative such as financials is kept locally on my own server or burned to a DVD and put in the closet. I couldn't care less if someone gets a hold of my vast collection of pictures and documents. It is private, but not going to hurt me if someone at the NSA starts snooping around.

    1. Re:No big deal (except the encryption part) by rioki · · Score: 3, Interesting

      You know there is a web interface to Dropbox too? People expect to read their documents, like word or PDF right there online. To do this the service must index the files and read them. Obviously if you encrypt the files, this can not be done.

      I use Dropbox as my offsite backup of sensitive information and I trust the information to be safe. Simple, I encrypt the tar-ball with symmetric GPG. But then again I can only download the file vie the web interface if I wish and not view the contents online... buhuhu

    2. Re:No big deal (except the encryption part) by chihowa · · Score: 3, Informative

      If you use their web interface, they will store your password on their servers. Be aware of that.

      Also, your account password is the the key used to encrypt your data (easy to verify: accessing your data on a new device only requires your account password). They use PDKDF2, which expands the password into a larger key, but (obviously) doesn't add any entropy to that already present in the password. Choose your password wisely.

      That password is also used to access the billing, etc web interface, so they do keep at least a hashed copy of your password on their servers.

      As with any closed source and opaque solution, you shouldn't depend in any way on unverifiable claims. They could now, or at any time in the future, store your passwords. You're better off handling your own security than trusting magic black boxes.

      --
      If you want a vision of the future, imagine a youtube comments section scrolling - forever.
  9. iDrive has the same problem by Animats · · Score: 4, Interesting

    iDrive, which is supposed to be a remote backup service, has a similar problem. They used to be a honest remote backup service, with client-side encryption. (They didn't protect the client password very well on the client machine, but at least the server didn't have it.) File contents were encrypted, but filenames were not, so you could look at logs and the directory tree on line. Then they came out with a "new version" of the service, one that is "web based" and offers "sharing".

    For "sharing" to work, of course, they need to know your encryption key. They suggest using the "default encryption key". Even if you're not "sharing", when you want to recover a copy of a file, you're prompted to enter your encryption key onto a web page. The web page immediately sends the encryption key to the server as plain text, as can be seen from a browser log. Asked about this, they first denied the problem, then, when presented with a browser log, refused to answer further questions.

    They try real hard to get their hands on your encryption key. After you log into their web site, a huge pop-up demands your encryption key. Without it, some of the menu items at the top of the page still work, and with some difficulty, you can actually find logs of what you backed up. You can't browse your directory tree, though.

    It's possible to use the service securely (maybe), but you have to run only the application for recovery, and never use the web-based service. They don't tell you that.

    This isn't a free service. I pay them $150 a year.

    1. Re:iDrive has the same problem by Anonymous Coward · · Score: 3, Insightful

      And Spideroak gives you a closed binary to run on your endpoints, and you quite happily type your password into that. Uh-huh.

      Spideroak are just another vendor saying 'trust us not to have been served an NSL' and trust us not to capture your key with the client software if served an NSL/warrant.

      Once the spideroak client is open and audited, perhaps at that point their marketing about a secure server architecture makes a difference.

  10. Re:what's new by Opportunist · · Score: 3, Funny

    Try to convince a Manager hellbent on joining "The Cloud" and you know the answer is no.

    For a chuckle, have him explain what "The Cloud" is before you do. At least it provides some entertainment before you try to convince him he's about to sink his business.

    --
    We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
  11. Re:Cloudy, chance of rain by martin-boundary · · Score: 2, Insightful
    How is that insightful? You've completely missed the whole point of privacy laws. In law, your hard drive in your computer is yours, and it is not public unless you go out of your way to make it so. In particular, anyone who uses ssh to access your hard drive breaks the law, unless you've specifically authorized them to do so. Lots of people, some slashdot readers, have gone to jail for doing just that.

    Also, your hard disk, in your computer, in your house isn't searcheable by law enforcement unless they have a warrant. So keep your stuff at home, and you'll be better off than leaving it on Dropbox (*).

    (*) I can see you're unconvinced. Let me spell it out for you: if your file is on Dropbox, then a properly worded warrant needs to be served to Dropbox, and they'll allow searches and copies of anything their hard drives contain. Including your file, your neighbour's file, everybody's files. If everybody keeps their own files at home, then a warrant needs to be served to you, to see your files, but it won't work for your neighbour's files. Another warrant needs to be served to the neighbour to see his files. And it won't work for everybody else. A warrant needs to be served individually to everyone, just to get the same access that Dropbox can give with a single properly worded warrant.

  12. I appreciate him saying that. by ddt · · Score: 2

    Perhaps "hostile" was unfair, but I appreciate that he said made it sound shocking. I am shocked when I learn people store secret docs unencrypted on Dropbox. Then they are then shocked when I tell them Dropbox is insecure. There should be a lot less shock all around.

  13. Sensible response by Craig+Ringer · · Score: 2

    That's an accurate and sensible response.

    In fact, 3rd party client encryption tools might be better than built-in support by Dropbox. They can be produced outside the USA by companies or individuals unaffiliated with DropBox and potentially harder to pressure into backdooring the software in an update.

    I'll stick to SpiderOak personally, despite the awful transfer speeds and somewhat clunky usability, because I just want a remote store that stores my gibberish bytes and gives me the same gibberish bytes back later.

  14. Alternatives by fuzzyf · · Score: 2

    I tried using SpiderOak, but it was a bit too slow for me atm. What I really needed was a off-site backup, so I ended up with Amazon Glacier with client side encryption. Can't beat the price :) I have dropbox too, and it's ok for it's use. Just have to realize that everything you upload to them is not private anymore. I wish more services did secure by default and option to reduce security for wanted features.

  15. We should add our own encryption??? by DrXym · · Score: 2, Insightful
    Hi Dropbox, stop blaming users. You are in the strongest position possible to offer encryption in Dropbox because it's your software. You know the triggers that cause files to be exchanged. You know the optimal way to minimize network traffic. If you can send and receive files, then why can't you also encrypt / decrypt files in this step? This could be as simple as providing a settings screen where the user enters a passphrase and once enabled all files within a protected folder are encrypted before they leave the client. This encryption could also scramble file names and break up large files into parts to obfuscate their size.

    Yes you'd have to warn the user that a protected folder means exactly that and there are restrictions on what you can do with it, e.g. access in some dropbox clients, web browsers, sharing to others. People will get it.

    Even better, this encryption / decryption could be thrown open as a pluggable API so 3rd parties could write their own encryption protocols to whatever personal or corporate standard they desired. For transparency the aforementioned passphrase encryption could even be supplied for review.

    Same goes for Skydrive, Google Drive etc. There is no excuse for not offering encryption. Not that I'm in the tinfoil hat camp to think this is to facilitate monitoring (although it does). More likely it's because these cloud storage servers use file hashing to spare themselves the bother of storing 1,000,000 copies of the same file. It still sucks though and even if the option is off by default, encryption of at least one folder should be provided.

    1. Re:We should add our own encryption??? by coofercat · · Score: 4, Informative

      You realise dropbox is free, right? Why should they do something expensive like offer encryption on a service that is (a) free, and (b) for sharing files. Sharing's hard if your stuff is encrypted, and sharing is the source of most of Dropbox's value.

      If you want encryption, then fine, do it yourself. You obviously know that your stuff won't be indexable or shareable so won't be calling for support or slagging Dropbox off online when you find indexing and sharing not working.

      There's room to suggest Dropbox should offer a pay-for encrypted service. The thing is, no matter how well they do it, it'll always be vulnerable to government interference, and it'll never be fully trusted anyway. BYO means no government interference and trust *for the relatively small number of people who care* without raising the costs too much for the multitudes who don't.

    2. Re:We should add our own encryption??? by Immerman · · Score: 2

      There absolutely are several reasons for not offering encryption. Some of the big ones that leap out at me:
      1) Most users are technically incompetent, and when they lose their encryption key they'll be prone to blaming Dropbox for the loss of data.
      2) Compression and data de-duplication between users is effective on unencrypted data, not so much on white noise. Make encryption standard and plan on being able to offer only a small fraction of the capacity at the same price point.
      3) If you want real security you have to assume you can't trust anyone except yourself, and would have to do your own client-side encryption using trustworthy software anyway. It really is the only rational choice where security is concerned.*

      *Even among the services that offer client-side encryption, a dismaying number discretely keep their own copy of your encryption key - at which point the encryption provides little more than an inconvenience to anyone trying to access your data - if they can get access to your encrypted data on the remote servers, they can probably also get access to the copy of your key stored there. And unless the client-side software is open source and audited by multiple independent parties before rolling out every update you have to assume that *every* provider is making that copy.

      --
      --- Most topics have many sides worth arguing, allow me to take one opposite you.
    3. Re:We should add our own encryption??? by trawg · · Score: 2

      You realise dropbox is free, right? Why should they do something expensive like offer encryption on a service that is (a) free, and (b) for sharing files. Sharing's hard if your stuff is encrypted, and sharing is the source of most of Dropbox's value.

      I'm a paying Dropbox customer.

      I would love a feature that lets me client-side encrypt my files before they go to their server; one where the keys never left my machine - being aware that if I lose them, I lose all my data.

      I would want the client software to be open source though and suspect that might not be in their interests.

      Ultimately though I think they've made a conscious choice to not offer a feature like this not because they don't want to or because NSA, but because they see it as a support nightmare.

      I tried a few of the alternatives that do client side encryption - Wuala and SpiderOak. I found them completely painful compared to the simplicity and elegance of Dropbox.

    4. Re:We should add our own encryption??? by DrXym · · Score: 2

      You realise dropbox is free, right?

      Basic Dropbox is, none of the other options are. And besides, why is that an excuse? If they can encrypt data as they send it, and as they store it on the cloud, why is it impossible to encrypt it on the client, or provide an API to allow a 3rd party to encrypt it? Furthermore, as it is the paid service that pays their wages, why aren't they implementing a feature that customers, particularly corporates would pay for and which would enhance their reputation for secure storage?

      If you want encryption, then fine, do it yourself. You obviously know that your stuff won't be indexable or shareable so won't be calling for support or slagging Dropbox off online when you find indexing and sharing not working.

      Well that's a stupid argument right there. I wonder if car companies apply it too - well if you want an airbag in your car why don't you install it yourself? Just because a single individual has the technical wherewithal to implement something doesn't excuse the company for not implementing it in the first place, particularly when it is a feature that many people want.

      There's room to suggest Dropbox should offer a pay-for encrypted service. The thing is, no matter how well they do it, it'll always be vulnerable to government interference, and it'll never be fully trusted anyway. BYO means no government interference and trust *for the relatively small number of people who care* without raising the costs too much for the multitudes who don't.

      No it won't. The point of a well designed client side encryption is Dropbox simply have no idea what they are storing on their servers. Government can interfere until the cows come home but Dropbox have no idea what is in those files.

  16. Re:I think people are missing the point by Captain+Hook · · Score: 2

    Use the web interface to download the file, then decrypt with a local copy of the encryption tool/key.

    What they mean is they can't render a document on the web interface.

    --
    These comments are my personal opinions and do not necessarily reflect the opinions of the other voices in my head.
  17. Use TrueCrypt! by Anonymous Coward · · Score: 3, Informative

    As long as you still trust TrueCrypt, there's no reason you shouldn't use an encrypted container file (or multiple smaller containers) in your Dropbox. Some people might not know this, but Dropbox only re-uploads the parts of the file that change (it does a binary comparison), and TrueCrypt typically only updates relatively small sections of the container file when you add/remove/modify a file in the container, so it doesn't take much bandwidth except for the initial upload. Just make sure you dismount frequently enough to allow Dropbox to sync when you make changes. (I'd recommend setting TrueCrypt to automatically dismount after an hour or so of no data being read/written.)

    You could use the dynamic disk option when creating the TC container to save bandwidth during the initial upload, if you're starting with an empty container (the size of the container will change, up to a set maximum, to match the contents), but that will have other performance penalties when using the container, and it brings with it the increased risks. In particular, it makes it possible for an analyst to get some idea of how you are storing files in the container, potentially making it easier to break the encryption.

    And since it's being stored in the cloud, you should maximize your security by using local keyfiles/tokens rather than a single password. You might as well assume that the whole world has a copy of the container.

    For convenience, you can store a portable unencrypted copy of TrueCrypt in Dropbox as well, but you should really only do that if you keep a local copy of the checksums for the binaries and compare them to the files whenever you run them. (That will ensure that nobody has accessed your account and replaced your portable TC binaries with compromised versions capable of stealing your keys.) Or carry a portable version on a USB drive.

    The only downside I can see to this is that if you need access to your files on a new machine, you will need to download the whole container, and if the new machine is compromised, you could have your keys stolen. Even so, it's much more secure than using Dropbox on its own, and in my opinion, it's worth the potential inconvenience to have good encryption and cloud access.

  18. Confirmation by Kazoo+the+Clown · · Score: 2

    So in other words, Dropbox confirmed Snowden's claims.