I'm not sure whether this is the most appropriate newsgroup, but anyway...
We've been asked by a client to develop a method of license enforcement
for some software they've developed and intend to sell. Their software
is an Access app ( yeah I know ... not particularly secure, but they are
the customer ) but we intend to build some OCX objects, maybe in Perl,
and re-use parts of it in later projects in Linux.
I'm currently researching our alternatives. I have NO experience in
this, so if I say something stoopid, go easy OK?
I've already checked out some commercial implementations - none of which
are cross-platform - which isn't necessary but is a big one of our
wish-list, so I'm now looking at the option of doing it in-house.
I've pretty much decided to use a product-activation scenario, where an
installation ID is made from a combination of hardware IDs and some
other stuff we can pull from the system. This will be encrypted and sent
to the license provider ( eg via email / phone / something ) and an
encrypted activation key will be created.
Some issues with this system are:
- hardware changes mean they have to re-register ... a possible solution
is to only use the motherboard ID ( which isn't likely to change without
a re-install anyway ), though this may not be unique enough.
- users don't like product activation. I can see their point here...
Any comments / suggestions? I have done a pretty extensive search of
groups.google.com and found almost nothing on the topic.
Am I approaching this the right way?
Thanks for any help!