First they disobey copyright regulations and post-copyright one of their books (at least), which will make it appear less out of date in the future (fraud), and now I see in their latest catalog that they are selling a hacking book that sounds like it's geared to the scumbag variety of hackers, based on their own description. Here's what a review said that I found on the web:
Pros
• Clear and easy to understand as long as you have some background already
• Provides detailed information on types of exploits and writing exploit code
• Gives the reader the nuts & bolts instead of an overview
Cons
• Too technical for beginners
The Bottom Line - This book is almost like a "Part 2" for many of the other hacker technique genre such as Hacking Exposed or Hack Attacks Revealed. Jon Erickson gives more detail for the intermediate to advanced readers including in-depth looks at stack and heap overflows and other types of vulnerabilities as well as instructions for creating exploit code for these flaws rather than just using exploits developed by others. This is a great book as long as you have some background in this field already.
...
Rather than simply describing the vulnerabilities and their exploits theoretically or showing you how to use pre-existing tools to exploit the vulnerabilities, Jon Erickson provides the nuts & bolts you need to learn how to program your own exploit code.
I don't think O'Reilly is the publisher, but they included that and other hacking books in their latest catalog. There are other publishers out there. I'll be avoiding O'Reilly in the future.
...Yes, I know I left out some information.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|