TA is wrong on linuxSolved

We're continually improving our client-side fraud detection (as well as server-side fraud-detection).

First, make sure you're using the latest version (currently 4.0.9.6).

The next version of TA (4.1.x) includes even more client-side fraud detection.

Hi Wyatt,I'm using the latest TA.

were you aware of linux error?because from my side, I've spread version of my app that users could activate forever....

did you succeed in reproducing the wrong behavior on linux?

best regards,Nicolas

Yes, in TA 4.1 (out soon -- no hard date yet) we resolve issues in certain configurations of certain Linux distros to improve client-side date/time fraud detection.

if you have told that before I wouldn't have release linux version of my app.

there's no hard trick/fraud in setting computer's date one year before...

Theres always a new release around the corner. Thats just the nature of software. When we release 4.1, include it in your app, and release a new version. Ditto for all new releases.

There are only benefits to using the latest versions of our software (less bugs, more features, speed optimizations).

no doubt about using new releases...but it will surely not be the point of view of people that can now use my app for free.because it also happen for verifed trials... I normally set 30 days for free and a user have reported 599 days for free

Yep, the upcoming 4.1 release thwarts those malicious customers that are *that* devoted to cheating software companies that they "freeze time" on the system (which causes other problems -- but malicious people are malicious).

Hi,would it be possible to list all linux activated licenses of my software and all linux verified trials to disable them in one shot?

thanks,++

Nope, we don't currently have the ability to search for product keys based on what platform they were activated on.

you doesn't help me a lot....

Hi,any news about upcoming TA 4.1?

thanks,++

No hard date. ASAP.

Hi,it's been more than a year that I'm waiting for a fix for linux...any progress on that?

best regards

Yes, it's coming soon. We don't release dates for a reason.

The latest TA is out and we've solved real world fraud as well as "cooked-up" experiments.

Hi,yes it seems to work fine now.thank you and congrats for your new release

++

Hi,I have a weird case on linux with a key that is outdated (ending on 2019-01-31).the user is running linux on a usb stick (linux mint) and got 24 days of trial. that's ok, as I allow my app for 30 days trial.if the user set the date of his computer to 2019-01-01, he's able to activate the key .. ?!?!I would expect this not to be that way... he shouldn't be able to activate the key...

is this because of the remaining trial days?

best regards,Nicolas

What you set in custom license fields has no effect on TurboActivate. It doesn't read them. It doesn't interpret them.

If you don't want a user to activate a key, revoke it. You can do this in the interface or in the web API.

Hi Wyatt,

unless revoking the key (which can be a pain...), there's no other option?TA cannot detect a wrong computer date?also, revoking a key also means that users cannot use "their" key anymore... if they want to pay again and reuse the soft.

++

>> "TA cannot detect a wrong computer date?"

Yes, it can. See https://wyday.com/blog/2019/turboactivate-turbofloat-4-1-trial-fraud-protection-nodejs-freebsd-support/

...and the thousands of forum posts that we responded to.

You're asking about custom license fields.

TurboActivate doesn't care what you put in those fields. It doesn't try to interpret them. That's your job.

If you want to revoke software than revoke the key. We have a mechanism for that. Use the LimeLM interface (click revoke key) or use the LimeLM web API.

the link you 've shared is about trials, I'm talking about a key that is expired... really... and at some point TA could not detect it.It's not my job to detect fraud!! it's TA's job !!

I do use custom fields !!my app is checking for custom fields to detect when a key expires, and that is ok.but when user set his computer's date to 10 years before the date in the custom field, TA says the user can use the key for 10 years ! and that's not what I expect.

I expect TA says:"Wait... your computer is set at year 2010? there's something wrong!! I won't activate your licence key"

hope I'm clear.

++

The trial system and activation systems are completely separate.

TA_IsDateValid() does only rudimentary fraud checking. It is not designed (and will never do) complex client-side fraud detection.

If you don't want a customer to use a key, revoke the key. As I said 2 times already:

1. Revoke it from within LimeLM

or

2. Revoke it from your back-office code using the LimeLM web API: https://wyday.com/limelm/help/api/limelm.pkey.revoke/

Those are the solutions to your problem.

ok,then new case:a key is valid till 2019-12-31.users set his computer date to 2010-12-31 and will be able to use the key for 9 years...

how can I prevent that?

++Nicolas

Revoke the product key.

I will not revoke a key valid until 2019-12-31 !!if the user buy the key 2019-01-01 for 1 year, and set his computer date to 2010, he can use my app for 9 years.I hope to be clear.

thanks

Well, thats not true. Because youll call IsGenuineEx() and after x + y days they will no longer be able to use your app regardless of what they do with their system clock.

So, revoke the key.