There is actually no protection at all.Non programmers might perhaps not be able to open the file and read it, but then again even if they read it, they would be none the wiser when seeing the Perl-code as they are non-programmers. Every programmer who knows a little bit of Perl can decode it in less than 10 minutes probably. it has been said time and time again: the only protection of your valuable code lies in strict legal licensing terms. Why do you think all the big software companies employ whole tribes of lawyers and add an EULA to every piece of software?
CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James
| [reply] |
If Acme::Bleach is sufficient to protect your code from the people you're giving it to (considering you have to have a use Acme::Bleach line sitting in it) then it'd probably be simpler to just give them the original code along with a box of some bright shiny objects and tell them to just look in the box whenever they want to look at the code.
Hrmm, Ogg want know how code work. Ogg supposed to look in box of . . . OOOOOhhhh shiny . . .
The cake is a lie.
The cake is a lie.
The cake is a lie.
| [reply]
[d/l] |
Well, someone interested in the source in the first place, would probably also possess enough savviness to figure out what to search for... — in particular as it says use Acme::Bleach; at the top of the bleached script :)
| [reply]
[d/l] |