Right, but as in Perl, context matters :-)

"The encryption extension is no Shared Object (not an .so file, but an .a file, and running it with a Perl executable different from that one provided with the extension ends up in 'Can't find shared object file for ... in @INC') ... "

So apparently, someone linked the encryption extension statically with the Perl executable to make it harder to reverse engineer. Now why would that fictive person ship this super secret decryption code along with the rest as a separate .a file? To make it easy for everyone to relink it with a perl patched to dump the cleartext code? Only fools would do that.

___

"The secret to creativity is knowing how to hide your sources." - Albert Einstein

Only fools would do that.

Not fools, just the ignorant. If you don't know why EU::MM installs the library for static modules, you probably won't suspect that it does so. And even if you look over the list of files you are distributing, it may not occur to you that that library has your module's code, not just some kind of binding layer for it.

I'm looking for a job.

#!/usr/bin/perl print "\n* Perl2exe Perl sourcecode revealer test code\n". " by Thijs (Thice) Bosschert\n". " v1.0 17-06-2012\n\n"; # Comment: This is a test comment print "\n* This is just a test line.\n\n";