Hi Dmitry
It is very difficult for me to understand some of your points 

>> At some point when the program checks for registration Key/File  it will for 
>> example set a boolean variable to true. Do you do it other way?

>Yes, the main points are:
> -inline keychecking func
You mean having all the code in one function in a .h file?


> -NEVER display any alert or dialog on correct/incorrect key being
entered, this is trivial to find
I'm fine with this

> -use many many function pointers in structured for keychecking. >Makes
>it harder to follow the code.
[Please explain]


> -If your app is 68k, do a check if it's in the simulator/emulator and
> in that case always be "Registred" to make it harder to use those tools to 
> hack it
[I can do this and indeed is very clever.]



>> Is it possible to check if my program is modified and prevent it from 
>> running?
> Anything is possible :)
>What Ryan suggested works, but is not too hard to circumvent. >Instead
>you can include RSA public key in your app's code section [preferably
> obfuscated], and then sign it, storing the signature in a different
>resource. Sign the app when you release. This way nobody can easily
> re-sign it without having your private key. Also, do not refuse to run
[I don't know how to do this]



> Also when you do do the checksum, avoid doing things liek
> DmGetResource('code',...). the constant 'code' will stand out in
> the disassembly. Instead just do something like:
> for(i = 0 ;i < DmNumResources(myApps); i++){
>   uint32 type;
>   uint16 id;



Do you have any source code to share in exchange for a free license to my 
program?
http://www.youtube.com/watch?v=9WQkDyb2Nds


-- 
For information on using the ACCESS Developer Forums, or to unsubscribe, please 
see http://www.access-company.com/developers/forums/

Reply via email to