9 ms·
I do believe they did more than simply look at the filename. We'll have to disagree there. I'd be very surprised if they did any more than looking at their lo
by cperciva 15y ago
I do believe they did more than simply look at the filename.
We'll have to disagree there. I'd be very surprised if they did any more than looking at their log files -- most likely using tail -f -- as the 100 million mark approached.
Admins will, and are completely expected to, look at the data - if only to make sure everything is working.
How does looking at individual files help to confirm that things are working? Once you're operating at scale, looking at individual files doesn't tell you anything useful; if there's a big problem users will notice it before you do, and if there's a small problem the files you look at probably won't be in the affected set.
Forgive me cperciva, but to me your post looks just like a giant plug for your own service.
Was I plugging Tarsnap? Sure; I mention it every chance I get on my blog. But I didn't write that post because I wanted to plug Tarsnap; I wrote it because I saw the trust-is-fragile post on HN Daily and felt that revising their privacy policy wasn't the right response. (If I had noticed that post when it was first discussed here, that blog post would probably have been just a comment -- but since I was about 24 hours late to the party I figured that nobody would read a comment I made here.)
- Udo 15y agoWe'll have to disagree there. I'd be very surprised if they did any more than looking at their log files I'm probably a little less trusting on this. An admin seeing the filename in the logfile and just calling its URL out of curiosity seems like a very likely scenario to me. They said something like "...and it was a picture of a cat", not "...and it was named cat.jpg". How does looking at individual files help to confirm that things are working? Not in this case, but having access to the file storage system per se is common and useful. But I didn't write that post because I wanted to plug Tarsnap; I understand. The combination of pointing the finger at someone for wrongdoing and then asserting your own superiority seemed inappropriate to me though. I understand where you're coming from, but I also believe to you the world is now full of places that should have client-side encryption, when in fact I don't think this is a good fit for what 37signals does at all. I wrote it because I saw the trust-is-fragile post on HN Daily and felt that revising their privacy policy wasn't the right response. I'm not a 37signals user, and I haven't read their policy. I agree that changing the policy following this incident is very bad timing, but I think this maneuver does correct an unreasonable expectation users might have.
- cperciva 15y agoI don't think [client-side encryption] is a good fit for what 37signals does at all. I'm inclined to agree with you. That's what I was getting at with my "even if 37signals doesn't want to offer cryptographically secure storage, they could at least remove the temptation to look at file names in log files by not writing sensitive information to log files in the first place" line.
- chc 15y agoI think most computer-savvy people, looking at a file called "cat.jpg," would make the leap to "it's a picture of a cat." The name is practically just a compressed version of that.
- Zirro 15y ago"I think most computer-savvy people..." http://cl.ly/0Y1M1D0z1g123I0S0u1R http://cl.ly/0Y1M1D0z1g123I0S0u1R - cat.jpg ;)
- mortenjorck 15y agoThat was actually exactly the alternative I had in mind, an icon for a catalog feature in some sort of application (though a PNG would have been more likely.)
- freddyuggs 15y agoWhat if the file was "kiddie porn.zip" or "TOP SECRET: asassination details for operation 'kill obama'" Aren't there some instances where they'd be justified looking at data...
- cperciva 15y agoI'd say in those circumstances they should be phoning the FBI or the secret service rather than looking at the data themselves.
- freddyuggs 15y agoYeah I think I'd agree there.
- Mavrik 15y agoNo. They're not the police or the court, they have no business playing ones. Attitude like yours gives us stupid privacy-violating terrorism and "protect-the-children" laws.
- deleted 15y ago[deleted]
- freddyuggs 15y agoSo you're saying if they notice 'illegal content' on their servers, they'd just leave it there?
- malandrew 15y agoThe fact that they can notice private "illegal content" at all is a violation of trust. If I mark something private, I should expect that it will be private from everyone including employees of that company. While it is reasonable to expect that they would contact the FBI in such instances, I would also hope that noticing such details illicits a "I shouldnt have been able to see that, so we're not doing enough to protect the privacy of our clients" response and corrective actions.
- sequoia 15y agoWas I plugging Tarsnap? Yes. EDIT: I don't have a problem with it, your service looks nice, but let's be honest. :)
- drumdance 15y agoHow does looking at individual files help to confirm that things are working? "Hello, thanks for calling tech support. How can I help you?" "I uploaded a file but it's not showing up in my account." "What was the name of the file?" "Cat.jpg" "Ok, give me a moment to look at the logs..." These are the kinds of questions that come up all the time in supporting a SaaS product with non-technical and semi-technical users. Debugging is not something only programmers do. Oftentimes bugs are found only after a client interacts with support. Oh, another thing: deletes. At my last company I can't tell you how many times customers wanted us to restore deleted data. After many frustrating support experiences we implemented soft deletes for most objects. Hard deletes required written confirmation from the user and 48 hours to purge it from all backups.