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

Now you're clearly talking "security by obscurity."

Obscurity isn't security.

  • Comment on Re^5: Automatically Converting Perl to C

Replies are listed 'Best First'.
Re^6: Automatically Converting Perl to C
by blueberryboost (Novice) on Apr 02, 2010 at 16:01 UTC
    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...
[reply]

      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]

In Section Seekers of Perl Wisdom