Re: system signature?

Long story short: you're wasting your time.

It's trivial for a well-informed person to copy your code. If you don't trust these people, you shouldn't be working with them.

There are no technical ways to make your code safe, as it must execute on the host system. Work with good people, write contracts (if you must), and move on...

Update: I forgot to mention, if perl2exe works like PAR does (which I think is true), did you know that you can open that .exe file with WinZIP? Please, spend your time on productive things.

Comment on Re: system signature?

Replies are listed 'Best First'.
Re^2: system signature? by xmerlin (Initiate) on Jan 13, 2006 at 09:45 UTC
Is is more than a trust issue really. I do NOT know the people who are going to do the tests and secondly it is a non-commercial program and I do not want people to make money from it. I am already considering of splitting the program into several seperate working testable functional units. It will not be possible to "glue" them together, so nobody will have the entire working copy. That way the risk of someone "stealing" my work and making money from it will be averted (I hope).	[reply]

Replies are listed 'Best First'.

Re^2: system signature?
by xmerlin (Initiate) on Jan 13, 2006 at 09:45 UTC

Is is more than a trust issue really. I do NOT know the people who are going to do the tests and secondly it is a non-commercial program and I do not want people to make money from it. I am already considering of splitting the program into several seperate working testable functional units. It will not be possible to "glue" them together, so nobody will have the entire working copy. That way the risk of someone "stealing" my work and making money from it will be averted (I hope).

[reply]