Sketchy instructions:

Place newcgi.sh, noncgi.html, noncgi.sh, suexec-cgiuser, and suexec-user in
/usr/lib/apache. 

Create a user and group called "cgiuser". Any CGI programs which don't run 
under a specific user will run as cgiuser. Cgiuser should be different from
the httpd user so that CGI programs can't modify the web server state.

mkdir /usr/lib/apache/suexecdir
chown httpd /usr/lib/apache/suexecdir
chgrp root /usr/lib/apache/suexecdir
chmod 700 /usr/lib/apache/suexecdir
cp /usr/lib/apache/suexec-cgiuser /usr/lib/apache/suexecdir/cgiuser
chown cgiuser /usr/lib/apache/suexecdir/cgiuser
chgrp cgigroup /usr/lib/apache/suexecdir/cgiuser
chmod 6111 /usr/lib/apache/suexecdir/cgiuser

Use newcgi.sh to set up the suexecdir binary for other users.

Patch mod_cgi.c with the patch file, patch-cgi-1.3.26-2. E.g.:
cd apachedir/src
patch -p0 < patch-cgi-1.3.26-2

Make sure that /usr/lib/apache/suexec does not exist. If it does, apache
will try to use its standard suexec feature and that'll cause all sorts of
havoc.

You'll also need to create some .apache-suid files to specify what's allowed
to run. The overall control file goes in /etc/apache/apache-suid. The one
for cgiuser goes in /usr/lib/apache/.apache-suid. The one for each user
goes in ~user/.apache-suid. CGI programs will only run if they are allowed by
both the user and the overall control file. The apache-suid file included is
intended for use in /etc/apache/apache-suid and offers a sample
configuration.

