Regarding your new "encryption" requirement, well good luck...
You seem to believe compiling Perl code makes it unreadable, but I can instantly think of at least three different approaches to deparse op-trees held in memory.
Personally I'd leave the decryption to the hook.
If you are afraid that the decryption key could be read from memory, switch to a algorithm which encrypts the key.
Since your approach is based on secure op-trees, this would be "safe" too. (read: not any more unsafe)
Cheers Rolf
(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery
FootballPerl is like chess, only without the dice
In reply to Re^5: use of already eval()ed module (from string)
by LanX
in thread use of already eval()ed module (from string)
by bliako
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |