TurboActivate 3.3 is coming soon. We're finish the features now. Is there something in particular you're waiting for? If so, I can tell you how to do it with TA 3.2.2.
TurboActivate 3.3 is coming soon. We're finish the features now. Is there something in particular you're waiting for? If so, I can tell you how to do it with TA 3.2.2.
1. Checking revocation securely (don't want to do this myself as you said TA would handle this)
2. Preventing users using VM's to bypass security
3. Preventing users from substutuing fake TA files to bypass security
1. Checking revocation securely (don't want to do this myself as you said TA would handle this)
That's correct.
2. Preventing users using VM's to bypass security
This will also be included. It's something we're all particularly proud of (it has been a long time coming and a massive amount of work).
3. Preventing users from substutuing fake TA files to bypass security
You have to handle this yourself. Either use the static library version of TurboActivate, or verify the Authenticode signature of TurboActivate.dll before letting the user continue with your app.