As far as I remember you don't necessarily need to define an AddHandler.
There are several ways in Apache to enable the executaion of CGIs.
The most straight-forward whithout much ado is to declare a directory as ScriptAlias.
Then anything within this directory would be considered as CGI executable.
Another way of CGI enabling would be to add an ExecCGI Option within a Directory container.
Then you either have to SetHandler cgi-script
or AddHandler along with file extensions.
The Sethandler would function like the ScriptAlias within that directory whereas the AddHandler would work like a file match on extensions.
From a security point of view I would consider the ExecCGI and SetHandler to offer a finer grained control.
There's no need to search the Internet because the Apache docs are explicit enough, and it is all much better put there than I could repeat here.
http://httpd.apache.org/docs/2.0/en/howto/cgi.html As for your problems with shared libs I would want to ask you if you are operating your webserver in a chroot jail?
Chrooting, especially with dynamic content can be quite tricky but there are plenty docs describing the necessary steps.
e.g.
http://penguin.triumf.ca/chroot.html However, if you merely were serving static contents probably the easiest was to install mod_security and use its chroot facility
http://www.modsecurity.org/documentation/modsecurity-apache/stable/06-special_features.html#N108BE
Madness, thy name is system administration
