Against Unauthorized Use (OpenInsight 32-Bit)
At 06 SEP 2010 08:51:43PM Edward Chan wrote:
What are the available options to put into our application run time copy so that user can not share their copy to the unauthorized users?
At 06 SEP 2010 09:45PM [email protected]'s Don Bakke wrote:
Edward,
Can you be a little more specific? Do you want to authenticate against the Windows login? Do you want to prevent access to a session that has been left running? Do you want to prevent multiple simultaneous logins using the same credentials?
All of these are possible (especially if you use 9.2) but they all have their own method for implementation.
At 07 SEP 2010 05:31AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
Or conceivably prevent unauthorised distribution of the software by locking it into the machine name or similar as referenced in the Sprezzatura blog?
World leaders in all things RevSoft
At 07 SEP 2010 08:54PM Edward Chan wrote:
Thank you very much for the solution. May I ask another question? Is it possible to prevent unauthorized distribution of the software within the same hard disk in the server by locking it into the folder of the hard disk?
At 07 SEP 2010 09:13PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
Given that you are encrypting the machine name in the registry there is nothing to stop you adding the folder name to the machine name before encrypting then adding drive() to the check.
World leaders in all things RevSoft
At 07 SEP 2010 10:24PM Edward Chan wrote:
Thank you very much.
At 08 SEP 2010 04:21PM Jim Vaughan wrote:
We use this http://www.crypkey.com/products/sdk.php