Yes, exactly. But they see big fat dollar signs. Every day wasted loses them more than I earn in a year and if a competitor beats them to it they'll be jumping off ledges.

So do you think I have a chance of beefing up the perlapps a bit?

I personally have never really considered how to crack a perlapp and maybe that's the question I should have asked.

It seems to me that the crux is likely to be - Does the perlapp need to be run to be cracked (I'm assuming yes) and if it does will it be run and controlled or run and observed. If the instructions are encountered sequentially and observed then I have a chance of making a right pain in the *** of myself for any attacker. If it is not processed sequentially or is stepped through like a debugger - under human control - I am probably powerless to hinder them more than once, if that much.

What I really need is another month but it isn't going to happen.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.