VirtualBox

Changeset 35277 in vbox


Ignore:
Timestamp:
Dec 21, 2010 2:52:06 PM (14 years ago)
Author:
vboxsync
Message:

Manual: new security considerations chapter; VRDE/VRDP

Location:
trunk/doc/manual
Files:
5 edited

Legend:

Unmodified
Added
Removed

  • trunk/doc/manual/Makefile.kmk

    r34807 r35277  
    132132        user_KnownIssues.xml \
    133133        user_PrivacyPolicy.xml \
     134        user_Security.xml \
    134135        user_Technical.xml \
    135136        user_ThirdParty.xml \

  • trunk/doc/manual/en_US/UserManual.xml

    r34802 r35277  
    5858    xmlns:xi="http://www.w3.org/2001/XInclude" />
    5959
     60  <xi:include href="user_Security.xml" xpointer="element(/1)"
     61              xmlns:xi="http://www.w3.org/2001/XInclude" />
     62
    6063  <xi:include href="user_KnownIssues.xml" xpointer="element(/1)"
    6164    xmlns:xi="http://www.w3.org/2001/XInclude" />

  • trunk/doc/manual/en_US/user_Frontends.xml

    r35193 r35277  
    66
    77  <sect1>
    8     <title id="vrde">VirtualBox Remote Desktop Extension (VRDE)</title>
    9 
    10     <para>VirtualBox can display virtual machines remotely. This allows you to
    11     see the output of a virtual machine's window remotely on another computer
    12     and control the virtual machine from there, as if the virtual machine was
    13     running on that computer.</para>
     8    <title id="vrde">Remote display (VRDP support)</title>
     9
     10    <para>VirtualBox can display virtual machines remotely, meaning that a
     11    virtual machine can execute on one machine even though the machine will be
     12    displayed on a second computer, and the machine will be controlled from
     13    there as well, as if the virtual machine was running on that second
     14    computer.</para>
    1415
    1516    <para>For maximum flexibility, starting with VirtualBox 4.0, VirtualBox
    … …  
    1920    be supplied by third parties with VirtualBox extension packages, which
    2021    must be installed separately from the base package. See <xref
    21     linkend="intro-installing" /> for more information. </para>
    22 
    23     <para>Oracle provides support for the VirtualBox Remote Display Protocol
    24     (VRDP) in such a VirtualBox extension package. When this package is
    25     installed, VirtualBox versions 4.0 and later support VRDP the same way as
    26     earlier versions.</para>
     22    linkend="intro-installing" /> for more information.</para>
     23
     24    <para>Oracle provides support for the <emphasis role="bold">VirtualBox
     25    Remote Display Protocol (VRDP)</emphasis> in such a VirtualBox extension
     26    package. When this package is installed, VirtualBox versions 4.0 and later
     27    support VRDP the same way as binary (non-open-source) versions of
     28    VirtualBox before 4.0 did.</para>
    2729
    2830    <para>VRDP is a backwards-compatible extension to Microsoft's Remote
    … …  
    140142      running virtual machines remotely, it is not convenient to have to run
    141143      the full-fledged GUI if you never want to have VMs displayed locally in
    142       the first place. In particular, if you are running servers whose only
    143       purpose is to host VMs, and all your VMs are supposed to run remotely
    144       over VRDE, then it is pointless to have a graphical user interface on
    145       the server at all -- especially since, on a Linux or Solaris host, the
    146       VirtualBox manager comes with dependencies on the Qt and SDL libraries,
    147       which is inconvenient if you would rather not have the X Window system
    148       on your server at all.</para>
     144      the first place. In particular, if you are running server hardware whose
     145      only purpose is to host VMs, and all your VMs are supposed to run
     146      remotely over VRDP, then it is pointless to have a graphical user
     147      interface on the server at all -- especially since, on a Linux or
     148      Solaris host, the VirtualBox manager comes with dependencies on the Qt
     149      and SDL libraries. This is inconvenient if you would rather not have the
     150      X Window system on your server at all.</para>
    149151
    150152      <para>VirtualBox therefore comes with yet another front-end called
    151153      <computeroutput>VBoxHeadless</computeroutput>, which produces no visible
    152       output on the host at all, but instead only delivers VRDE data.<footnote>
     154      output on the host at all, but instead only delivers VRDP data. This
     155      front-end has no dependencies on the X Window system on Linux and
     156      Solaris hosts.<footnote>
    153157          <para>Before VirtualBox 1.6, the headless server was called
    154158          <computeroutput>VBoxVRDP</computeroutput>. For the sake of backwards
    … …  
    157161        </footnote></para>
    158162
    159       <para>To start a virtual machine with VBoxHeadless, you have two
     163      <para>To start a virtual machine with
     164      <computeroutput>VBoxHeadless</computeroutput>, you have two
    160165      options:</para>
    161166
    162167      <itemizedlist>
    163168        <listitem>
    164           <para>You can use <screen>VBoxManage startvm "VM name" --type headless</screen>
    165           The extra <computeroutput>--type</computeroutput> option causes the
    166           VirtualBox core to use <computeroutput>VBoxHeadless</computeroutput>
    167           as the front-end to the internal virtualization engine.</para>
     169          <para>You can use <screen>VBoxManage startvm "VM name" --type headless</screen>The
     170          extra <computeroutput>--type</computeroutput> option causes
     171          VirtualBox to use <computeroutput>VBoxHeadless</computeroutput> as
     172          the front-end to the internal virtualization engine instead of the
     173          Qt front-end.</para>
    168174        </listitem>
    169175
    … …  
    173179          follows:<screen>VBoxHeadless --startvm &lt;uuid|name&gt;</screen></para>
    174180
    175           <para>This way of starting the VM has the advantage that you can see
     181          <para>This way of starting the VM is preferred because you can see
    176182          more detailed error messages, especially for early failures before
    177183          the VM execution is started. If you have trouble with
    … …  
    184190      <para>Note that when you use
    185191      <computeroutput>VBoxHeadless</computeroutput> to start a VM, since the
    186       headless server has no other means of output, the VRDE server
    187       will <emphasis>always</emphasis> be enabled, regardless of whether you
    188       have enabled the VRDE server in the VM's settings. If this is
    189       undesirable (for example because you want to access the VM via
     192      headless server has no other means of output, the VRDP server will
     193      <emphasis>always</emphasis> be enabled, regardless of whether you had
     194      enabled the VRDP server in the VM's settings. If this is undesirable
     195      (for example because you want to access the VM via
    190196      <computeroutput>ssh</computeroutput> only), start the VM like
    191       this:<screen>VBoxHeadless --startvm &lt;uuid|name&gt; --vrde=off</screen>
    192       To use the setting from the VM configuration, as the
     197      this:<screen>VBoxHeadless --startvm &lt;uuid|name&gt; --vrde=off</screen>To
     198      have the VRDP server enabled depending on the VM configuration, as the
    193199      other front-ends would, use this:<screen>VBoxHeadless --startvm &lt;uuid|name&gt; --vrde=config</screen></para>
    194200    </sect2>
    … …  
    202208      create a virtual machine, establish an RDP connection and install a
    203209      guest operating system -- all without having to touch the headless
    204       server. VirtualBox extension packages with the VRDP server must be
    205       installed. All you need is the following:</para>
     210      server. All you need is the following:</para>
    206211
    207212      <para><orderedlist>
    208213          <listitem>
    209214            <para>VirtualBox on a server machine with a supported host
    210             operating system; for the following example, we will assume a
    211             Linux server;</para>
    212           </listitem>
    213 
    214           <listitem>
    215             <para>an ISO file on the server, containing the installation data
    216             for the guest operating system to install (we will assume Windows
    217             XP in the following example);</para>
    218           </listitem>
    219 
    220           <listitem>
    221             <para>a terminal connection to that host over which you can access
    222             a command line (e.g. via <computeroutput>telnet</computeroutput>
    223             or <computeroutput>ssh</computeroutput>);</para>
    224           </listitem>
    225 
    226           <listitem>
    227             <para>an RDP viewer on the remote client; see <xref
     215            operating system. The VirtualBox extension pack for the VRDP
     216            server must be installed (see the previous section). For the
     217            following example, we will assume a Linux server.</para>
     218          </listitem>
     219
     220          <listitem>
     221            <para>An ISO file accessible from the server, containing the
     222            installation data for the guest operating system to install (we
     223            will assume Windows XP in the following example).</para>
     224          </listitem>
     225
     226          <listitem>
     227            <para>A terminal connection to that host through which you can
     228            access a command line (e.g. via
     229            <computeroutput>ssh</computeroutput>).</para>
     230          </listitem>
     231
     232          <listitem>
     233            <para>An RDP viewer on the remote client; see <xref
    228234            linkend="rdp-viewers" /> above for examples.</para>
    229235          </listitem>
    … …  
    240246            <para>Note that if you do not specify
    241247            <computeroutput>--register</computeroutput>, you will have to
    242             manually use the registervm command later.</para>
     248            manually use the <computeroutput>registervm</computeroutput>
     249            command later.</para>
    243250
    244251            <para>Note further that you do not need to specify
    245             <computeroutput>--ostype</computeroutput> but doing so selects
     252            <computeroutput>--ostype</computeroutput>, but doing so selects
    246253            some sane default values for certain VM parameters, for example
    247254            the RAM size and the type of the virtual network device. To get a
    … …  
    258265          <listitem>
    259266            <para>Create a virtual hard disk for the VM (in this case, 10GB in
    260             size) and register it with VirtualBox:<screen>VBoxManage createhd --filename "WinXP.vdi" --size 10000 --remember</screen></para>
     267            size):<screen>VBoxManage createhd --filename "WinXP.vdi" --size 10000</screen></para>
    261268          </listitem>
    262269
    … …  
    267274
    268275          <listitem>
    269             <para>Set this newly created VDI file as the first virtual hard
     276            <para>Set the VDI file created above as the first virtual hard
    270277            disk of the new VM:<screen>VBoxManage storageattach "Windows XP" --storagectl "IDE Controller"
    271278      --port 0 --device 0 --type hdd --medium "WinXP.vdi"</screen></para>
    … …  
    293300
    294301            <para>You should now be seeing the installation routine of your
    295             guest operating system in the RDP viewer.</para>
     302            guest operating system remotely in the RDP viewer.</para>
    296303          </listitem>
    297304        </orderedlist></para>
    … …  
    337344
    338345    <sect2 id="vbox-auth">
    339       <title>VRDE authentication</title>
    340 
    341       <para>For each virtual machine that is remotely accessible via VRDE, you
     346      <title>RDP authentication</title>
     347
     348      <para>For each virtual machine that is remotely accessible via RDP, you
    342349      can individually determine if and how client connections are
    343       authenticated.</para>
    344 
    345       <para>For this, use <computeroutput>VBoxManage modifyvm</computeroutput>
    346       command with the <computeroutput>--vrdeauthtype</computeroutput> option;
    347       see <xref linkend="vboxmanage-modifyvm" /> for a general introduction.
    348       Three methods of authentication are available:<itemizedlist>
     350      authenticated. For this, use <computeroutput>VBoxManage
     351      modifyvm</computeroutput> command with the
     352      <computeroutput>--vrdeauthtype</computeroutput> option; see <xref
     353      linkend="vboxmanage-modifyvm" /> for a general introduction. Three
     354      methods of authentication are available:<itemizedlist>
    349355          <listitem>
    350356            <para>The "null" method means that there is no authentication at
    351             all; any client can connect to the VRDE server and thus the
     357            all; any client can connect to the VRDP server and thus the
    352358            virtual machine. This is, of course, very insecure and only to be
    353359            recommended for private networks.</para>
    … …  
    356362          <listitem>
    357363            <para>The "external" method provides external authentication
    358             through a special authentication library.</para>
    359 
    360             <para>VirtualBox comes with three default libraries for external
    361             authentication:<itemizedlist>
     364            through a special authentication library. VirtualBox ships with
     365            two such authentication libraries:<orderedlist>
    362366                <listitem>
    363                   <para>On Linux hosts,
    364                   <computeroutput>VBoxAuth.so</computeroutput> authenticates
    365                   users against the host's PAM system.</para>
     367                  <para>The default authentication library,
     368                  <computeroutput>VBoxAuth</computeroutput>, authenticates
     369                  against user credentials of the hosts. Depending on the host
     370                  platform, this means:<itemizedlist>
     371                      <listitem>
     372                        <para>On Linux hosts,
     373                        <computeroutput>VBoxAuth.so</computeroutput>
     374                        authenticates users against the host's PAM
     375                        system.</para>
     376                      </listitem>
     377
     378                      <listitem>
     379                        <para>On Windows hosts,
     380                        <computeroutput>VBoxAuth.dll</computeroutput>
     381                        authenticates users against the host's WinLogon
     382                        system.</para>
     383                      </listitem>
     384
     385                      <listitem>
     386                        <para>On Mac OS X hosts,
     387                        <computeroutput>VBoxAuth.dylib</computeroutput>
     388                        authenticates users against the host's directory
     389                        service.<footnote>
     390                            <para>Support for Mac OS X was added in version
     391                            3.2.</para>
     392                          </footnote></para>
     393                      </listitem>
     394                    </itemizedlist></para>
     395
     396                  <para>In other words, the "external" method per default
     397                  performs authentication with the user accounts that exist on
     398                  the host system. Any user with valid authentication
     399                  credentials is accepted, i.e. the username does not have to
     400                  correspond to the user running the VM.</para>
    366401                </listitem>
    367402
    368403                <listitem>
    369                   <para>On Windows hosts,
    370                   <computeroutput>VBoxAuth.dll</computeroutput> authenticates
    371                   users against the host's WinLogon system.</para>
     404                  <para>An additional library called
     405                  <computeroutput>VBoxAuthSimple</computeroutput> performs
     406                  authentication against credentials configured in the
     407                  "extradata" section of a virtual machine's XML settings
     408                  file. This is probably the simplest way to get
     409                  authentication that does not depend on a running and
     410                  supported guest (see below). The following steps are
     411                  required:<orderedlist>
     412                      <listitem>
     413                        <para>Enable
     414                        <computeroutput>VBoxAuthSimple</computeroutput> with
     415                        the following command:</para>
     416
     417                        <para><screen>VBoxManage setproperty vrdeauthlibrary "VBoxAuthSimple"</screen></para>
     418                      </listitem>
     419
     420                      <listitem>
     421                        <para>To enable the library for a particular VM, you
     422                        must then switch authentication to external:<screen>VBoxManage modifyvm &lt;vm&gt; --vrdeauthtype external</screen></para>
     423
     424                        <para>Replace
     425                        <computeroutput>&lt;vm&gt;</computeroutput> with the
     426                        VM name or UUID.</para>
     427                      </listitem>
     428
     429                      <listitem>
     430                        <para>You will then need to configure users and
     431                        passwords by writing items into the machine's
     432                        extradata. Since the XML machine settings file, into
     433                        whose "extradata" section the password needs to be
     434                        written, is a plain text file, VirtualBox uses hashes
     435                        to encrypt passwords. The following command must be
     436                        used:<screen>VBoxManage setextradata &lt;vm&gt; "VBoxAuthSimple/users/&lt;user&gt;" &lt;hash&gt;</screen></para>
     437
     438                        <para>Replace
     439                        <computeroutput>&lt;vm&gt;</computeroutput> with the
     440                        VM name or UUID,
     441                        <computeroutput>&lt;user&gt;</computeroutput> with the
     442                        user name who should be allowed to log in and
     443                        <computeroutput>&lt;hash&gt;</computeroutput> with the
     444                        encrypted password. As an example, to obtain the hash
     445                        value for the password "secret", you can use the
     446                        following command:<screen>VBoxManage internalcommands passwordhash "secret"</screen></para>
     447
     448                        <para>This will print
     449                        "2bb80d537b1da3e38bd30361aa855686bde0eacd7162fef6a25fe97bf527a25b".
     450                        You can then use VBoxManage setextradata to store this
     451                        value in the machine's "extradata" section.</para>
     452
     453                        <para>As example, combined together, to set the
     454                        password for the user "john" and the machine "My VM"
     455                        to "secret", use this command:<screen>VBoxManage setextradata "My VM" "VBoxAuthSimple/users/john"
     456    2bb80d537b1da3e38bd30361aa855686bde0eacd7162fef6a25fe97bf527a25b</screen></para>
     457                      </listitem>
     458                    </orderedlist></para>
    372459                </listitem>
    373 
    374                 <listitem>
    375                   <para>On Mac OS X hosts,
    376                   <computeroutput>VBoxAuth.dylib</computeroutput>
    377                   authenticates users against the host's directory
    378                   service.<footnote>
    379                       <para>Support for Mac OS X was added in version
    380                       3.2.</para>
    381                     </footnote></para>
    382                 </listitem>
    383               </itemizedlist></para>
    384 
    385             <para>In other words, the "external" method per default performs
    386             authentication with the user accounts that exist on the host
    387             system. Any user with valid authentication credentials is
    388             accepted, i.e. the username does not have to correspond to the
    389             user running the VM.</para>
    390           </listitem>
    391 
    392           <listitem>
    393             <para>An additional library called
    394             <computeroutput>VBoxAuthSimple</computeroutput> performs
    395             authentication against credentials configured in the VM's extra
    396             data section. This is probably the simplest way to get
    397             authentication that does not depend on a running and supported
    398             guest (see below). In order to enable VBoxAuthSimple, issue
    399             <computeroutput>VBoxManage setproperty vrdeauthlibrary
    400             "VBoxAuthSimple"</computeroutput>. To enable the library for a VM,
    401             switch authentication to external using <computeroutput>VBoxManage
    402             modifyvm "VM name" --vrdeauthtype external</computeroutput>. Last
    403             but not least, you have to configure users and passwords. Here is
    404             an example for the user "john" with the password "secret":
    405             <computeroutput>VBoxManage internalcommands passwordhash
    406             "secret"</computeroutput> This will give you the hash value
    407             "2bb80d537b1da3e38bd30361aa855686bde0eacd7162fef6a25fe97bf527a25b"
    408             which you set using <computeroutput>VBoxManage setextradata "VM
    409             name" "VBoxAuthSimple/users/john"
    410             "2bb80d537b1da3e38bd30361aa855686bde0eacd7162fef6a25fe97bf527a25b"</computeroutput>.</para>
     460              </orderedlist></para>
    411461          </listitem>
    412462
    … …  
    414464            <para>Finally, the "guest" authentication method performs
    415465            authentication with a special component that comes with the Guest
    416             Additions; as a result, authentication is not performed with the
    417             host users, but with the guest user accounts. This method is
    418             currently still in testing and not yet supported.</para>
     466            Additions; as a result, authentication is not performed on the
     467            host, but with the <emphasis>guest</emphasis> user
     468            accounts.</para>
     469
     470            <para>This method is currently still in testing and not yet
     471            supported.</para>
    419472          </listitem>
    420473        </itemizedlist></para>
    421474
    422475      <para>In addition to the methods described above, you can replace the
    423       default "external authentication module with any other module. For this,
    424       VirtualBox provides a well-defined interface that allows you to write
    425       your own authentication module. This is described in detail in the
     476      default "external" authentication module with any other module. For
     477      this, VirtualBox provides a well-defined interface that allows you to
     478      write your own authentication module. This is described in detail in the
    426479      VirtualBox Software Development Kit (SDK) reference; please see <xref
    427480      linkend="VirtualBoxAPI" /> for details.</para>
    … …  
    440493            RDP client does not perform any checks in order to verify the
    441494            identity of the server it connects to. Since user credentials can
    442             be obtained using a man in the middle (MITM) attack, RDP4
     495            be obtained using a "man in the middle" (MITM) attack, RDP4
    443496            authentication is insecure and should generally not be
    444497            used.</para>
    … …  
    475528      <title>Multiple connections to the VRDP server</title>
    476529
    477       <para>The VRDP server of VirtualBox supports simultaneous
     530      <para>The VRDP server of VirtualBox supports multiple simultaneous
    478531      connections to the same running VM from different clients. All connected
    479532      clients see the same screen output and share a mouse pointer and
    … …  
    495548      (<computeroutput>-d</computeroutput>). If the parameter ends with
    496549      <computeroutput>@</computeroutput> followed by a number, VirtualBox
    497       interprets this number as the screen index. The primary guest
    498       screen is selected with <computeroutput>@1</computeroutput>, the first
    499       secondary screen is <computeroutput>@2</computeroutput>, etc.</para>
    500 
    501       <para>The MS RDP6 client does not let you specify a separate domain
    502       name. Instead, use <computeroutput>domain\username</computeroutput> in
    503       the <computeroutput>Username:</computeroutput> field -- for example,
     550      interprets this number as the screen index. The primary guest screen is
     551      selected with <computeroutput>@1</computeroutput>, the first secondary
     552      screen is <computeroutput>@2</computeroutput>, etc.</para>
     553
     554      <para>The Microsoft RDP6 client does not let you specify a separate
     555      domain name. Instead, use
     556      <computeroutput>domain\username</computeroutput> in the
     557      <computeroutput>Username:</computeroutput> field -- for example,
    504558      <computeroutput>@2\name</computeroutput>.
    505559      <computeroutput>name</computeroutput> must be supplied, and must be the
    … …  
    517571      compression ratio by lowering the video quality.</para>
    518572
    519       <para>Video streams in a guest are detected by the server
    520       automatically as frequently updated rectangular areas. Therefore, this
    521       method works with any guest operating system without having to install
    522       additional software in the guest.</para>
     573      <para>The VRDP server automatically detects video streams in a guest as
     574      frequently updated rectangular areas. As a result, this method works
     575      with any guest operating system without having to install additional
     576      software in the guest; in particular, the Guest Additions are not
     577      required.</para>
    523578
    524579      <para>On the client side, however, currently only the Windows 7 Remote
    525580      Desktop Connection client supports this feature. If a client does not
    526       support video redirection, the VRDP server uses regular bitmap
     581      support video redirection, the VRDP server falls back to regular bitmap
    527582      updates.</para>
    528583
    … …  
    530585
    531586      <para>The quality of the video is defined as a value from 10 to 100
    532       percent, as is common with JPEG compression. The quality can be changed
    533       using the following command: <screen>VBoxManage modifyvm "VM name" --vrdevideochannelquality 75</screen></para>
     587      percent, representing a JPEG compression level (where lower numbers mean
     588      lower quality but higher compression). The quality can be changed using
     589      the following command: <screen>VBoxManage modifyvm "VM name" --vrdevideochannelquality 75</screen></para>
    534590    </sect2>
    535591
    … …  
    537593      <title>VRDP customization</title>
    538594
    539       <para>Starting with VirtualBox 4.0, it is possible to disable display
    540       output, mouse and keyboard input, audio, remote USB or clipboard in the
    541       VRDP server.</para>
    542 
    543       <para>The following commands change corresponding server settings:</para>
     595      <para>With VirtualBox 4.0 it is possible to disable display output,
     596      mouse and keyboard input, audio, remote USB or clipboard individually in
     597      the VRDP server.</para>
     598
     599      <para>The following commands change corresponding server
     600      settings:</para>
    544601
    545602      <screen>VBoxManage modifyvm "VM name" --vrdeproperty Client/DisableDisplay=1
    … …  
    553610      1. For example: <screen>VBoxManage modifyvm "VM name" --vrdeproperty Client/DisableDisplay=</screen></para>
    554611
    555       <para>Note that with earlier releases of VirtualBox (3.2.10 or more recent 3.2 versions),
    556       the following commands change corresponding server settings:</para>
     612      <para>These properties were introduced with VirtualBox 3.2.10. However,
     613      in the 3.2.x series, it was necessary to use the following commands to
     614      alter these settings instead:</para>
    557615
    558616      <screen>VBoxManage setextradata "VM name" "VRDP/Feature/Client/DisableDisplay" 1

  • trunk/doc/manual/en_US/user_Glossary.xml

    r35193 r35277  
    317317        network connection over which data is transferred in both directions.
    318318        Typically graphics updates and audio are sent from the remote machine
    319         and keyboard and mouse input events are sent from the client.
    320         VirtualBox contains an enhanced implementation of the relevant
    321         standards implemented as a VirtualBox Remote Desktop Extension (VRDE),
    322         which is largely compatible with Microsoft's RDP implementation.
    323         See <xref linkend="vrde" /> for details.</para>
     319        and keyboard and mouse input events are sent from the client. A
     320        VirtualBox extension package by Oracle provides VRDP, an enhanced
     321        implementation of the relevant standards which is largely compatible
     322        with Microsoft's RDP implementation. See <xref linkend="vrde" /> for
     323        details.</para>
    324324      </glossdef>
    325325    </glossentry>
    … …  
    430430
    431431      <glossdef>
    432         <para>VirtualBox Remote Desktop Extension -- allows remot eaccess to
    433         virtual machines. VirtualBox provides a VRDE, which implements Remote
    434         Desktop Protocol (see RDP).</para>
     432        <para>VirtualBox Remote Desktop Extension. This interface is built
     433        into VirtualBox to allow VirtualBox extension packages to supply
     434        remote access to virtual machines. A VirtualBox extension package by
     435        Oracle provides VRDP support; see <xref linkend="vrde" /> for
     436        details.</para>
    435437      </glossdef>
    436438    </glossentry>

  • trunk/doc/manual/en_US/user_VBoxManage.xml

    r35240 r35277  
    202202        <listitem>
    203203          <para><computeroutput>hostinfo</computeroutput> displays information
    204           about the host system, such as CPUs, memory size and operating system
    205           version.</para>
     204          about the host system, such as CPUs, memory size and operating
     205          system version.</para>
    206206        </listitem>
    207207
    … …  
    845845
    846846    <sect2 id="vboxmanage-modifyvm-other">
    847       <title>Serial port, audio, clipboard, remote desktop and USB settings</title>
     847      <title>Serial port, audio, clipboard, remote desktop and USB
     848      settings</title>
    848849
    849850      <para>The following other hardware settings are available through
    … …  
    950951            <para><computeroutput>--vrde on|off</computeroutput>: With the
    951952            VirtualBox graphical user interface, this enables or disables the
    952             VirtualBox remote desktop extension (VRDE) server. Note that if you are using
    953             <computeroutput>VBoxHeadless</computeroutput> (see <xref
    954             linkend="vboxheadless" />), VRDE is enabled by default.</para>
     953            VirtualBox remote desktop extension (VRDE) server. Note that if
     954            you are using <computeroutput>VBoxHeadless</computeroutput> (see
     955            <xref linkend="vboxheadless" />), VRDE is enabled by
     956            default.</para>
    955957          </listitem>
    956958
    … …  
    972974            <para><computeroutput>--vrdeaddress &lt;IP
    973975            address&gt;</computeroutput>: The IP address of the host network
    974             interface the VRDE server will bind to. If specified, the
    975             server will accept connections only on the specified host network
     976            interface the VRDE server will bind to. If specified, the server
     977            will accept connections only on the specified host network
    976978            interface.</para>
    977979          </listitem>
    … …  
    986988          <listitem>
    987989            <para><computeroutput>--vrdemulticon on|off</computeroutput>: This
    988             enables multiple connections to the same VRDE server, if the server
    989             supports this feature; see
    990             <xref lang="" linkend="vrde-multiconnection" />.</para>
     990            enables multiple connections to the same VRDE server, if the
     991            server supports this feature; see <xref lang=""
     992            linkend="vrde-multiconnection" />.</para>
    991993          </listitem>
    992994
    … …  
    994996            <para><computeroutput>--vrdereusecon on|off</computeroutput>: This
    995997            specifies the VRDE server behavior when multiple connections are
    996             disabled. When this option is enabled, the server will allow
    997             a new client to connect and will drop the existing connection. When
    998             this option is disabled (this is the default setting), a new
    999             connection will not be accepted if there is already a client
    1000             connected to the server.</para>
     998            disabled. When this option is enabled, the server will allow a new
     999            client to connect and will drop the existing connection. When this
     1000            option is disabled (this is the default setting), a new connection
     1001            will not be accepted if there is already a client connected to the
     1002            server.</para>
    10011003          </listitem>
    10021004
    10031005          <listitem>
    10041006            <para><computeroutput>--vrdevideochannel on|off</computeroutput>:
    1005             This enables video redirection, if it is supported by the VRDE server;
    1006             see <xref lang="" linkend="vrde-videochannel" />.</para>
     1007            This enables video redirection, if it is supported by the VRDE
     1008            server; see <xref lang="" linkend="vrde-videochannel" />.</para>
    10071009          </listitem>
    10081010
    10091011          <listitem>
    10101012            <para><computeroutput>--vrdevideochannelquality
    1011             &lt;percent&gt;</computeroutput>: Sets the image quality for
    1012             video redirection; see <xref lang=""
     1013            &lt;percent&gt;</computeroutput>: Sets the image quality for video
     1014            redirection; see <xref lang=""
    10131015            linkend="vrde-videochannel" />.</para>
    10141016          </listitem>
    … …  
    12211223
    12221224        <glossdef>
    1223           <para>Starts a VM without a window for remote display
    1224           only.</para>
     1225          <para>Starts a VM without a window for remote display only.</para>
    12251226        </glossdef>
    12261227      </glossentry>
    … …  
    17221723
    17231724    <para>When "iscsi" is used with the
    1724     <computeroutput>--medium</computeroutput> parameter, additional parameters
    1725     must or can be used:<glosslist>
     1725    <computeroutput>--medium</computeroutput> parameter for iSCSI support --
     1726    see <xref linkend="storage-iscsi" /> --, additional parameters must or can
     1727    be used:<glosslist>
    17261728        <glossentry>
    17271729          <glossterm>server</glossterm>
    … …  
    17671769            (optional).<note>
    17681770                <para>Currently, username and password are stored without
    1769                 encryption (i.e. in cleartext) in the machine configuration
    1770                 file.</para>
     1771                encryption (i.e. in clear text) in the XML machine
     1772                configuration file.</para>
    17711773              </note></para>
    17721774          </glossdef>
    … …  
    19541956          <computeroutput>sdelete</computeroutput> tool provided by Microsoft.
    19551957          Execute <computeroutput>sdelete -c</computeroutput> in the guest to
    1956           zero the free disk space before compressing the virtual disk image.
    1957           </para>
    1958          
     1958          zero the free disk space before compressing the virtual disk
     1959          image.</para>
     1960
    19591961          <para>Please note that compacting is currently only available for
    19601962          VDI images. A similar effect can be achieved by zeroing out free
    19611963          blocks and then cloning the disk to any other dynamically expanding
    1962           format. You can use this workaround until compacting is also supported
    1963           for disk formats other than VDI.</para>
     1964          format. You can use this workaround until compacting is also
     1965          supported for disk formats other than VDI.</para>
    19641966        </listitem>
    19651967
Note: See TracChangeset for help on using the changeset viewer.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette