Host the code as a service on your own machine, and only distribute code that gets the required parameters and data from the user.and connects to your machine to have it do the work Ship the answers back to the user. Make sure the hidden code uses taint and avoids string eval.
| [reply] [Watch: Dir/Any] |
Hi,
see perldoc -qhide,
Cheers, Christoph | [reply] [Watch: Dir/Any] [d/l] |
| [reply] [Watch: Dir/Any] |
Acme::Bleach
----
I Go Back to Sleep, Now.
OGB
| [reply] [Watch: Dir/Any] |
Write it inside <pre>...</pre> tags and make the sentence really long so whatever you're trying to hide falls off the right edge of the internet. Nobody will ever find it there (or, see Markup in the Monastery).
Alternately:
- In the cookie jar.
- In a magnetic keyholder in the mailbox.
- Out on the back 40, under the 4th pole from the west end.
You can put it there (for any selected value of "there") between executions...
| [reply] [Watch: Dir/Any] |
Here's a good way to go hide: #!/usr/bin/perl
use strict;
use warnings;
use Devel::Hide qw(Hide::ThisModule);
require Hide::ThisModule;
Seriously, see How can I hide the source for my Perl program?. | [reply] [Watch: Dir/Any] [d/l] |
If it is really important, compile critical pieces into a C dll and call from Perl.
A C dll can be reversed also, but it takes more time.
If you need still more anti reversing built in, there are tools that can make reversing object code much harder. You can use those in conjunction with your C dll.
If it is really, really important for the reverser, they will reverse anything you do. You are just increasing the time and expense for them to reverse what you do.
At some point you have to consider whether the effort you put in anti reversing is more gainfully spent in adding features to your program
Reality:
Legal solutions are out of reach of most small businesses in USA.
No one gives a rat's ass about the legal notice you put on your program in large parts of the world.
Best wishes
Sanjay Mishra
| [reply] [Watch: Dir/Any] |