stitution-wide authentication system that's imple-
mented with a PerlAuthenHandler). But we certainly don't want giving
them that sort of access to open up a floodgate by allowing them to exe-
cute arbitrary Perl code on the server - unless we say so (e.g., by giv-
ing them ExecCGI permission
Auth::Module
(I don't want to have to create blocks for everyone who
wants to use a local auth module.)
Or is there at least a way to log what's going on in such a way
that if something bad does happen, it's easy enough to figure out
who the culprit was?
--
Richard Goerwitz
PGP
