By pablo
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.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Hey Pablo, <br> <br>If you’re running Ubuntu, I’d look into creating an AppArmor profile for Dropbox. It’s a pretty simple way to lock down a process so that that it only has access certain files, etc: <br> <br>https://wiki.ubuntu.com/AppArmor <br> <br>I think that would probably be the best way forward. <br>
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.