As someone who has spent quite a lot of time using Windows' File System Watcher functionality, I know that that is nonsense. So DLP alerting that Dropbox is “acccessing” a new file shouldn’t be surprising. This is, by necessity, a system-wide process. > The Dropbox application uses a filesystem monitor to detect when changes are made by monitoring filesystem write events. I was able to produce a test in under 5 minutes that disproves the article's core assumption: This article makes me irrationally annoyed by how lazy the author was. Google wants to data mine your data, even if you delete the data and your google account, google wants to keep using your data, forever. They literally only want to host your data. REMARKABLY less ambiguous, and in fact enumerates the Services they offer. These and other features may require our systems to access, store and scan Your Stuff." Our Services also provide you with features like photo thumbnails, document previews, email organization, easy sorting, editing, sharing and searching. We need your permission to do things like hosting Your Stuff, backing it up, and sharing it when you ask us to. These Terms don't give us any rights to Your Stuff except for the limited rights that enable us to offer the Services. You ignorant, uninformed points are worthless. Once again, make sure you actually read the damned thing in question before even replying to a comment about it. There is nothing legally stopping them from doing it, and if you have been paying attention to the issues highlighted by Snowden and others, there is little backlash to them as a company for doing very evil things such as leaving inter-datacenter communication unencrypted allowing the NSA and others to snoop upon Gmail and all other google services as the data replicates across locations. They can quite literally use your content for any reason because they can use it to develop new services (such as, say, personalized road side advertising.) The fact is, my original statement stands. It used to say any service offered now or in the future, and now it says "to make new services." They changed the TOS to rephrase, but didn't remove the infringing portion.
Safemonk dropbox license#
This license continues even if you stop using our Services (for example, for a business listing you have added to Google Maps). The rights you grant in this license are for the limited purpose of operating, promoting, and improving our Services, and to develop new ones. "When you upload, submit, store, send or receive content to or through our Services, you give Google (and those we work with) a worldwide license to use, host, store, reproduce, modify, create derivative works (such as those resulting from translations, adaptations or other changes we make so that your content works better with our Services), communicate, publish, publicly perform, publicly display and distribute such content. Without reversing the entire program we can't say for sure that Dropbox isn't siphoning out data in some other sneakier way, but the accusations of data theft from these file events are simply not true. It's actually SHEL元2.DLL that is responsible for opening the folder and querying its attributes, not the Dropbox client. This is true but again it's a side effect of an innocent function call, this time SHGetFolderPathW(). Secondly, the original author also posted evidence of Dropbox accessing various shell folders - Desktop, Documents, Music, Pictures, and so on.
Why the Dropbox client calls stat() on files outside of the Dropbox folder (but on the same drive) is not clear, but, as the article above also mentions, that is all it does, so no problem there. A bit later on it does a comparison to ".bat", which identifies it as the function win32_stat() in Modules/posixmodule.c - the ensuing behaviour of this function corresponds to QueryBasicInformation as shown on the original author's Process Monitor dump. Moving up the call stack and disassembling the calling function, we can see that it's part of the Python runtime: (presumably python27_lockdown.dll is Dropbox's custom hardened copy). I couldn't be fussed to reverse it again, so instead used Rohitab Batra's excellent API Monitor to figure out what's really going on.įirstly to address files being accessed outside of Dropbox - this is true, but literally all it does is read the file attributes.
0 kommentar(er)
