Errata
The errata list is a list of errors and their corrections that were found after the product was released.
The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.
Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update
Version | Location | Description | Submitted by | Date submitted |
---|---|---|---|---|
Printed | Page vii Contributors List |
In the enumeration of contributors, the attributions to various hacks are completely |
Anonymous | |
ePub | throughout | My Sign In Iframe does not keep up with itself in my Chromebook2 on CB3550-3340 ONE AND ONLY DEVICE at the present. |
Carolyn Suzanne Bornn | Jul 13, 2019 |
Printed | Page 11 2nd paragraph, last sentence |
"to redirect file descriptor to errfile" |
tcordes | Mar 25, 2015 |
Printed | Page 11 2nd command example block |
Spurious backslash at and of 1st line: |
tcordes | Mar 25, 2015 |
Printed | Page 12 Colored heading for Hack #6 |
The brown color text in the heading changes from darker brown to lighter brown mid-heading between the e and the x in "Complex". I thought it was a print press error, but, if you look closely, the dithering changes, meaning this is caused by faulty formatting commands. |
tcordes | Mar 27, 2015 |
Printed | Page 13 4th text paragraph, 2nd sentence |
Incorrect punctuation: period inside the parentheses: |
tcordes | Mar 25, 2015 |
Printed | Page 16 albumize script, line 12 |
echo -n `echo $x|cut -f 2- -d '-'`;echo -ne ' 00' |
Anonymous | |
Printed | Page 23 3rd paragraph from bottom of page |
This is a little more than a minor technical error, but not a serious error. |
Anonymous | |
Printed | Page 33 2nd last paragraph, 2nd sentence |
"to land in the directory from which process ID 3852 was run" |
tcordes | Mar 25, 2015 |
Printed | Page 33 2nd last paragraph, 2nd sentence |
Incorrect punctuation: period inside the parentheses: |
tcordes | Mar 25, 2015 |
Printed | Page 33 2nd last paragraph, 3rd sentence |
"The exe link points to full path to the binary" |
tcordes | Mar 25, 2015 |
Printed | Page 33 Last paragraph, 1st sentence |
"processes" is possessive, not plural, and should be process's or process', depending on your favoured style. |
tcordes | Mar 25, 2015 |
Printed | Page 37 1st text paragraph |
"and back grounded processes" |
tcordes | Mar 25, 2015 |
Printed | Page 41 3rd paragraph, 3rd sentence |
Incorrect punctuation: period inside the parentheses: |
tcordes | Mar 25, 2015 |
Printed | Page 42 Last sentence on page 42 |
The final sentence implies that loadlin is used primarily to multiboot between two |
Anonymous | |
Printed | Page 42 2nd last text paragraph |
Incorrect punctuation: period inside the parentheses: |
tcordes | Mar 25, 2015 |
Printed | Page 43 1st paragraph, 1st sentence |
Incorrect punctuation: period inside the parentheses: |
tcordes | Mar 25, 2015 |
Printed | Page 45 Last text paragraph |
First sentence completely missing its period: after "Java application)" |
tcordes | Mar 25, 2015 |
Printed | Page 54 The "See Also" for Hack #26, near bottom of page |
The last two bullet points of the "See Also" should be "links" to Hacks #36 and #66 respectively, much like they are elsewhere in the book (for example Hack #38). They should be formatted as such, not just confusing, seemingly random, italic text. |
tcordes | Mar 25, 2015 |
Printed | Page 55 4th text paragraph, last sentence, and following code example |
At "try this perl one-liner" followed by a colon: the example following is devoid of any perl one-liner. The text leads one to believe you are going to be shown the one-liner here. If you meant for the code example merely to be linked to in the referenced hack #73 (which it is, buried with 10 other examples), the wording here should perhaps be changed to: |
tcordes | Mar 27, 2015 |
Printed | Page 60 2nd last text paragraph, 1st sentence |
In "The special CVS file notify", the word "notify" should be in italics, much as the word "users" is in the same paragraph, third sentence. In both cases a literal filename is being referred to. |
tcordes | Mar 27, 2015 |
Printed | Page 61 2nd code/command example |
Spurious "<code>" at the end of the example. It doesn't make any sense there, and it is not in bold like the preceding text, it is most likely a text/formatting typo of some sort. |
tcordes | Mar 27, 2015 |
Printed | Page 62 4th text paragraph, 2nd and 3rd setences |
Incorrect punctuation: period inside the parentheses: |
tcordes | Mar 27, 2015 |
Printed | Page 63 1st paragraph, 2nd sentence |
"contained with in it" |
tcordes | Mar 27, 2015 |
Printed | Page 63 2nd paragraph, 1st sentence |
Incorrect punctuation: period inside the parentheses: |
tcordes | Mar 27, 2015 |
Printed | Page 63 5th text paragraph, 2nd sentence, hack link |
The referenced hack number and title is wrong, it should be Hack #17, not #23. |
tcordes | Mar 27, 2015 |
Printed | Page 65 3rd text paragraph (1st large one), 2nd sentence |
The whole sentence makes no sense. "tar" is not a "design decision" in "ssh". ssh knows nothing about tar. Perhaps saying instead "the ability of ssh to use standard input/output, like with tar," is a brilliant design decision would make more sense. It needs a whole new rejigging. |
tcordes | Mar 27, 2015 |
Printed | Page 66 Hack #37's "See also" section, 2nd link |
2nd Hack link is improperly formatted (color, wording, symbols), unlike the two surrounding links. |
tcordes | Mar 27, 2015 |
Printed | Page 73 1st paragraph |
Where it says how to restore the boot sector directly from a floppy, I believe |
Anonymous | |
Printed | Page 78 code example, 13th last line (including blank lines) |
Using $SHELL here won't work if the user's shell is not bash. For instance, this breaks when the user's shell is tcsh. (Granted, most Linux users will have bash as their default shell.) The problem is that SHELL is not being defined in the script, and so takes its value from the environment. The solution is to defined SHELL as /bin/bash at the top of the script, so the user's environment is overridden. |
tcordes | Mar 27, 2015 |
Printed | Page 78 Last paragraph |
Incorrect punctuation: period inside the parentheses: |
tcordes | Mar 27, 2015 |
Printed | Page 88 1st paragraph, 2nd sentence |
"much of a network admins' time" |
tcordes | Mar 27, 2015 |
Printed | Page 91 last paragraph, 1st sentence |
rp_filter isn't really a "free firewall rule" (i.e., something in iptables), it's a kernel network stack setting. Whilst certainly useful in a "firewall" scenario, its usefulness certainly isn't limited to one. |
tcordes | Apr 10, 2015 |
Printed | Page 91 1st paragraph, 1st sentence |
"the console with iptables!) If you" |
tcordes | Jan 12, 2016 |
Printed | Page 96 last set of command examples, 3rd example line |
Line-continuation backslash is missing from this line (after "fa:ca:de"). It is present on the two preceding lines. |
tcordes | Apr 10, 2015 |
Printed | Page 97 3rd text paragraph, only sentence |
The first half of the sentence is correct: you can't delete a custom chain that has any references to it. The second half -- the remedy -- is wrong. Flushing the rules in chain foo will not get rid of any references to chain foo. The references to chain foo exist in other, "calling", chains. Usually you would not want to indiscriminately flush the calling chains. The only solution is to painstakingly go through all chains looking for calls to chain foo ("-j foo") and then -D deleting them. Only then can you use -X to delete your custom chain. |
tcordes | Apr 10, 2015 |
Printed | Page 97 1st sample command output, "Chain fun-filter" line |
In this example, "Chain fun-filter (0 references)" should in fact show 1 reference. The onereference is in Chain INPUT. Follow the instructions given and that (1, not 0) is the output you will see. |
tcordes | Apr 10, 2015 |
Printed | Page 98 Last command group on page. |
I think I have found the following typo; instead of: |
Anonymous | |
Printed | Page 98 1st paragraph, last sentence |
"...remote clients appear to exist on the network services, or more generally, to connect to any two private networks together..." |
tcordes | Apr 10, 2015 |
Printed | Page 100 last command example block |
On both lines, the word "ip" is not in bold type, unlike the previous examples on the page. |
tcordes | Apr 10, 2015 |
Printed | Page 101 1st text paragaph (hack #52), 3rd sentence |
First word of sentence ("this") is not capitalized. |
tcordes | Apr 10, 2015 |
Printed | Page 104 last command example, 3rd-last line |
The line containing "eth0" has sprung up out of nowhere: it and its 10.42.4.0 network are not mentioned anywhere in the hack; and the previous "before" output of the exact same route command on client (page 101) does not contain this line. |
tcordes | Apr 10, 2015 |
Printed | Page 106 Hack #53, paragraphs 1, 2 and 3 |
The 3 hack-links (in brown type) are to the wrong hack: surely they are supposed to reference Hack #52 "Using vtun over ssh to Circumvent NAT", not Hack #51. |
tcordes | Apr 10, 2015 |
Printed | Page 107 2nd paragraph, 3rd sentence; and 4th paragraph |
Both sentences reference the script named "vtundconf" (as per the Listing heading) as "vtund.conf" (which is the separate config file). Also, in paragraph 4 "currently runs great" should be "currently run great" as the subject consists of two items, not one. |
tcordes | Apr 10, 2015 |
Printed | Page 109 2nd and 5th code "paragraphs" |
The compute_netmask subroutine definition and usage of it are nasty. While it works fine, and as intended, it is almost certainly a kludgy miracle. compute_netmask returns a value that is never used anywhere, but looking at the code you will think that is its entire purpose. The calling code ignores the return value and instead relies upon the side-effect of compute_netmask setting $addr and $mask. It's all extremely bad form and will confuse anyone, even perl hackers, but most especially perl newbies. |
tcordes | Apr 10, 2015 |
Printed | Page 110 3rd code "paragraph", just before __DATA__ |
system("$Vtund $name"); |
tcordes | Apr 10, 2015 |
Printed | Page 119 2nd-last paragraph, last sentence |
Incorrect punctuation: period inside the parentheses: |
tcordes | Apr 23, 2015 |
Printed | Page 120 1st paragraph, 2nd sentence |
Incorrect punctuation: period inside the parentheses: |
tcordes | Apr 23, 2015 |
Printed | Page 121 4th paragraph |
To run this script from .bashrc or .bash_profile you need to disable it for scp or |
Anonymous | |
Printed | Page 122 1st text paragraph, 1st sentence |
"bpf filter" is thrown at you without ever (to this point in the book) defining "bpf". I had to go look it up online. Perhaps it should be spelled out by its full name here, and given its acronym, like "Berkeley Packet Filter (BPF)". "bpf" in any case should probably also be all-uppercase. |
tcordes | Apr 23, 2015 |
Printed | Page 123 2nd text paragraph, 1st sentence |
"note the ' in the google query" |
tcordes | Apr 23, 2015 |
Printed | Page 124 3rd and 4th sample command blocks |
"root@catlin:~# nmap -sX 10.42.4.0/26..." |
tcordes | Apr 23, 2015 |
Printed | Page 126 12 lines up from bottom, including blank lines |
printf("%4d - %4d %8d Kb %d %8d Kb %5d\ |
tcordes | Apr 23, 2015 |
Printed | Page 129 4th paragraph, 2nd sentence |
"The script can continue to watch to watch when ..." |
tcordes | Apr 23, 2015 |
Printed | Page 130 2nd paragraph, last sentence |
Incorrect punctuation: period inside the parentheses: |
tcordes | Apr 23, 2015 |
Printed | Page 131 last paragraph, 1st sentence, and Figure 5-1 |
The sentence refers to Figure 5-2 saying it's a "pie chart", but it's Figure 5-1 that is the pie chart, not 5-2. In fact, the text before Figure 5-1 says 5-1 contains "all sorts of details about what traffic has been seen on your network", but 5-1 is a pie-chart overview, with very few "details". It's almost as if there was supposed to be another figure before 5-1, and it went missing. |
tcordes | Apr 23, 2015 |
Printed | Page 132 Figure 5-2 description text |
"overtime" should be "over time" |
tcordes | Apr 23, 2015 |
Printed | Page 133 2nd-last text paragraph, only sentence |
"Now you can watch activity on all of your hosts simultaneously with a command, as:" |
tcordes | Apr 23, 2015 |
Printed | Page 139 All of page 139-140 missing |
All of the pages which include the start of hac #66 is missing and the link |
Simon Bradley | Dec 25, 2008 |
Printed | Page 140 Last sentence, 3rd last paragraph |
"'Turbo-mode' ssh Logins" (#67) |
tcordes | Jan 11, 2016 |
Printed | Page 141 "See also" section, last line |
"'Turbo-mode' ssh Logins" (#67) |
tcordes | Jan 11, 2016 |
Printed | Page 142 Last paragraph, 1st sentence |
"installed on each homer, bart" |
tcordes | Jan 11, 2016 |
Printed | Page 144 1st paragraph, last sentence; and "See also" section, last line |
"'Turbo-mode' ssh Logins" (#67) |
tcordes | Jan 11, 2016 |
Printed | Page 145 Last paragraph, 2nd sentence |
"'Turbo-mode' ssh Logins" (#67) |
tcordes | Jan 11, 2016 |
Printed | Page 147 1st command line example set and following paragraph |
Command line example set shows ssh of port 8080, but the following text description says port 8000. The next example uses 8000 so that probably is what is intended in the initial example. (3/03 printing) |
tcordes | Jan 11, 2016 |
Printed | Page 152 1st paragraph, 1st sentence |
"it but becomes" |
tcordes | Jan 11, 2016 |
Printed | Page 159 command example after 2nd paragraph |
syslogd -m 0 -a... |
tcordes | Jan 11, 2016 |
Printed | Page 161 1st paragraph |
"matches multiple view statement's match-clients substatements" |
tcordes | Jan 11, 2016 |
Printed | Page 170 Command example after 1st paragraph |
"mysql --dbuser=monitor"... |
tcordes | Jan 11, 2016 |
Printed | Page 171 3rd textual paragraph |
"]One suggested method" |
tcordes | Jan 11, 2016 |
Printed | Page 174 1st paragraph after teh numbered bullet points |
"and 9, very carefully.)" |
tcordes | Jan 11, 2016 |
Printed | Page 174 Point #9, 1st and 2nd sentence |
"Start MySQL on each slave... Finally, fire up MySQL on each slave" |
tcordes | Jan 11, 2016 |
Printed | Page 175 Hack 83 Restoring a Single Table from Large Mysql dump |
Just a suggestion - it seems like all of my mysql dumps insert backticks all over the place, including the table name, which makes this hack not work. I suggest making the following changes for anyone else having the problem: |
Anonymous | |
Printed | Page 179 3rd textual paragraph |
"takes the form database user password" |
tcordes | Jan 12, 2016 |
Printed | Page 185 "See also" section, 3rd bullet point |
"Linux Help.Net" |
tcordes | Jan 12, 2016 |
Printed | Page 187 2nd paragraph |
"snippet from a Apache" |
tcordes | Jan 12, 2016 |
Printed | Page 189 1st paragraph, last sentence |
"log the information to it's access_log." |
tcordes | Jan 12, 2016 |
Printed | Page 190 3rd URL example before the 1st text paragraph |
"track=nyt" URL example should be in bold face like the others. (3/03 printing) |
tcordes | Jan 12, 2016 |
Printed | Page 203 3rd last textual paragraph, 2nd sentence |
"delivered by a script the takes" |
tcordes | Jan 12, 2016 |
Printed | Page 204 1st paragraph, 2nd sentence |
"it returns predictable contend (say, the default view of the first page of an article.)" |
tcordes | Jan 12, 2016 |
Printed | Page 208 "See also" section, 2nd bullet point |
"Proxy Server Hack" is mentioned but I can't find any such hack in the book, except perhaps #98. In any case, it should be formatted in brown/red color as with the hacks referenced below it. (3/03 printing) |
tcordes | Jan 12, 2016 |
Printed | Page 211 2nd paragraph, 1st sentence |
"gateway for 12.34.56.78)." |
tcordes | Jan 12, 2016 |
Printed | Page 219 upper right |
the index entry for 'rcg' is mistakenly labelled 'rgc' |
Anonymous |