I was just using SysInternals
ProcMon.exe to track down a problem and found
Dropbox.exe accesing files outside of the Dropbox folder I have configured.
My Dropbox location is at
I see the following in a ProcMon log I was studying:
Does anyone have an idea why
Dropbox.exe is accessing files outside of the configured Dropbox directroy? Other than the obvious bad reasons (like its copying all of your files, its a Trojan, etc)?
Does anyone else see this behavior when running Dropbox and SysInternals
NOTE: I didn't see
Dropbox.exe reading the data (at least from the ProcMon log I looked at) so perhaps it's a "feature" not a bug.
NOTE 2: This post on the Dropbox forums discusses a concern of Dropbox having a Trojan in it, but it basically says that there is no Trojan in Dropbox.