I'm trying to figure out how to totally isolate a wine prefix (such as ~/.wine) to it's own folder. This is for security and morso simply for neatness. Obviously, the first step would be to totally disconnect the home/desktop integration in winecfg, right?

Is there some way I can run wine so that wine is limited in permissions to only read/write from the ./wine directory? (or just write permissions, if read is necessary for the dll integration?)

Basically, my question is this: Is it possible to isolate wine to ~/.wine? If so, how can this best be accomplished? I'm using wine 1.6, if it makes a difference.

  • See my answer here re wine 'sandbox' mode, which is nothing like a true sandbox, but may be useful nonetheless. – user76204 Aug 6 '13 at 17:44

Wine needs access to its different parts: it reads from fonts in /usr/share/wine, a bunch of shared object libraries in /usr/share, not to mention the .dlls in the same place.

The best way to keep Wine totally isolated in ~/.wine would be to compile the program from source in that directory. But it will always read information from the various software it uses.

The entire process for 32 bit:

sudo apt-get -y purge wine && sudo apt-get -y --purge autoremove
cd ~/.wine
sudo apt-get -y build-dep wine1.4
apt-get source wine
cd wine1.4-1.4.1/

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.