diff --git a/docs/nmap-install.xml b/docs/nmap-install.xml index 3e65f0e44..25873fa81 100644 --- a/docs/nmap-install.xml +++ b/docs/nmap-install.xml @@ -23,7 +23,7 @@ installed by default. On Unix systems, open a terminal window and try executing nmap . If Nmap exists and is in your PATH,PATH environment variable -you should see output similar to . +you should see output similar to that in . version number of Nmap @@ -134,7 +134,7 @@ included in that file too. The keys can be imported with the command this once, then you can verify all future Nmap releases from that machine. Before trusting the keys, verify that the fingerprints match the values shown in . +linkend="ex-check-gpg-keys" xrefstyle="select: label nopage"/>. Verifying the Nmap and Fyodor PGP Key Fingerprints @@ -161,9 +161,9 @@ This is the detached signature file. With the proper PGP key in your keyring and the detached signature file downloaded, verifying an Nmap release takes a single GPG command, as shown in . If the file has been +linkend="ex-gpg-verify-nmap-release-good" xrefstyle="select: label nopage"/>. If the file has been tampered with, the results will look like . +linkend="ex-gpg-verify-nmap-release-bad" xrefstyle="select: label nopage"/>. Verifying PGP key fingerprints (Successful) @@ -194,7 +194,7 @@ might have been accidentally corrupted. For every Nmap package download file, there is a corresponding file in the sigs directory with .digest.txt appended to the name (e.g. nmap-4.68.tar.bz2.digest.txt). An example -is shown in . This is the detached +is shown in . This is the detached signature file. The hashes from the digest file can be verified using common tools such as sha1sum, md5sum, or gpg, as shown in Configure the build system: ./configure -If the configuration succeeds, an ASCII art dragon appears to congratulate you on successful configuration and warn you to be careful, as shown in . +If the configuration succeeds, an ASCII art dragon appears to congratulate you on successful configuration and warn you to be careful, as shown in . Successful configuration screen @@ -520,7 +520,7 @@ the RPMs don't support OpenSSL for version detection and Nmap Scripting Engine p RPMinstalling from Installing via RPM is quite easy—it even downloads the package for you when given the proper URLs. The following example downloads and installs Nmap 4.68, including the frontend. Of course you should use the latest version at the download site above instead. Any existing RPM-installed versions are -upgraded. demonstrates this installation process. +upgraded. demonstrates this installation process. Installing Nmap from binary RPMs @@ -535,7 +535,7 @@ Preparing... ########################################### [100%] -As the filenames above imply, these binary RPMs were created for normal PCs (x86 architecture).x86 architecture I also distribute x86_64x86_64 architecture binaries for 64-bit Linux users. These binaries won't work for the relatively few Linux users on other platforms such as SPARC, Alpha, or PowerPC. They also may refuse to install if your library versions are sufficiently different from what the RPMs were initially built on. One option in these cases would be to find binary RPMs prepared by your Linux vendor for your specific distribution. The original install CDs or DVD are a good place to start. Unfortunately, those may not be current or available. Another option is to install Nmap from source code as described previously, though you lose the binary package maintenance consistency benefits. A third option is to build and install your own binary RPMs from the source RPMs distributed from the download page above. demonstrates this technique with Nmap 4.68. +As the filenames above imply, these binary RPMs were created for normal PCs (x86 architecture).x86 architecture I also distribute x86_64x86_64 architecture binaries for 64-bit Linux users. These binaries won't work for the relatively few Linux users on other platforms such as SPARC, Alpha, or PowerPC. They also may refuse to install if your library versions are sufficiently different from what the RPMs were initially built on. One option in these cases would be to find binary RPMs prepared by your Linux vendor for your specific distribution. The original install CDs or DVD are a good place to start. Unfortunately, those may not be current or available. Another option is to install Nmap from source code as described previously, though you lose the binary package maintenance consistency benefits. A third option is to build and install your own binary RPMs from the source RPMs distributed from the download page above. demonstrates this technique with Nmap 4.68. Building and installing Nmap from source RPMs @@ -589,7 +589,7 @@ if you would like the GUI too, though some distributions don't yet package Zenma repository on the Internet, finding the appropriate package for your architecture, and then installing it along with any necessary dependencies. This is shown (edited for brevity) in . You can later perform +linkend="ex-nmap-install-from-yum" xrefstyle="select: label nopage" />. You can later perform yum update to install available updates to Nmap and other packages in the repository. @@ -870,7 +870,7 @@ c: cd "\Program Files\Nmap" -Execute nmap.exe. is a screen shot showing a simple example. +Execute nmap.exe. is a screen shot showing a simple example. @@ -1039,7 +1039,7 @@ approach will continue to work. Mac OS X, including GTK+ and PyGTK. These libraries have many dependencies of their own. A convenient way to install all of them is to use a third-party packaging system as described in -. Once the dependencies are +. Once the dependencies are installed, follow the instructions in to install Zenmap as usual. diff --git a/docs/refguide.xml b/docs/refguide.xml index 539993031..1ab772b33 100644 --- a/docs/refguide.xml +++ b/docs/refguide.xml @@ -86,7 +86,7 @@ operating system guesses, device types, and MAC addresses. A typical Nmap scan is shown in . The only Nmap arguments used in + linkend="man-ex-repscan" xrefstyle="select: label nopage" />. The only Nmap arguments used in this example are , to enable OS and version detection, script scanning, and traceroute; for faster execution; and then the two target hostnames. diff --git a/docs/scripting.xml b/docs/scripting.xml index c06a41b14..1d58b4447 100644 --- a/docs/scripting.xml +++ b/docs/scripting.xml @@ -141,7 +141,7 @@ The reference manual is also next to that port in the Nmap output port table. Host scripts, on the other hand, run no more than once against each target IP and produce results below the port table. shows a typical script scan. Examples of + linkend="nse-ex1" xrefstyle="select: label nopage"/> shows a typical script scan. Examples of service scripts producing output are Stealth SSH version, which tricks some SSH servers into divulging version information without logging the attempt as they normally @@ -870,7 +870,7 @@ that. by Luiz Henrique de Figueiredo.Henrique de Figueiredo, Luiz The Binlib functions take a format string to encode and decode binary - data. The operators of the format string are shown in . + data. The operators of the format string are shown in . Binlib format string operators @@ -3065,7 +3065,7 @@ end required clean up operations. - shows cleanup + shows cleanup exception handling at work. A new function named catch is defined to simply close the newly created socket in case of an error. It is then used