OllyDebugger and Assembly.

Hello, I have seen that many people are having problems using these programs, whenever someone wants to hack a MMORPG is used these programs, but the question is:

What is the CALL Olly Debugger? Assembly what it is?

We show in this tutorial all you need to get your life hacker.

Summary:

Introduction and concepts------------------1
A little assembly ---------------------------2
Olly Debugger Interface --------------------3
Avenue of approach------------------------4
Re-assembly-------------------------------5
Plugin -------------------------------------6

INTRODUCTION AND CONCEPTS

First would be interesting to shed some light on what is and what a debugger is a disassembler, because although almost always walk together, have different purposes.

Disassembler is something that can turn the machine language to assembly language by quoting the instructions sent to the processor for their mnemonics in assembly (asm). Not to be confused with a decompiler, which seeks to convert the native code on a higher level language like C, C + + or Basic.

Debuggers are programs that can analyze, debug and test applications. Currently, most programming IDEs have built a debugger (Visual Studio, for example). The main one is useful for the identification and treatment of error, you can run the code line by line (or instruction by instruction) and analyze the change of variables and behavior code. The binary debuggers already compiled - as the Windows executable (EXE) - follow the same concept of ordinary debuggers, but because the code has already been compiled, it must have a built-in debugger disassembler to decode the instructions.

Currently there are dozens of debuggers and disassemblers there, among which the most famous are: W32Dasm, IDA, WinDbg, SoftICE and OllyDbg. In this tutorial we will use the OllyDbg, it is one of the best and most powerful debuggers (including a disassembler) available. It is also small and free

Download in Attachments!

Scan Rar: odbg201c.zip - Verificador de malware do Jotti

Scan .exe: ollydbg.exe - Verificador de malware do Jotti

What use a debugger?

Many people question why to use a debugger, and in most cases you have access to the original source (if you have programmed the application). I quote below some of the largest facilities of a debugger:

--> Error Handling: Certainly one of the main. Sometimes when programming an application a little mistake went unnoticed, causing malfunction or generate an illegal operation. In many cases it is easier as you analyze the binary compiled into a debugger to try to find the error in the original code. Within that same item we can mention the bug fixes of applications already discontinued (provided with the permission of the company that owns the rights).

--> Reverse Engineering: The process of reverse engineering could not be done efficiently without using a debugger / disassembler. Many people tend to confuse cracked reverse-engineered, and are different concepts. Reverse engineering alone is a completely legal activity, because much of what we see today was only possible due to reverse engineering. The creation of Linux drivers for peripherals that previously only worked with Windows (WinModems) is a good example of reverse engineering brings good things for us.

--> Learning: The use of debuggers and reverse engineering is one of the best ways to learn assembly language. You program something in a language medium or high and then analyzes the results of the binary compiled into a debugger. With this knowledge one can master the language better and create more streamlined and efficient algorithms.

CONCEPTS NEEDED

To understand the workings of a debugger you need to know a little about some concepts related to computers, such as working memory, processor, batteries and addresses. Basic knowledge of assembly is also necessary, since this is the language we have to analyze. If you have no experience in assembly, rest assured that in the following chapters give an overview about it, enough to understand our mini-application study. Below is a brief list of concepts:

--> Processor / CPU: First, many people find that the computer (Office) It's called CPU especially the older ones, but no. Processor or CPU is the brain of every computer. It is he that decodes and executes instructions opcodes. It is basically composed of an arithmetic-logic unit (ALU), floating point unit (FPU), registers, cache, bus and clock generator.

--> RAM: Local temporary storage of data (they are deleted at shutdown). Every application that uses memory to store your data and these are sought and managed by the processor.

--> Addressing Memory:É uma faixa de valores que apontam para uma determinada posição de memória. Toda vez que você escreve ou lê algum dado da memória é necessário indicar o endereço de onde está aquele valor, para que o processador possa buscá-lo.

--> Stack: It is a data structure. Its main feature is the way it works, where you just put the values ​​or remove, without specifying an address (LIFO - Last In, First Out - Last in, first out). It works like a stack of books you will the piling. When you need to remove one of them, it is necessary to take all the books up.

--> Registers: Small parts present within the processor memory (not to be confused with RAM). Extremely fast, and the CPU uses them as a temporary storage of data and performing operations. The amount of data that can be stored depends on the type of processor. The 32-bit processors can store numbers up to 32 bits in each register without requiring conversion routines.

Please wait ... In Brief Tutorial Assembly!

__________________________________________________ __________________________________________________ ____________________