Help:Paranoid permissions

From GRWiktionaryHelp

Apache and CGIWrap

If you have your own server running Apache and are running PHP as CGI, you can install CGIWrap. This tool enables you to run the Apache server as a different user for CGIs.

That way, you can create a new user for your Wikimedia pages. Installing CGIWrap is beyond the scope of this document, especially since you must compile it accordingly to your own server. However, as a quick guideline, you can follow these rules:

• Create a Wikimedia user

useradd -M -s /sbin/nologin wikiuser

• Have a cgi-bin folder, containing CGIWrap (example in /home/myuser/cgi-bin). Once everything is configured, keep only cgiwrap, move the debug versions to another folder if you ever need it. Your cgiwrap file should be accessible only to Apache (chown and chmod accordingly).

chown apache:apache cgiwrap
chmod 500 cgiwrap

• Inside the cgi-bin folder, create a symbolic link to the Wikimedia root.

ln -s /home/myuser/public_html/wiki /home/myuser/cgi-bin/wikilink

• In your wiki's .htaccess file, add the following definitions:

AddHandler php-wrapper .php
Action php-wrapper /cgi-bin/cgiwrap/wikiuser/wikilink

• Finally, chown and chmod all the .php files of your Wikimedia folder to be accessible solely by wikiuser.

chown -R wikiuser:wikiuser *.php
chmod -R 500 *.php

The files will be accessible as usual. You do not need to specify in your path any cgi-bin, as this is transparently taken care for you.

I strongly suggest you start out with /cgi-bin/cgiwrapd/... as your php-wrapper, as it will precisely show what is currently working. I also strongly suggest you do not delete your CGIWrap source folder until everything works perfectly as this is a real trial and error process, taking a long time. However, it's all worth your time as your Wikimedia will be runned in its own separate process, in its own uid, without being able to interfere any other uid. Inverse is also true, except for root, that can read anything anywhere.