Actually, I’d say make the key file consist of several different encrypted blocks that are dealt with in different places. You want the cracking to be a dull repetetive task rather than out and out hard. And if you make some tests inactive until a certain date it makes it even worse. The point being that you can end up with hacks and key gens that seem to work, and the cracker has to test every function in the software in order to be sure. That’s very time consuming to hack, and the multiplexed key makes it hard to make a keygen. So you end up with many different looking test segments, spread all over the binary. If you make your tests in the form of inlinable functions in a globally accesible module it’s not too time consuming. Then test the different elements of the key at different places in the code.ĭo a test in every non-time critical function in the code. Use a multiplexed key, which is to say many independent keys baked into one. Instead of a serial you might want to go with a key file. So if your target audience is in the amateur audio/music field I’d say don’t use PACE. It works well in many cases, but since it works on the driver level it has the capacity to severly fuxxor a system, and does so from time to time judging by the testimonials. PACE is an object og hatred in the audio community.
0 Comments
Leave a Reply. |