in reply to Re^5: Automatically Converting Perl to C
in thread Automatically Converting Perl to C

OK, then what would you suggest as being the best security solution to my problem? I need to look into a tech solution, and unfortunately the particular niche I am working in needs more protection than the "non-technical solutions" that Dave kindly suggested in this thread. Also, the constraint that I have right now is that an executable needs to leave my hands, I cannot at this point keep the exec on my machine ans allow remote access through an API...
  • Comment on Re^6: Automatically Converting Perl to C

Replies are listed 'Best First'.
Re^7: Automatically Converting Perl to C
by ikegami (Patriarch) on Apr 05, 2010 at 02:09 UTC

    I need to look into a tech solution

    The iPad was jailbroken the day after it was released. Do you think you're better than Apple? Tech solutions do not fix broken business models.

[reply]
      > Do you think you're better than Apple?

      Do you think the motivations to unveil his "secrets" are comparable?

      I mean if you hide your sources on the moon, it's also not safe, since NASA could launch a mission to steal them... :-)

      From my observation, for most people talking about obfuscation, erasing all comments already efficiently destroys any motivation to reuse their code...

      Cheers Rolf

[reply]

        I mean if you hide your sources on the moon

        The user can't execute the program that's on the moon unless they are there too, in which case they don't need a NASA mission to steal its secrets.

        Do you think the motivations to unveil his "secrets" are comparable?

        Every case is different, but not really. The only secret an application can keep is the one noone cares to look for.

[reply]

In Section Seekers of Perl Wisdom