Our own home rolled scheme relies on the customers email address as the
first part of the key.
So, a customer has to enter their email address, then the regcode. If they
want to share the app, they need to share their email address. This has a
couple of intended consequences. First, I think a custo
Thanks to everyone for the thoughts on this. I agree that you can never
100% prevent piracy from those who are determined enough and can waste a lot
of time and effort trying to do so. I guess that's a plus for Zygodact - I
buy the product, spend perhaps a couple of hours doing whatever
customisa
On 7/18/11 2:43 AM, Tiemo Hollmann TB wrote:
As I understand Zygodact, or Peters or Shaos approach the user can pass on
his "name, etc." and the generated code to everyone else to unlock the
software.
How do you handle this issue? Is it just something "as is", is this scenario
so negligible in y
You could include (without telling the user) the contents of $user as part of
what is inputted to generate the code. This would make it more secure but cause
problems with portability, etc. I agree with the later posts pointing out the
trade-offs between security and user-frendliness. Consider y
Gosh! Sorry Sean for having put you into the wrong country, should have had
a look on google maps :)
Nevertheless the Japanese women showed a great contest here in germany...
Tiemo
> -Ursprüngliche Nachricht-
> Von: use-livecode-boun...@lists.runrev.com [mailto:use-livecode-
> boun...@list
First: Congratulations to Shao to the winner of the FIFA womens soccer world
championship: Japan!
As I understand Zygodact, or Peters or Shaos approach the user can pass on
his "name, etc." and the generated code to everyone else to unlock the
software.
How do you handle this issue? Is it just som
