a little guidance for protecting a DLL please

Hi

We plan to protect a DLL. The DLL is called at high frequency (many times per minute) by a commercial 'host' application to which our DLL adds additional functionality using run time linking. The licensing model for our DLL is node locked and time limited.

We're totally clear on the activation process, setting up keys and fields to meet our model.

What we'd appreciate some guidance on is given that our DLL will be called many times per minute, how do we prevent calls to the licensing server happening each time our DLL is called yet still enable checking upon first load of the DLL?

Thanks

BD.

Well, you shouldn't be contacting the server even on every launch of the DLL / App / Tool / Whatever. That's why TA_IsGenuineEx() exists -- namely, to contact the server every X days with a grace period of Y days.

See: https://wyday.com/limelm/help/using-turboactivate-with-c-plus-plus/

Regarding when to do this checking, it depends on your DLL design. Presumably a customer will be using your DLL in an app, and that app will be running for some period of time.

So, basically, use the C example as-is. Namely, do the bulk of the licensing stuff during the "init" call to your dll (presumably you have to set stuff up once before other calls are made).

Reply
Discard post