Hacking: The Art of Exploitation

[count_duckula]

As this book would most likely be very challenging as I am a complete beginner What would you recomend I should read before this book that explains more basic concepts and would give me the ability to come back this book and have the knowledge to be able to read it?

[ghost107]

A similar book is this:
Sockets, Shellcode, Porting, & Coding, Reverse Engineering Exploits and Tool Coding for Security Professionals by James C Foster

But same as Hacking: The Art of Exploitation, requires an intermediate knowledge in programming (C/C++/C#/Java/Python, at least 1 of them). I would recommend learning an programming language first(at least as beginner). And understanding basic networking.

And for shellcoding chapter I think you need to know some assembly too.

[Haabb]

I love this book. ... Here's what the pointer.c (from page 44) looks like in vim...

Even though this is quite an old post, I don't see any replies.

1. When you try to run your code with ./pointer.c, since it it not a compiled program, your terminal will interpret it as a shellscript and fail because it's not a correct script.
2. When you compile with gcc, the warnings you get are because what you are trying to do is dangerous. When you do a printf without formatting, printf(pointer); in your case, a format string can be exploited. The correct way is to use a format like printf("%s", string) or printf("%i %i %i %i", integer1, integer2,...). Warnings at compilation does not affect the compilation and you should still get a working output (a.out if no output is specified)

What you should do:
gcc pointer.c -o pointer
./pointer

Format strings are covered in the book, as far as i remember.

[rbrummett]

I've skimmed through a lot of this book and very confused for the most part. I've done a lot of programming in C and some programming in assembly and familiar with unix, but not to the extent that the author covers. He really takes advantage of system tools that I wasn't aware of and running programs, shellcode from extra memory in variables.

I need to go back into this book with a highlighter, pencil, post-it notes and bug the hell out of my professor who is a security expert.

[cluele55]

I've skimmed through a lot of this book and very confused for the most part. I've done a lot of programming in C and some programming in assembly and familiar with unix, but not to the extent that the author covers. He really takes advantage of system tools that I wasn't aware of and running programs, shellcode from extra memory in variables.

I need to go back into this book with a highlighter, pencil, post-it notes and bug the hell out of my professor who is a security expert.

I have a similar coding background -- No Assembly but mostly C, some Python, and a little Java. I wasn't crazy about the structure of this book. I didn't think the content was confusing as much as it was annoying. Do we have to have THAT MANY screenshots? It's nice to be able to see a few on-screen results just to know that you are on the right track, but most of the screenshots were fluff. (I'm a technical writer, so I'm very anti-fluff when it comes to technical content.)

I'm still new to the many exploits out there and there's a lot of fascinating info in this book. But there were a hundred pages dedicated to programming. Really, if you are reading a book like this, you should know what variables are and pointers, arrays, and functions. With that and all the fluffy screenshots, the book was ridiculously over padded.

Still, the book is worth having. Though it's also worth it to read books on specific attacks. "Violent Python" is a good one, for example, and there are whole books dedicated to SQL Injection.