[Help] Reverse Engineering.
[Help] Reverse Engineering.
Can Somebody Show Me How To Decompile/ Reverse Engineer A Dll So I Can See It's Source Code?
I Want To Remove A Feature Of A Hack I Downloaded From The Internet..
I Want To Remove A Feature Of A Hack I Downloaded From The Internet..
Originally Posted by chriscasper
Can Somebody Show Me How To Decompile/ Reverse Engineer A Dll So I Can See It's Source Code?
I Want To Remove A Feature Of A Hack I Downloaded From The Internet..
I Want To Remove A Feature Of A Hack I Downloaded From The Internet..
You cant decompile. When you view a DLL it will be in ASM language.
yes i know. and the language scares me.
and suicide is nothing to joke about. grow up.
and suicide is nothing to joke about. grow up.
Originally Posted by chriscasper
yes i know. and the language scares me.
and suicide is nothing to joke about. grow up.
and suicide is nothing to joke about. grow up.
Hmm how do i put this....
Impossible
Impossible
Originally Posted by whit
Hmm how do i put this....
Impossible
Impossible
cause my friends dad is a computer programmer and i asked him and he said "im not helping with little teenager hacks, just ask somebody about reverse engineering and do it that way." 
Originally Posted by chriscasper
are you sure? cause my friends dad is a computer programmer and i asked him and he said "im not helping with little teenager hacks, just ask somebody about reverse engineering and do it that way."
cause my friends dad is a computer programmer and i asked him and he said "im not helping with little teenager hacks, just ask somebody about reverse engineering and do it that way." Not for C++ for sure
Originally Posted by whit
Yea sure you can view the asm instructions but not the source its self..
Not for C++ for sure
I'm not gonna take a stand on the leaching thing, because he just wants to know how to reverse engineer something. I don't care what that thing is. I only care that he wants to learn how to do something. And I place knowledge first on my list above morals or consequences or anything else, knowledge should be shared even if it was my own hack I would explain how, though I wouldn't give him specifics, he would have to actually apply the knowledge himself. At that point it becomes immoral, but not before, only once he has both the will and ability and acts upon it.
To remove something from a program, first you need to know what that thing is, secondly how it is programmed, and lastly how it is compiled. Bearing all of that you can then look for traces of what should be the compiled code that does a certain thing.
It takes an understanding of quite a few levels of programming. For instance if I wanted to remove reloading time from a FPS. I would have to know that the game prbly uses an engine, and that engine prbly contains a class for weapons, and that weapon has a reload time, and a animation that goes with the reloading sequence. I would have to understand that a gun only prbly reloads when the ammo is 0 or you hit "R". Keeping all this in mind I then have to learn how to use the tools of Reverse Engineering, Debugger, Disassemblers, memory searchers, etc. to find the ammo count. Then I can search for what code accesses the value. Prbly the reload function. The reload function prbly has some sort of timer. I can look for any kind of countdown and change it to create no reload.
Or better yet I could think: "Well reload times are different for different guns." A pistol reloads faster then a sniper rifle. So I could literally change my weapons up and scan for increased and/or decreased values depending on the currently selected weapon. (NOTE: This is a more logical approach, while earlier was a more programmatic approach. Logic is superior to knowledge everytime, and in my experience leads to less complication)
So you see the are a myriad of ways to arrive at the same solution. You don't even need to know the exact high level code that was compiled. You just need to understand that the same logic is kept when compiling, and no matter how optimized, and how much loss of information there is the underlying logic must always remain for the program to function properly. Figuring out and attaining this logic is the art of Reverse Engineering.
To remove something from a program, first you need to know what that thing is, secondly how it is programmed, and lastly how it is compiled. Bearing all of that you can then look for traces of what should be the compiled code that does a certain thing.
It takes an understanding of quite a few levels of programming. For instance if I wanted to remove reloading time from a FPS. I would have to know that the game prbly uses an engine, and that engine prbly contains a class for weapons, and that weapon has a reload time, and a animation that goes with the reloading sequence. I would have to understand that a gun only prbly reloads when the ammo is 0 or you hit "R". Keeping all this in mind I then have to learn how to use the tools of Reverse Engineering, Debugger, Disassemblers, memory searchers, etc. to find the ammo count. Then I can search for what code accesses the value. Prbly the reload function. The reload function prbly has some sort of timer. I can look for any kind of countdown and change it to create no reload.
Or better yet I could think: "Well reload times are different for different guns." A pistol reloads faster then a sniper rifle. So I could literally change my weapons up and scan for increased and/or decreased values depending on the currently selected weapon. (NOTE: This is a more logical approach, while earlier was a more programmatic approach. Logic is superior to knowledge everytime, and in my experience leads to less complication)
So you see the are a myriad of ways to arrive at the same solution. You don't even need to know the exact high level code that was compiled. You just need to understand that the same logic is kept when compiling, and no matter how optimized, and how much loss of information there is the underlying logic must always remain for the program to function properly. Figuring out and attaining this logic is the art of Reverse Engineering.
tl;dr @ why
My short version: No
My short version: No