How do we automatically invalidate keys which count execution count?
Is it possible to reuse (reenter) the keys?
Reuse old keys?
Re: Reuse old keys?
Hi sanyock,
There are no ways to force keys to expire, not by execution not by anything else.
Re-enter the key - of course, that's possible. Use Enigma API for that. To force protection to accept new key, just check and save it using api EP_RegCheckAndSaveKey or combination EP_RegCheckKey and EP_RegSaveKey.
There are no ways to force keys to expire, not by execution not by anything else.
Re-enter the key - of course, that's possible. Use Enigma API for that. To force protection to accept new key, just check and save it using api EP_RegCheckAndSaveKey or combination EP_RegCheckKey and EP_RegSaveKey.
Re: Reuse old keys?
Then I guess a key can be invalidated by custom program having its own database of local blacklist in a cryptoapi storage?
Such key can be reused only after reversing NTFS state to a saved checkpoint or reinstall Windows which is ok as any time consuming operations are treated as inacceptable for customers who have money, willing to pay and save their valuable time.
Such key can be reused only after reversing NTFS state to a saved checkpoint or reinstall Windows which is ok as any time consuming operations are treated as inacceptable for customers who have money, willing to pay and save their valuable time.
Re: Reuse old keys?
Sure, any own customization can be made there. Just in case, there is a plugins system that may hook key saving/loading functions, you may use this hook at license load and return or do not return a key in case it is invalidated.