From 0e8455e292b67067efc563ec434ba056d9709a98 Mon Sep 17 00:00:00 2001 From: fyodor Date: Mon, 16 Jun 2008 00:24:00 +0000 Subject: [PATCH] =?UTF-8?q?some=20edits=20suggested=20by=20Jo=C3=A3o=20Med?= =?UTF-8?q?eiros?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/nmap-install.xml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/nmap-install.xml b/docs/nmap-install.xml index c17841e06..fc364c9cf 100644 --- a/docs/nmap-install.xml +++ b/docs/nmap-install.xml @@ -157,7 +157,7 @@ signature file downloaded, verifying an Nmap release takes a single GPG command, as shown in . If the file has been tampered with, the results will look like +linkend="ex-gpg-verify-nmap-release-bad"/>. Verifying PGP Key Fingerprints (Successful) @@ -464,7 +464,7 @@ Preparing... ########################################### [100%] -As the filenames above imply, these binary RPMs were created for normal PCs (X86 architecture). I also distribute x86_64 binaries of some releases for users with 64-bit Linux running on an AMD Opteron or Athlon64 processor. 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.62. +As the filenames above imply, these binary RPMs were created for normal PCs (x86 architecture). I also distribute x86_64 binaries of some releases for users with 64-bit Linux running on an AMD Opteron or Athlon64 processor. 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.62. Building and installing Nmap from source RPMs @@ -565,7 +565,7 @@ This works for Debian derivatives such as Ubuntu too. Information on the latest Debian stable Nmap package is available at and the development (unstable) Nmap and Zenmap packages are available from and . +url="http://packages.debian.org/unstable/nmap" /> and . Other Linux Distributions @@ -615,13 +615,13 @@ be reused. Apply the by double-clicking on nmap_performance.reg, or run the command regedt32 nmap_performance.reg. Or you can make the changes by hand. Simply add these three Registry DWORD values to -HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters: +the CurrentControlSet\Services\Tcpip\Parameters entry under HKEY_LOCAL_MACHINE\SYSTEM: MaxUserPort Set a large value such as 65534 (0x0000fffe). See MS KB Q196271. TCPTimedWaitDelay - Set the minimum value (0000001e). See MS KB Q149532. + Set the minimum value (0x0000001e). See MS KB Q149532. StrictTimeWaitSeqCheck Set to 1 so TcpTimedWaitDelay is checked.