Changeset 85107 in vbox for trunk/doc/manual/en_US

Timestamp:

Jul 8, 2020 11:02:23 AM (5 years ago)

Author:

vboxsync

svn:sync-xref-src-repo-rev:

139036

Message:

doc/manual: Clarify NAT/NAT service behavior regarding loopback access. Eliminate all "e.g." which have sneaked into the docs. Oracle doc team is avoiding it.

Location:

trunk/doc/manual/en_US

Files:

• user_KnownIssues.xml (modified) (1 diff)
• user_Networking.xml (modified) (2 diffs)
• user_Security.xml (modified) (3 diffs)

trunk/doc/manual/en_US/user_KnownIssues.xml

@@ -99 +99 @@
           Additionally, the "Microsoft Device Guard and Credential Guard hardware
           readiness tool" might has be used in order to turn off more features,
-          e.g. with <screen>.\DG_Readiness_Tool_vX.X.ps1 -Disable -AutoReboot</screen>
+          for example with <screen>.\DG_Readiness_Tool_vX.X.ps1 -Disable -AutoReboot</screen>
           <note>
             <para>

trunk/doc/manual/en_US/user_Networking.xml

@@ -472 +472 @@
       on its private network.
     </para>
+
+    <note>
+      <para>
+        Even though the NAT engine separates the VM from the host,
+        the VM has access to the host's loopback interface and the
+        network services running on it. The host's loopback interface
+        is accessible as IP address 10.0.2.2. This access to the host's
+        loopback interface can be extremely useful in some cases, for
+        example when running a web application under development in the
+        VM and the database server on the loopback interface on the host.
+      </para>
+    </note>
 
     <para>
@@ -799 +811 @@
 <screen>VBoxManage list natnetworks</screen>
 
+    <note>
+      <para>
+        Even though the NAT service separates the VM from the host,
+        the VM has access to the host's loopback interface and the
+        network services running on it. The host's loopback interface
+        is accessible as IP address 10.0.2.2 (assuming the default
+        configuration, in other configurations it's the respective
+        address in the configured IPv4 or IPv6 network range). This
+        access to the host's loopback interface can be extremely useful
+        in some cases, for example when running a web application under
+        development in the VM and the database server on the loopback
+        interface on the host.
+      </para>
+    </note>
+
   </sect1>
 

trunk/doc/manual/en_US/user_Security.xml

@@ -63 +63 @@
       <listitem>
         <para>
-          <emphasis role="strong"> Monitor system activity.</emphasis>
+          <emphasis role="strong">Monitor system activity.</emphasis>
           System security builds on three pillars: good security
           protocols, proper system configuration and system monitoring.
@@ -216 +216 @@
           subnet belonging to this VM and the guest IP is not visible
           from the outside. This networking mode works without any
-          additional setup and is sufficient for many purposes.
+          additional setup and is sufficient for many purposes. Keep in
+          mind that NAT allows access to the host operating system's
+          loopback interface.
         </para>
 
@@ -536 +538 @@
       issues. By default VirtualBox will configure the VMs to run in a
       secure manner, however this may not always be possible without
-      additional user actions (e.g. host OS / firmware configuration
+      additional user actions (for example host OS / firmware configuration
       changes).
     </para>