1. Go to your local book store/amazon 2. Go to computers/tech section 3. Buy literally any book on C++ 4. Read it and do all the work in the book 5. Read it again and do all the work in the book again. 6. Buy another book. 7. Repeat steps 4 and 5. 8. Come back here and ask us where to get started with hacking. 9. Listen to us. 10. Learn things from online tutorials 11. Learn D3D. 12. Make hacks.
Contribution by ArhkXi: 1.Go to Amazon.com look for programming books with good reviews on what you're tryin' to learn 2.Order these books or download them via a torrent search engine (like torrentz.com) 3.Get a book on C, and then learn C++ 4.reread your C/C++ books and keep doing the exercises and expanding on them 5.Get a book on Assembly, I'm going to tell you straight-up it is not only literally 100x easier when you know Assembly, but you know how the different memory segments work and how to manipulate memory because you know how things work. 6. Reread your assembly book if its a decent one like Amazon.com: Assembly Language Step-by-Step: Programming with Linux (9780470497029): Jeff Duntemann: Books it would have laid out how computer memory works in a way you can completely understand. 7. After you have a better understand of how memory works you might want to skim through your C/C++ books and realize how much more you know once you understand basic architecture and memory through Assembly. 8. Get a book on WinAPI like Amazon.com: Programming Windows (Microsoft Programming Series) (0790145199508): Charles Petzold: Books torrent search and you will find a pdf, the examples and executables that come with the original accompanying CD can be downloaded from his site athttp://www.charlespetzold.com/src/ProgWin5.zip
9.Get familiar with the API, and pick up an O'Reily book on hacking, and with all of your knowledge now all you really need is someone to show the techniques that are the underlying tactics in hacking, which will turn out to be lots of controlled memory corruption techniques. 10 Learn D3D, I'm currently reading a pdf of Amazon.com: Beginning Direct3D Game Programming, Second Edition (9781931841399): Wolfgang Engel: Books
And I myself am stuck on step 10 .
I can't over e***asize the importance of learning ASM, that some others seem to undermine so much. Reading through hacking books is cryptic when you don't know ASM and the segments, but if you knew ASM you would have navigated these segments many times before and understand completely what each segment is and their respective purposes. Learning ASM would also reveal to you how different types of variable are stored into memory, static the default type of a variables storage is pushed onto the stack (SS, Stack segment) with its respective stack frame. Global variables are on heap, and other etc I probably don't know / Knowing that the SS grew from high memory to low memory while instructions naturally run from low memory to high memory, let me understand more of what was going on, because if you didn't know that thing worked that way wouldn't you be confused, when trying to hack, something that actively requires memory manipulation.
Reading through hacking books knowing how memory works now, whenever I come across a new concept in a chapter I may feel more like a goof for not already knowing, rather than struggling to understand.
Another thing you'll want to do, just to be a good tech savvy person is to Google ANY tech related term you don't know, or you think you could know more about. That's just the habit of a good hacker who wants to know everything. DNA Processing (in relation to the processor being made form DNA), Quadratic processor, quantum processor, VM (Virtual Machine), VNC (Virtual Network Computing), IP (Internet Protocol), MAC (Media Access Control, relating to MAC address), Encryption, RSA.
.
Knowing that the SS grew from high memory to low memory while instructions naturally run from low memory to high memory, let me understand more of what was going on, because if you didn't know that thing worked that way wouldn't you be confused, when trying to hack, something that actively requires memory manipulation.
