mirror of
https://github.com/nmap/nmap.git
synced 2026-08-04 14:49:29 +00:00
fixed typo at man page: defeat-rst-ratelimit
This commit is contained in:
parent
eaa7b38623
commit
36bbbf5b11
2 changed files with 2 additions and 2 deletions
|
|
@ -1562,7 +1562,7 @@ Using this option can reduce accuracy, as some ports will appear non\-responsive
|
|||
\FCfiltered\F[]
|
||||
rather than the
|
||||
\FCclosed\F[]
|
||||
state we see when RST packets are received\&. This optional is useful when you only care about open ports, and distinguishing between
|
||||
state we see when RST packets are received\&. This option is useful when you only care about open ports, and distinguishing between
|
||||
\FCclosed\F[]
|
||||
and
|
||||
\FCfiltered\F[]
|
||||
|
|
|
|||
|
|
@ -2605,7 +2605,7 @@ non-responsive because Nmap didn't wait long enough for a rate-limited
|
|||
RST response. With a SYN
|
||||
scan, the non-response results in the port being labeled
|
||||
<literal>filtered</literal> rather than the <literal>closed</literal>
|
||||
state we see when RST packets are received. This optional is useful
|
||||
state we see when RST packets are received. This option is useful
|
||||
when you only care about open ports, and distinguishing between
|
||||
<literal>closed</literal> and <literal>filtered</literal> ports isn't
|
||||
worth the extra time.</para>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue