Dear Cornholio,
If a user cracks the hasp_update executable file to get the vendor code string, he can only perform the read only operation on any existing license (like collect c2v or fingerprint, login/logout to existing license etc).
There is no way that a new license can be generated or existing license terms can be modified.
So there is no risk of unauthorized license usage.
hasp_update tool is just a normal executable that implements our API's.
There is no other layer of protection to prevent cracking of executable file. This is because the API's provide solution only for licensing and not protection of any kind.
You can protect the executable using envelope to prevent the cracking. However, it would require a license key (HL or SL) to open the file. You can provide a provisional license for this purpose to allow the customer using the hasp_update tool on a fresh machine.
Note: The "hasp_update" tool is only a sample tool. You can also implement the similar functionality in your actual application and then protect it using envelope.
For more detailed explanation, please drop us an email on Support@SafeNet-Inc.com
Thanks,
Ashish