Best way to protect my new commercial software.

[Paul Boddie]

On Dec 10, 9:55 am, farsheed <rodmena.... at gmail.com> wrote:
> Thanks. But I ask this question technically, I mean I know nothing is
> uncrackable and popular softwares are not well protected. But my
> software is not that type and I don't want this specific software
> popular.

Understood.

> It is some kind of in house tool and I want to copy protect it. this
> is very complicated tool and not useful for
> many people. indeed this is an animation manging tool I wrote for my
> company. So if you have any idea that what is the best way to do it,
> I'll appreciate that.

I'll state my agreement with the opinion usually given when these
kinds of questions are asked: that determined people will find a way
to run software if that software is distributed, and running software
as a service is probably the only reliable way of concealing your
code. If your code is in-house, there might be numerous dependencies
on in-house services that would make the code useless to an outsider,
and you could consider exploiting this aspect of your software.

See this recent thread on this subject:

http://groups.google.com/group/comp.lang.python/browse_frm/thread/d00c8926c0da7df0

This is very much a frequently asked question (the last thread
appeared about three days ago), so I've tidied up a Python Wiki page
dealing with this topic:

http://wiki.python.org/moin/HowDoYouProtectSource

I trust this provides some answers.

Paul