![]() ![]() Well, you end up in a catch 22 situation. All they do is to get the tools that allow them to implement a relatively secure system (within the boundaries pointed out in Peters answer).What is the problem with copy protection in general? If a software uses mathematically sound encryption for its licensing scheme this has no bearing on the security of the copy protection as such. User276 already hints, in part, at what the problem is.Many software vendors think that they purchase some kind of security for their licensing model when licensing a dongle system. Given that I have - without publishing the results - 'cracked' two different dongle systems in the past, I'd like to share my insights as well. Clearly Peter has addressed the main points of proper implementation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |