Quote:
Originally Posted by AttonRand
Coders trust so much protectors that they feel secure just by enabling some/all features which the protector offers.
Most of them doesnt even care about using code markers in their source thus making unpacking very easy and cut off 50% of protector power.
|
It is most useful and correct advice to my mind. Many people buy a protector, simply choose input and output files and click protect button. After some time they become amazed to find a cracked executable of own software. Probably the most unpacked programs are not a weakness of protection systems but the lazy of software developers.
Simply spend a whole day for protection implementing and you will get good results.
Quote:
Originally Posted by AttonRand
My advice: develop your own registration procedure, add some asm tricks to your app and pack it using code crypters.
|
Disagree regarding this... If you are not well in cryptography then you could make many errors applying own registration, that could be bypassed and keygened. Registration routines of protectors are much stronger and do not have mistakes (not sure about all protectors of course
)
Regarding asm tricks - also disagree, some tricks could work on 50% machines, but for another 50% you will get a crash. It is really better to use protectors that had been dozen times tested on dozen machines..