UPDATE: Check out the newer post on additional features.
There has been much ado of late about Dropbox security with one of the most egregious issues being how easy it is to surreptitiously “clone” someone else’s Dropbox by obtaining just one piece of data – the host id – from the Dropbox SQLite
Moloch built a Windows & Linux impersonation/cloning utility in Python that was/is meant to be used from a USB/external volume. The utility can save the cloned host id to a local file and also has the capability to use a simple
HTTP GET request to log data to a “mothership” web site.
Since many Dropbox users use OS X (including me) I didn’t want them to feel left out or smugly more secure. So, I set about creating a native version of the utility.
This release is not as feature-rich as Moloch’s Python script but it won’t take much more effort to crank out a version that duplicates all of the functionality. “Release early. Release often.” as the kids these days are wont to say.
You can find the source at its github repository. When building it or just downloading & running the executable (see below), you should heed the repo’s README and take care to change the following items in the application’s
Info.plist property list:
- MothershipURL – this is the URL of the remote host you want to store the cloned info to. It defaults to
somesite.domain/mothership.phpto avoid accidentally sending your own Dropbox data to a remote host. PLEASE NOTE that you will need to get the
mothership.phpscript from the original Windows/Linux code distribution as I have not asked for permission to distribute it here. You can grab the original
dbClone.rardirectly from here: (I love the irony of it being hosted on Dropbox itself).
ALSO NOTE that there’s no need to modify the application’s property list if you don’t mind typing in a URL each run. I eventually plan on making this a separate property list file that allows for multiple URLs so you can select it from a drop-down (and still type a new one if you like).
- LogFilename – just include the filename you want to use when storing the cloned info locally if you do not like the default (it’s the same as Moloch’s –
"GroceryList.txt"). It defaults to the top-level of the mounted volume (the original Linux & Windows dbClone was meant to be run from a USB/external volume) or
"~/"if running it on your boot drive.
You can use the property list editor(s) that come with Apple’s Developer Tools or use vim, TextEdit, TextWrangler (or your favorite text editor) and modify these lines appropriately:
If you do use the “backup” option, the current naming scheme is
"backup-config.db" and it”s important to note that the program will not attempt to overwrite the file. I may change that behaviour in an upcoming release.
I tested the build on OS X 10.6.7 but the Xcode project is set to build for compatibility with 10.5.x or 10.6.x. Feedback on behaviour on other systems would be most welcome.
If you just want the executable, grab the zip’d app and give it a go.
Any and all feedback is welcome (via github or in the comments).