![]() Greater than the value of the application. All you can hope for is to raise the bar high enough that cracking your program is not worth the trouble - to make the effort of cracking Should I catch up to that? Do reassure me if they're really "can't be bypassed"! Thanks!Ī determined attacker will be able to bypass whatever protection you can come up with. Just asking suggestions.īut I'd been thinking lately, crackers/hackers do get smarter, would one day, they would be able to bypass these protections oneĭay? I know there a lot of tips in the first guide, but "if" one day, crackers do find a way to getting into an application, how Among them, I also found some articles saying that applicationĬompiles with a debugging symbol that allowed crackers to make use of them.īut no matter what are the methods behind software cracking, are there any ways to prevent things from being debugged or de-assembled by them in the term of coding? I'm not really asking a question here. I'm not a cracker, nor do I want to be one, but I can see that it isn't really hard to squeeze informations from the application. Though, I'm not really very sure how this is going on, so I wouldĪppreciate if someone would correct me on this.īecause of this fact, I tried debugging my own application. Though I didn't want to go to theĭetail to keep my hands clean, as far as I read, a cracker have to "reverse-engineer" the application to crack it.Īnd as far as I know, this is done by using debugging programs or an interactive disassembler to either "debug" the application and modifying it or decompile the application straight-away. ![]() ![]() ![]() I'd been spending time to kinda "researching" how people crack software. But I'm getting very concerned about this matter. I am probably no-fit to really discuss a topic and I may have also posted in the wrong category. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |