Gee, I was just about to ask a very similar question. I will be most interested in what the other monks have to say.
I will add that putting sensitive information within a module's source is a really, really bad idea. Any user of the system can run 'perldoc -m' and get the full source code of the module, in which case 'all your password are belong to us'. :-(
My question is, would it be a good idea to put the sensitive information in a separate file in the directory alongside the module, use "do" to slurp it in, and restrict permissions accordingly -- or would it be safer to put that information somewhere outside the perl library tree entirely, such as /etc (or /usr/local/etc)? I would think putting these things outside the Perl library tree will wreak havoc on the build process, though.
