'Protecting' Perl Code?
An anonymous reader asks: "Ok, so here is the scenario: my company has some software that is used internally and it is written in Perl. We now need to put this code on a server that has 'public' access (it's a university machine). We provide root access to the system for the purpose of learning, but we need to keep the code from being viewed or edited. Is there anything to do besides the 'perl2exe' and the ActiveState compiler? How effective are those really at protecting code?"
CHMOD?
..and it's called "Perl". You don't need to do anything at all for your code to be unreadable.
That's nonsense, don't listen to this guy.
Look, just to show how nice we are, why don't you upload it to my FTP server, give me the root password and IP of this machine, and I'll take care of the rest.
<xml><I><am><so><damn>Web 2.0</damn></so></am></I></xml>
Perl is already Tolkienized -- just look at the start of every source file!
What, do you have to run it on a Tolkien Ring network instead of Ethernet?
"One Ring to rule them all,
One Ring to find them,
One Ring to bring them all
And in the darkness bind them."