The book I'm complaining about isn't Spidering Hacks, but I'm not sure if you assumed it was.
One measure that could be taken to help keep such books out of the hands of the bad guys is to title them as crack prevention books rather than cracker helper books. That's not the case with the book from O'Reilly's catalog. O'Reilly's description of it also shouldn't make it sound like it will help crackers, but it does. O'Reilly is making it more attractive to the scumbag variety of hackers (the term I used in my original post, which seems to have been misunderstood by several monks) than to decent computer security people. The title and content should make it as clear as possible that it is a book for crack prevention, if such a book is published at all.
-
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.
|
