Hi there, one of our clients reported they were able to bypass the protection. They basically cloned the hard drive from an offline activated machine, put it onto a new machine, and it works for the first time.
We already disabled activations for virtual machine.
Some additional information:OS: Ubuntu 18.04environment: PythonI'm actually not sure about the version of `libTurboActivate.so` that we are using, but it should be the latest version of last August. I can send you the file if necessary.
I spoke with a person over the phone call this morning, he asked me to gather additional information, my question is what is needed?
Start here: https://wyday.com/limelm/help/faq/#useful-reports
Version numbers for everything. Also, product keys, etc.
Also, ensure the customer was not activated on a virtual machine to begin with (i.e. you didn't disable VM activations after they already activated on a VM).
We can't reproduce this behavior on real machines. We *can* reproduce this on VMs (which is why your should *always* disable VM activations and use TurboFloat).
sha256 sum of libTurboActivate.so: 42ac974245e61a988be9e967d4b2f48e751f701a69222b6a16bcc63f6c2e1fa2
here is our product key https://wyday.com/limelm/version/6280/, we did not enable virtual machine activation from the very beginning.
system version: Ubuntu 18.04architecture of machine: x64
would it be helpful to get ActivationRequest.dat files from our client as well?
Wyatt wrote:> Start here: https://wyday.com/limelm/help/faq/#useful-reports> > Version numbers for everything. Also, product keys, etc.> > Also, ensure the customer was not activated on a virtual machine to begin> with (i.e. you didn't disable VM activations after they already activated> on a VM).> > We can't reproduce this behavior on real machines. We *can* reproduce this> on VMs (which is why your should *always* disable VM activations and use> TurboFloat).> > https://wyday.com/limelm/help/vm-hypervisor-licensing/
Ok, that's not the latest version. Use the latest version.
Also, tell us the product key used (you linked to the version).
the product key used was [SNIP]
are you sure using the latest version would solve this problem? this version is basically one latest version from last August, could you check internally if you have a fix for this problem since then?
they were able to reuse this product key [SNIP] in a brand new machine discussed above,
the client was being honest and deleted the activation files, and reactivated that machine with [SNIP].
Maybe we can compare the activation requests for these two keys and see if they have the same machine information?
I have emailed you separately offline ActivationRequest files from two separate machines since i'm not able to upload attachments here.
We're looking into it. We'll get back to you tomorrow.
Thank you. Additional information: storix (https://www.storix.com/) was used to clone the drive.
Hi, do you have any updates? Thanks
Still investigating. Well update this topic when theres an update.
Hi there, do you have any updates regarding this issue?
This Linux-only bug will be fixed in an upcoming bug release.
