Hello
I have a [Perpetual] and [Expiration Date] type feature in my product.
I use the product to create a SL-UserMode license
When I do hasp_login() for each features, I expect the following status
1. HASP_STATUS_OK
2. HASP_FEATURE_EXPIRED
3. HASP_TIME_ERR
4. other status
To my knowledge, for Perpetual feature, api does not return 2(expire) and 3(time_err) status
For [Expiration Date] feature, 2(expire) and 3(time_err) are both possible.
To test this, for Expiration Date feature:
a. If I set the computer date to a far future date, I get 2(expire) as expected.
b. Then If I change the date back within the expiry date, I get 1(ok).
c. If I repeat a and b many times, I still do not get 3(time_err). When the date is set within expiry date, the Expiration Date feature returns 1.
d. After each computer date change, I reboot the computer.
My question is
1. Is it sure that the Sentinel LDK detects that the user has tried to tamper the computer time for Expiration Date feature in case of software license?
2. I mean I just want to make sure that the user cannot use the [Expiration Date] feature simply by reverting the computer date for software license.
3. Is this behaviour that I am getting(not gettting HASP_TIME_ERR status even though trying to tamper time) because of the presence of Perpetual feature in the product?
Thank you