Has anyone successfully deployed Dropbox on their cloud server, while placing limitations on what the Dropbox daemon or client can access? Say, via a chroot jail, AppArmor, creating a separate user account w/limited rights, …?
I’m in the process of writing up an <a href=“https://github.com/DigitalOcean-User-Projects/Articles-and-Tutorials/blob/master/Dropbox_install_ubuntu.md”>article</a> on deploying Dropbox on a DigitalOcean droplet. The component where there does not seem to be much of a consensus, however, is how to reign in Dropbox’s access to files on your system that it has no business going into.
The most helpful article I’ve come across, on the topic, thus far, is <a href=“https://grepular.com/Protecting_Your_GNU_Linux_System_from_Dropbox”>Protecting Your GNU/Linux System from Dropbox</a>; but I’m holding out for a simpler approach.
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.