Setting aside opinions on copy protection and licensing, suppose I wanted to
implement such a scheme.
The key itself might be a network license, or an encrypted file containing
license info and system-specific info. But the real issue is how to protect
the code that accesses the key. I know
On 10/12/05, Jonathon McKitrick [EMAIL PROTECTED] wrote:
Setting aside opinions on copy protection and licensing, suppose I wanted to
implement such a scheme.
The key itself might be a network license, or an encrypted file containing
license info and system-specific info. But the real issue
On Wednesday 12 October 2005 05:42 am, Jonathon McKitrick wrote:
But what techniques could be implemented within a library or archive that
would make it difficult for someone to trace the algorithm and/or make
changes to the code to remove the protection checks?
There is none. The closest
