From 99220fe0bc637febc56ea38faae99e885f180b6c Mon Sep 17 00:00:00 2001
From: dmiller <dmiller@e0a8ed71-7df4-0310-8962-fdc924857419>
Date: Thu, 23 Jul 2020 21:16:13 +0000
Subject: [PATCH] Document that --open implies --defeat-rst-ratelimit since
 7.40

---
 docs/refguide.xml | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/docs/refguide.xml b/docs/refguide.xml
index 1bc32bdda..5378cf47d 100644
--- a/docs/refguide.xml
+++ b/docs/refguide.xml
@@ -4012,8 +4012,6 @@ even if this option is not specified.
         </term>
         <listitem>
 
-
-
 <para>Sometimes you only care about ports you can actually connect to
 (<literal>open</literal> ones), and don't want results cluttered with
 <literal>closed</literal>, <literal>filtered</literal>, and
@@ -4027,6 +4025,13 @@ hosts with at least one
 <literal>unfiltered</literal> port, and only see ports in those states.  These three states are treated just as they normally are, which means that <literal>open|filtered</literal> and <literal>unfiltered</literal> may be condensed into counts if there are an overwhelming number of them.
 </para>
 
+<para>Beginning with Nmap 7.40, the <option>--open</option> option implies
+  <indexterm><primary><option>--defeat-rst-ratelimit</option></primary></indexterm>
+  <option>--defeat-rst-ratelimit</option>, because that option only affects
+  <literal>closed</literal> and <literal>filtered</literal> ports, which are
+  hidden by <option>--open</option>.
+</para>
+
         </listitem>
       </varlistentry>