Please do not place too much stock in the "security" you may think you have achieved using Acme::Enc. See posts like Close Perl Code (similar posts can be found, Super Search is your friend) which highlight this point. Also, if you do not want to display things on a web page, why are you including them in the data which is returned to the browser?
Don't depend on obscurity for security. It goes against everything the people who made perl, ssh, the modules you're using- believe in.
It's not about morality- It's just poor practice. You will ultimately end up introducing new bugs, making your program slow- turning off anybody who may want to help- including the community and your co-workers! :-D
I know it seems counter intuitive. But- do you like perl, apache, firefox, etc? These things work partly because it's not about hiding code. Making the conversion of philosophy from hiding things- to showing everything- is hard but you will grow and become stronger. Your stuff will work better and be more secure also.
If you must 'hide' things- "hide" config files with precious db acces parameters, etc- by chmodding them so only you or our software can read them. Your script in /home/myself/public_html/cgi-bin/precious.cgi could use YAML to read a config file in /home/myself/not_inside_webshare/precious.conf
Here, check this out, about security through obscurity. Obviously I want you to read the part that says 'arguments for'.
Also skim through some of this interview with Stallman, and some of the gnu ideology, it may energize you and inject you with ambition and good energy.