Index: /trunk/doc/manual/en_US/user_AdvancedTopics.xml
===================================================================
--- /trunk/doc/manual/en_US/user_AdvancedTopics.xml (revision 56450)
+++ /trunk/doc/manual/en_US/user_AdvancedTopics.xml (revision 56451)
@@ -621,17 +621,17 @@
versions
- X11R6.8/X11R6.9 and XFree86 version 4.3 (vboxvideo_drv_68.o and vboxmouse_drv_68.o)
+ X11R6.8/X11R6.9 and XFree86 version 4.3 (vboxvideo_drv_68.o and vboxmouse_drv_68.o)
- X11R7.0 (vboxvideo_drv_70.so and vboxmouse_drv_70.so)
+ X11R7.0 (vboxvideo_drv_70.so and vboxmouse_drv_70.so)
- X11R7.1 (vboxvideo_drv_71.so and vboxmouse_drv_71.so)
+ X11R7.1 (vboxvideo_drv_71.so and vboxmouse_drv_71.so)
- X.Org Server versions 1.3 and later (vboxvideo_drv_13.so and vboxmouse_drv_13.so and so on).
+ X.Org Server versions 1.3 and later (vboxvideo_drv_13.so and vboxmouse_drv_13.so and so on).
By default these drivers can be found in the
@@ -840,17 +840,17 @@
limitations apply:
- Only PCI cards with non-shared interrupts (such as using MSI on host) are supported at the moment.
+ Only PCI cards with non-shared interrupts (such as using MSI on host) are supported at the moment.
- No guest state can be reliably saved/restored (as the internal state of the PCI card could not be retrieved).
+ No guest state can be reliably saved/restored (as the internal state of the PCI card could not be retrieved).
- Teleportation (live migration) doesn't work (for the same reason).
+ Teleportation (live migration) doesn't work (for the same reason).
- No lazy physical memory allocation. The host will preallocate the whole RAM required for the VM on startup (as we cannot catch physical hardware accesses to the physical memory).
+ No lazy physical memory allocation. The host will preallocate the whole RAM required for the VM on startup (as we cannot catch physical hardware accesses to the physical memory).
@@ -900,15 +900,15 @@
- MaxFramerate The highest rate at which video frames
+ MaxFramerate The highest rate at which video frames
are sent to the guest. A higher frame rate requires more CPU power. Therefore sometimes
it is useful to set a lower limit. Default is no limit and allow the guest to use all
- frame rates supported by the host webcam.
+ frame rates supported by the host webcam.
- MaxPayloadTransferSize How many bytes the emulated
+ MaxPayloadTransferSize How many bytes the emulated
webcam can send to the guest at a time. Default value is 3060 bytes, which is used by
some webcams. Higher values can slightly reduce CPU load, if the guest is able to use
larger buffers. However, a high MaxPayloadTransferSize
- might be not supported by some guests.
+ might be not supported by some guests.
@@ -1478,7 +1478,10 @@
replace pcbios by efi in the keys.
-
- DMI BIOS information (type 0)
- VBoxManage setextradata "VM name"
+
+
+ DMI BIOS information
+
+ (type 0)
+ VBoxManage setextradata "VM name"
"VBoxInternal/Devices/pcbios/0/Config/DmiBIOSVendor" "BIOS Vendor"
VBoxManage setextradata "VM name"
@@ -1494,8 +1497,12 @@
VBoxManage setextradata "VM name"
"VBoxInternal/Devices/pcbios/0/Config/DmiBIOSFirmwareMinor" 4
-
-
- DMI system information (type 1)
- VBoxManage setextradata "VM name"
+
+
+
+
+ DMI system information
+
+ (type 1)
+ VBoxManage setextradata "VM name"
"VBoxInternal/Devices/pcbios/0/Config/DmiSystemVendor" "System Vendor"
VBoxManage setextradata "VM name"
@@ -1512,8 +1519,12 @@
"VBoxInternal/Devices/pcbios/0/Config/DmiSystemUuid"
"9852bf98-b83c-49db-a8de-182c42c7226b"
-
-
- DMI board information (type 2)
- VBoxManage setextradata "VM name"
+
+
+
+
+ DMI board information
+
+ (type 2)
+ VBoxManage setextradata "VM name"
"VBoxInternal/Devices/pcbios/0/Config/DmiBoardVendor" "Board Vendor"
VBoxManage setextradata "VM name"
@@ -1529,8 +1540,12 @@
VBoxManage setextradata "VM name"
"VBoxInternal/Devices/pcbios/0/Config/DmiBoardBoardType" 10
-
-
- DMI system enclosure or chassis (type 3)
- VBoxManage setextradata "VM name"
+
+
+
+
+ DMI system enclosure or chassis
+
+ (type 3)
+ VBoxManage setextradata "VM name"
"VBoxInternal/Devices/pcbios/0/Config/DmiChassisVendor" "Chassis Vendor"
VBoxManage setextradata "VM name"
@@ -1542,19 +1557,30 @@
VBoxManage setextradata "VM name"
"VBoxInternal/Devices/pcbios/0/Config/DmiChassisAssetTag" "Chassis Tag"
-
-
- DMI processor informatiion (type 4)
- VBoxManage setextradata "VM name"
+
+
+
+
+ DMI processor information
+
+ (type 4)
+ VBoxManage setextradata "VM name"
"VBoxInternal/Devices/pcbios/0/Config/DmiProcManufacturer" "GenuineIntel"
VBoxManage setextradata "VM name"
"VBoxInternal/Devices/pcbios/0/Config/DmiProcVersion" "Pentium(R) III"
-
-
- DMI OEM strings (type 11)
- VBoxManage setextradata "VM name"
+
+
+
+
+ DMI OEM strings
+
+ (type 11)
+ VBoxManage setextradata "VM name"
"VBoxInternal/Devices/pcbios/0/Config/DmiOEMVBoxVer" "vboxVer_1.2.3"
VBoxManage setextradata "VM name"
"VBoxInternal/Devices/pcbios/0/Config/DmiOEMVBoxRev" "vboxRev_12345"
-
+
+
+
+
If a DMI string is not set, the default value of VirtualBox is used.
To set an empty string use
@@ -1664,70 +1690,70 @@
following:
-
-
- --timesync-interval
-
- Specifies the interval at which to synchronize the time
- with the host. The default is 10000 ms (10 seconds).
-
-
-
-
- --timesync-min-adjust
-
- The minimum absolute drift value measured in milliseconds
- to make adjustments for. The default is 1000 ms on OS/2 and 100
- ms elsewhere.
-
-
-
- --timesync-latency-factor
-
- The factor to multiply the time query latency with to
- calculate the dynamic minimum adjust time. The default is 8
- times, that means in detail: Measure the time it takes to
- determine the host time (the guest has to contact the VM host
- service which may take some time), multiply this value by 8 and
- do an adjustment only if the time difference between host and
- guest is bigger than this value. Don't do any time adjustment
- otherwise.
-
-
-
-
- --timesync-max-latency
-
- The max host timer query latency to accept. The default is
- 250 ms.
-
-
-
-
- --timesync-set-threshold
-
- The absolute drift threshold, given as milliseconds where
- to start setting the time instead of trying to smoothly adjust
- it. The default is 20 minutes.
-
-
-
-
- --timesync-set-start
-
- Set the time when starting the time sync service.
-
-
-
-
- --timesync-set-on-restore
- 0|1
-
- Set the time after the VM was restored from a saved state
- when passing 1 as parameter (default). Disable by passing 0. In
- the latter case, the time will be adjusted smoothly which can
- take a long time.
-
-
-
+
+
+ --timesync-interval
+
+ Specifies the interval at which to synchronize the time
+ with the host. The default is 10000 ms (10 seconds).
+
+
+
+
+ --timesync-min-adjust
+
+ The minimum absolute drift value measured in milliseconds
+ to make adjustments for. The default is 1000 ms on OS/2 and 100
+ ms elsewhere.
+
+
+
+ --timesync-latency-factor
+
+ The factor to multiply the time query latency with to
+ calculate the dynamic minimum adjust time. The default is 8
+ times, that means in detail: Measure the time it takes to
+ determine the host time (the guest has to contact the VM host
+ service which may take some time), multiply this value by 8 and
+ do an adjustment only if the time difference between host and
+ guest is bigger than this value. Don't do any time adjustment
+ otherwise.
+
+
+
+
+ --timesync-max-latency
+
+ The max host timer query latency to accept. The default is
+ 250 ms.
+
+
+
+
+ --timesync-set-threshold
+
+ The absolute drift threshold, given as milliseconds where
+ to start setting the time instead of trying to smoothly adjust
+ it. The default is 20 minutes.
+
+
+
+
+ --timesync-set-start
+
+ Set the time when starting the time sync service.
+
+
+
+
+ --timesync-set-on-restore
+ 0|1
+
+ Set the time after the VM was restored from a saved state
+ when passing 1 as parameter (default). Disable by passing 0. In
+ the latter case, the time will be adjusted smoothly which can
+ take a long time.
+
+
+
All these parameters can be specified as command line parameters
@@ -1790,5 +1816,5 @@
A VirtualBox VNIC template is a VNIC whose name starts with
"vboxvnic_template" (case-sensitive).
-
+
On Solaris 11 hostsWhen Crossbow based bridged
networking is used., a VNIC template may be used to
@@ -1849,5 +1875,5 @@
rem_drv vboxnet
-
+
Edit the file /platform/i86pc/kernel/drv/vboxnet.conf
and add a line for the new interface we want to add as shown below:
@@ -2962,5 +2988,5 @@
VBoxManage setextradata "VM name" GUI/MouseCapturePolicy MODE
-
+
where MODE is one of the
following keywords:
@@ -3685,7 +3711,7 @@
VBoxManage setextradata "VM name" VBoxInternal/Devices/usb-ehci/LUN#0/Config/CaptureFilename "filename"
- The command above enables capturing on the root hub attached to the EHCI controller.
+ The command above enables capturing on the root hub attached to the EHCI controller.
To enable it for the OHCI or XHCI controller replace usb-ehci
- with usb-ohci or usb-xhci respectively.
+ with usb-ohci or usb-xhci respectively.
Index: /trunk/doc/manual/en_US/user_BasicConcepts.xml
===================================================================
--- /trunk/doc/manual/en_US/user_BasicConcepts.xml (revision 56450)
+++ /trunk/doc/manual/en_US/user_BasicConcepts.xml (revision 56451)
@@ -421,12 +421,11 @@
installed on the guest.
- Drag'n drop is disabled by default. This setting can be
+ Drag'n drop is disabled by default. This setting can be
changed at any time using the "Drag'n'Drop" menu item in the
- "Devices" menu of the virtual machine.
-
- See for more information.
-
+ "Devices" menu of the virtual machine.
+
+ See for more information.
Experimental support for drag and drop was added
- with VirtualBox 4.2.
+ with VirtualBox 4.2.
Index: /trunk/doc/manual/en_US/user_ChangeLog.xml
===================================================================
--- /trunk/doc/manual/en_US/user_ChangeLog.xml (revision 56450)
+++ /trunk/doc/manual/en_US/user_ChangeLog.xml (revision 56451)
@@ -16,7 +16,10 @@
- With VirtualBox 3.2, changelog information for versions before 2.0 was removed in
- order to save space. To access this information, please consult the User Manual of
- VirtualBox version 3.1 or earlier.
+
+ Older Change log details
+ With VirtualBox 3.2, changelog information for versions before 2.0
+ was removed in order to save space. To access this information, please
+ consult the User Manual of VirtualBox version 3.1 or earlier.
+
Index: /trunk/doc/manual/en_US/user_Frontends.xml
===================================================================
--- /trunk/doc/manual/en_US/user_Frontends.xml (revision 56450)
+++ /trunk/doc/manual/en_US/user_Frontends.xml (revision 56451)
@@ -582,19 +582,19 @@
generate a server certificate.
- Create a CA self signed certificate:
+ Create a CA self signed certificate:
openssl req -new -x509 -days 365 -extensions v3_ca \
- -keyout ca_key_private.pem -out ca_cert.pem
+ -keyout ca_key_private.pem -out ca_cert.pem
- Generate a server private key and a request for signing:
+ Generate a server private key and a request for signing:
openssl genrsa -out server_key_private.pem
-openssl req -new -key server_key_private.pem -out server_req.pem
+openssl req -new -key server_key_private.pem -out server_req.pem
- Generate the server certificate:
+ Generate the server certificate:
openssl x509 -req -days 365 -in server_req.pem \
- -CA ca_cert.pem -CAkey ca_key_private.pem -set_serial 01 -out server_cert.pem
+ -CA ca_cert.pem -CAkey ca_key_private.pem -set_serial 01 -out server_cert.pem
Index: /trunk/doc/manual/en_US/user_GuestAdditions.xml
===================================================================
--- /trunk/doc/manual/en_US/user_GuestAdditions.xml (revision 56450)
+++ /trunk/doc/manual/en_US/user_GuestAdditions.xml (revision 56451)
@@ -362,6 +362,6 @@
will undermine a silent installation.
- On some Windows versions like Windows 2000 and Windows XP the user intervention
- popups mentioned above always will be displayed, even after importing the Oracle certificates.
+ On some Windows versions like Windows 2000 and Windows XP the user intervention
+ popups mentioned above always will be displayed, even after importing the Oracle certificates.
Since VirtualBox 4.2 installing those CA certificates on a Windows
@@ -402,62 +402,70 @@
Windows Guest Additions installer on the CD-ROM:
-
- VeriSign Code Signing CA
-
-
- In the Windows Explorer, right click on VBoxWindowsAdditions-<Architecture>.exe,
- click on "Properties"
-
-
- Go to tab "Digital Signatures", choose "Oracle Corporation" and click on "Details"
-
-
- In tab "General" click on "View Certificate"
-
-
- In tab "Certification Path" select "VeriSign Class 3 Public Primary CA"
-
-
- Click on "View Certificate"
-
-
- In tab "Details" click on "Copy to File ..."
-
-
- In the upcoming wizard choose "DER encoded binary X.509 (.CER)"
- and save the certificate file to a local path, finish the wizard
-
-
- Close certificate dialog for "Verisign Class 3 Code Signing
- 2010 CA"
-
-
-
-
-
- Oracle Corporation
-
-
- In the Windows Explorer, right click on VBoxWindowsAdditions-<Architecture>.exe,
- click on "Properties"
-
-
- Go to tab "Digital Signatures", choose "Oracle Corporation" and click on "Details"
-
-
- In tab "General" click on "View Certificate"
-
-
- In tab "Details" click on "Copy to File ..."
-
-
- In the upcoming wizard choose "DER encoded binary X.509 (.CER)"
- and save the certificate file to a local path, finish the wizard
-
-
- Close certificate dialog for "Oracle Corporation"
-
-
-
+
+
+ VeriSign Code Signing CA
+
+ Open the Windows Explorer.
+
+
+ Right click on VBoxWindowsAdditions-<Architecture>.exe,
+ click on "Properties"
+
+
+ Go to tab "Digital Signatures", choose "Oracle Corporation" and click on "Details"
+
+
+ In tab "General" click on "View Certificate"
+
+
+ In tab "Certification Path" select "VeriSign Class 3 Public Primary CA"
+
+
+ Click on "View Certificate"
+
+
+ In tab "Details" click on "Copy to File ..."
+
+
+ In the upcoming wizard choose "DER encoded binary X.509 (.CER)"
+ and save the certificate file to a local path, finish the wizard
+
+
+ Close certificate dialog for "Verisign Class 3 Code Signing
+ 2010 CA"
+
+
+
+
+
+
+ Oracle Corporation
+
+ Open the Windows Explorer.
+
+
+ Right click on VBoxWindowsAdditions-<Architecture>.exe,
+ click on "Properties"
+
+
+ Go to tab "Digital Signatures", choose "Oracle Corporation" and click on "Details"
+
+
+ In tab "General" click on "View Certificate"
+
+
+ In tab "Details" click on "Copy to File ..."
+
+
+ In the upcoming wizard choose "DER encoded binary X.509 (.CER)"
+ and save the certificate file to a local path, finish the wizard
+
+
+ Close certificate dialog for "Oracle Corporation"
+
+
+
+
+
After exporting the two certificates above they can be imported into the
@@ -647,5 +655,5 @@
In order to fully update your guest system, open a
- terminal and run yum update as root.
+ terminal and run yum update as root.
@@ -668,5 +676,5 @@
In order to fully update your guest system, open a
- terminal and run zypper update as root.
+ terminal and run zypper update as root.
@@ -706,5 +714,5 @@
In order to fully update your guest system, open a
- terminal and run zypper update as root.
+ terminal and run zypper update as root.
@@ -748,6 +756,6 @@
In order to fully update your guest system, open a
- terminal and run urpmi --auto-update
- as root.
+ terminal and run urpmi --auto-update
+ as root.
@@ -779,5 +787,5 @@
In order to fully update your guest system, open a
- terminal and run yum update as root.
+ terminal and run yum update as root.
@@ -1275,12 +1283,14 @@
implemented.
- When transferring data from the host to the guest OS, the host in this
- case is the source, whereas the guest OS is the target. However, when doing
- it the other way around, that is, transferring data from the guest OS to the
- host, the guest OS this time became the source and the host is the target.
-
- For security reasons drag'n drop can be configured at runtime
- on a per-VM basis either using the "Drag'n'Drop" menu item in the "Devices" menu
- of the virtual machine or VBoxManage: The following four modes are available:
+ When transferring data from the host to the guest OS, the host in
+ this case is the source, whereas the guest OS is the target. However, when
+ doing it the other way around, that is, transferring data from the guest OS
+ to the host, the guest OS this time became the source and the host is the
+ target.
+
+ For security reasons drag'n drop can be configured at runtime on a
+ per-VM basis either using the "Drag'n'Drop" menu item in the "Devices" menu
+ of the virtual machine or VBoxManage: The following four modes are
+ available:
@@ -1309,5 +1319,5 @@
and vice versa.
-
+
Drag'n drop support depends on the frontend being used; at the
@@ -1449,17 +1459,20 @@
Unlike the current basic Direct3D support, the WDDM video
driver installation does not require
- the "Safe Mode".
- The Aero theme is not enabled by default. To enable it
+ the "Safe Mode".
+
+ The Aero theme is not enabled by default. To enable it
+
In Windows Vista guest: right-click on the desktop, in the
context menu select "Personalize", then select "Windows Color and Appearance"
in the "Personalization" window, in the "Appearance Settings" dialog select
- "Windows Aero" and press "OK"
+ "Windows Aero" and press "OK"
+
In Windows 7 guest: right-click on the desktop, in the
context menu select "Personalize" and select any Aero theme
- in the "Personalization" window
-
-
+ in the "Personalization" window
+
+
Index: /trunk/doc/manual/en_US/user_Introduction.xml
===================================================================
--- /trunk/doc/manual/en_US/user_Introduction.xml (revision 56450)
+++ /trunk/doc/manual/en_US/user_Introduction.xml (revision 56451)
@@ -1567,6 +1567,6 @@
To experiment with a VM configuration, test different guest OS levels
or to simply backup a VM, VirtualBox can create a full or a linked copy of
- an existing VM.Cloning support was introduced with VirtualBox
- 4.1.
+ an existing VM.Cloning support was introduced with VirtualBox
+ 4.1.
A wizard will guide you through the clone process:
Index: /trunk/doc/manual/en_US/user_KnownIssues.xml
===================================================================
--- /trunk/doc/manual/en_US/user_KnownIssues.xml (revision 56450)
+++ /trunk/doc/manual/en_US/user_KnownIssues.xml (revision 56451)
@@ -12,34 +12,34 @@
- WDDM Direct3D video driver for Windows guests
-
-
- Hardware 3D acceleration support for Windows, Linux, and Solaris
- guests
-
-
- Hardware 2D video playback acceleration support for Windows
- guests
-
-
- PCI pass-through (Linux hosts only)
-
-
- Mac OS X guests (Mac hosts only)
-
-
- ICH9 chipset emulation
-
-
- EFI firmware
-
-
- Host CD/DVD drive pass-through
-
-
- Support of iSCSI via internal networking
-
-
- Synthetic CPU reporting
+ WDDM Direct3D video driver for Windows guests
+
+
+ Hardware 3D acceleration support for Windows, Linux, and Solaris
+ guests
+
+
+ Hardware 2D video playback acceleration support for Windows
+ guests
+
+
+ PCI pass-through (Linux hosts only)
+
+
+ Mac OS X guests (Mac hosts only)
+
+
+ ICH9 chipset emulation
+
+
+ EFI firmware
+
+
+ Host CD/DVD drive pass-through
+
+
+ Support of iSCSI via internal networking
+
+
+ Synthetic CPU reporting
Index: /trunk/doc/manual/en_US/user_Networking.xml
===================================================================
--- /trunk/doc/manual/en_US/user_Networking.xml (revision 56450)
+++ /trunk/doc/manual/en_US/user_Networking.xml (revision 56451)
@@ -725,7 +725,10 @@
linkend="vboxmanage-dhcpserver" /> for details.
-
- On Linux and Mac OS X hosts the number of host-only interfaces is
- limited to 128. There is no such limit for Solaris and Windows hosts.
+
+
+
+ On Linux and Mac OS X hosts the number of host-only
+ interfaces is limited to 128. There is no such limit for Solaris and
+ Windows hosts.
@@ -791,10 +794,9 @@
Internal network case.
-
- On Unix-based hosts (e.g. Linux, Solaris, Mac OS X) it is not possible
- to bind to ports below 1024 from applications that are not run by
- root. As a result, if you try to
- configure such a source UDP port, the VM will refuse to start.
-
+ On Unix-based hosts (e.g. Linux, Solaris, Mac OS X) it is
+ not possible to bind to ports below 1024 from applications that are not run
+ by root. As a result, if you try to
+ configure such a source UDP port, the VM will refuse to
+ start.
@@ -937,5 +939,5 @@
Use bridged attachment instead of
- NAT;
+ NAT;
Index: /trunk/doc/manual/en_US/user_Security.xml
===================================================================
--- /trunk/doc/manual/en_US/user_Security.xml (revision 56450)
+++ /trunk/doc/manual/en_US/user_Security.xml (revision 56451)
@@ -6,145 +6,139 @@
- Overview
-
+ General Security Principles
+
+ The following principles are fundamental to using any application
+ securely.
+
+
+ Keep Software Up To Date
+
+
+ One of the principles of good security practise is to keep all
+ software versions and patches up to date. Activate the VirtualBox
+ update notification to get notified when a new VirtualBox release
+ is available. When updating VirtualBox, do not forget to update
+ the Guest Additions. Keep the host operating system as well as the
+ guest operating system up to date.
+
+
+
+
+
+ Restrict Network Access to Critical Services
+
+
+ Use proper means, for instance a firewall, to protect your computer
+ and your guest(s) from accesses from the outside. Choosing the proper
+ networking mode for VMs helps to separate host networking from the
+ guest and vice versa.
+
+
+
+
+
+ Follow the Principle of Least Privilege
+
+
+ The principle of least privilege states that users should be given the
+ least amount of privilege necessary to perform their jobs. Always execute VirtualBox
+ as a regular user. We strongly discourage anyone from executing
+ VirtualBox with system privileges.
+
+
+ Choose restrictive permissions when creating configuration files,
+ for instance when creating /etc/default/virtualbox, see
+ . Mode 0600 would be preferred.
+
+
+
+
+
+ Monitor System Activity
+
+
+ System security builds on three pillars: good security protocols, proper
+ system configuration and system monitoring. Auditing and reviewing audit
+ records address the third requirement. Each component within a system
+ has some degree of monitoring capability. Follow audit advice in this
+ document and regularly monitor audit records.
+
+
+
+
+
+ Keep Up To Date on Latest Security Information
+
+
+ Oracle continually improves its software and documentation. Check this
+ note note yearly for revisions.
+
+
+
+
+
-
-
- General Security Principles
-
- The following principles are fundamental to using any application
- securely.
-
-
- Keep Software Up To Date
-
-
- One of the principles of good security practise is to keep all
- software versions and patches up to date. Activate the VirtualBox
- update notification to get notified when a new VirtualBox release
- is available. When updating VirtualBox, do not forget to update
- the Guest Additions. Keep the host operating system as well as the
- guest operating system up to date.
-
-
-
-
-
- Restrict Network Access to Critical Services
-
-
- Use proper means, for instance a firewall, to protect your computer
- and your guest(s) from accesses from the outside. Choosing the proper
- networking mode for VMs helps to separate host networking from the
- guest and vice versa.
-
-
-
-
-
- Follow the Principle of Least Privilege
-
-
- The principle of least privilege states that users should be given the
- least amount of privilege necessary to perform their jobs. Always execute VirtualBox
- as a regular user. We strongly discourage anyone from executing
- VirtualBox with system privileges.
-
-
- Choose restrictive permissions when creating configuration files,
- for instance when creating /etc/default/virtualbox, see
- . Mode 0600 would be preferred.
-
-
-
-
-
- Monitor System Activity
-
-
- System security builds on three pillars: good security protocols, proper
- system configuration and system monitoring. Auditing and reviewing audit
- records address the third requirement. Each component within a system
- has some degree of monitoring capability. Follow audit advice in this
- document and regularly monitor audit records.
-
-
-
-
-
- Keep Up To Date on Latest Security Information
-
-
- Oracle continually improves its software and documentation. Check this
- note note yearly for revisions.
-
-
-
-
-
-
-
Secure Installation and Configuration
+
+
+ Installation Overview
+
+ The VirtualBox base package should be downloaded only from a trusted source,
+ for instance the official website
+ http://www.virtualbox.org.
+ The integrity of the package should be verified with the provided SHA256
+ checksum which can be found on the official website.
+
+
+ General VirtualBox installation instructions for the supported hosts
+ can be found in .
+
+
+ On Windows hosts, the installer allows for disabling USB support, support
+ for bridged networking, support for host-only networking and the Python
+ language bindings, see .
+ All these features are enabled by default but disabling some
+ of them could be appropriate if the corresponding functionality is not
+ required by any virtual machine. The Python language bindings are only
+ required if the VirtualBox API is to be used by external Python
+ applications. In particular USB support and support
+ for the two networking modes require the installation of Windows kernel
+ drivers on the host. Therefore disabling those selected features can
+ not only be used to restrict the user to certain functionality but
+ also to minimize the surface provided to a potential attacker.
+
+ The general case is to install the complete VirtualBox package. The
+ installation must be done with system privileges. All VirtualBox binaries
+ should be executed as a regular user and never as a privileged user.
+
+
+ The Oracle VM VirtualBox extension pack provides additional features
+ and must be downloaded and installed separately, see
+ . As for the base package, the SHA256
+ checksum of the extension pack should be verified. As the installation
+ requires system privileges, VirtualBox will ask for the system
+ password during the installation of the extension pack.
+
+
+
+
+ Post Installation Configuration
+
+ Normally there is no post installation configuration of VirtualBox components
+ required. However, on Solaris and Linux hosts it is necessary to configure
+ the proper permissions for users executing VMs and who should be able to
+ access certain host resources. For instance, Linux users must be member of
+ the vboxusers group to be able to pass USB devices to a
+ guest. If a serial host interface should be accessed from a VM, the proper
+ permissions must be granted to the user to be able to access that device.
+ The same applies to other resources like raw partitions, DVD/CD drives
+ and sound devices.
+
+
-
-
- Installation Overview
-
- The VirtualBox base package should be downloaded only from a trusted source,
- for instance the official website
- http://www.virtualbox.org.
- The integrity of the package should be verified with the provided SHA256
- checksum which can be found on the official website.
-
-
- General VirtualBox installation instructions for the supported hosts
- can be found in .
-
-
- On Windows hosts, the installer allows for disabling USB support, support
- for bridged networking, support for host-only networking and the Python
- language bindings, see .
- All these features are enabled by default but disabling some
- of them could be appropriate if the corresponding functionality is not
- required by any virtual machine. The Python language bindings are only
- required if the VirtualBox API is to be used by external Python
- applications. In particular USB support and support
- for the two networking modes require the installation of Windows kernel
- drivers on the host. Therefore disabling those selected features can
- not only be used to restrict the user to certain functionality but
- also to minimize the surface provided to a potential attacker.
-
- The general case is to install the complete VirtualBox package. The
- installation must be done with system privileges. All VirtualBox binaries
- should be executed as a regular user and never as a privileged user.
-
-
- The Oracle VM VirtualBox extension pack provides additional features
- and must be downloaded and installed separately, see
- . As for the base package, the SHA256
- checksum of the extension pack should be verified. As the installation
- requires system privileges, VirtualBox will ask for the system
- password during the installation of the extension pack.
-
-
-
-
- Post Installation Configuration
-
- Normally there is no post installation configuration of VirtualBox components
- required. However, on Solaris and Linux hosts it is necessary to configure
- the proper permissions for users executing VMs and who should be able to
- access certain host resources. For instance, Linux users must be member of
- the vboxusers group to be able to pass USB devices to a
- guest. If a serial host interface should be accessed from a VM, the proper
- permissions must be granted to the user to be able to access that device.
- The same applies to other resources like raw partitions, DVD/CD drives
- and sound devices.
-
-
-
+
Security Features
Index: /trunk/doc/manual/en_US/user_ThirdParty.xml
===================================================================
--- /trunk/doc/manual/en_US/user_ThirdParty.xml (revision 56450)
+++ /trunk/doc/manual/en_US/user_ThirdParty.xml (revision 56451)
@@ -3036,9 +3036,6 @@
Copyright 1996-2002, 2006 by David Turner, Robert Wilhelm, and Werner Lemberg
-
+
Introduction
-
-
-
The FreeType Project is distributed in several archive packages;
@@ -3100,6 +3097,6 @@
actually use.
-
-
+
+
Legal Terms
@@ -3157,4 +3154,5 @@
+
Redistribution of source code must retain this license file
(`FTL.TXT') unaltered; any additions, deletions or changes to
@@ -3163,6 +3161,8 @@
original files must be preserved in all copies of source
files.
+
+
Redistribution in binary form must provide a disclaimer that
states that the software is based in part of the work of the
@@ -3170,4 +3170,5 @@
encourage you to put an URL to the FreeType web page in your
documentation, though this isn't mandatory.
+
@@ -3236,5 +3237,5 @@
-
+
Index: /trunk/doc/manual/en_US/user_VBoxManage.xml
===================================================================
--- /trunk/doc/manual/en_US/user_VBoxManage.xml (revision 56450)
+++ /trunk/doc/manual/en_US/user_VBoxManage.xml (revision 56451)
@@ -889,5 +889,4 @@
- This allows you to change the address range occupied by
--bridgeadapter<1-N>
@@ -4321,9 +4320,9 @@
of registers, each having one of the following forms:
- register-set.register-name.sub-field
- register-set.register-name
- cpu-register-name.sub-field
- cpu-register-name
- all
+ register-set.register-name.sub-field
+ register-set.register-name
+ cpu-register-name.sub-field
+ cpu-register-name
+ all
The all form will cause all
@@ -4340,8 +4339,8 @@
of register assignments, each having one of the following forms:
- register-set.register-name.sub-field=value
- register-set.register-name=value
- cpu-register-name.sub-field=value
- cpu-register-name=value
+ register-set.register-name.sub-field=value
+ register-set.register-name=value
+ cpu-register-name.sub-field=value
+ cpu-register-name=value
The value format should be in the same style as what