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 C:\users\pats\Dropbox

I see the following in a ProcMon log I was studying:

QueryOpen \\host\share\users\pats\somedir\myfile.7z

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 ProcMon.exe?

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.

link|improve this question
Is \host\share\users\pats\somedir\myfile.7z the actual file path? It would help to know the actual file in question. – iglvzx Dec 19 '11 at 7:39
I didn't save the log, and I don't remember the name. Sorry about that. I didn't think the exact name would matter. I thought the observation that DropBox.exe was accessing a remote share was interesting enough. – PatS Dec 20 '11 at 17:55
feedback

migrated from stackoverflow.com Dec 19 '11 at 7:30

This question came from our site for professional and enthusiast programmers.

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
or
required, but never shown

Browse other questions tagged or ask your own question.