Commit 8ad77fa0 authored by Tails developers's avatar Tails developers

Merge remote-tracking branch 'origin/doc/7143-virtualization' (Closes: #7143).

parents 48342fb2 efc7e6f7
......@@ -54,7 +54,7 @@ my $summary = gettext("Warning: virtual machine detected!");
my $body =
gettext("Both the host operating system and the virtualization software are able to monitor what you are doing in Tails.")
. " "
. gettext("<a href='file:///usr/share/doc/tails/website/doc/advanced_topics/virtualization.en.html'>Learn more...</a>")
. gettext("<a href='file:///usr/share/doc/tails/website/doc/advanced_topics/virtualization.en.html#security'>Learn more...</a>")
. " "; # Workaround: else the last line of the notification is not displayed
$notify->create(summary => $summary,
......
......@@ -406,10 +406,10 @@ msgstr ""
#: config/chroot_local-includes/usr/local/bin/tails-virt-notify-user:57
msgid ""
"<a href='file:///usr/share/doc/tails/website/doc/advanced_topics/"
"virtualization.en.html'>Learn more...</a>"
"virtualization.en.html#security'>Learn more...</a>"
msgstr ""
"<a href='file:///usr/share/doc/tails/website/doc/advanced_topics/"
"virtualization.fr.html'>En savoir plus...</a>"
"virtualization.fr.html#security'>En savoir plus...</a>"
#: config/chroot_local-includes/usr/local/bin/tor-browser:18
msgid "Tor is not ready"
......
- [[!traillink Protection_against_cold_boot_attacks|advanced_topics/cold_boot_attacks]]
- [[!traillink Virtualization|advanced_topics/virtualization]]
- [[!traillink <span_class="application">VirtualBox</span>|advanced_topics/virtualization/virtualbox]]
- [[!traillink <span_class="application">GNOME_Boxes</span>|advanced_topics/virtualization/boxes]]
- [[!traillink <span_class="application">virt-manager</span>|advanced_topics/virtualization/virt-manager]]
- [[!traillink Enable_a_wireless_device|advanced_topics/wireless_devices]]
<div class="caution">
Running Tails inside a virtual machine has [[various security
implications|virtualization#security]]. Depending on the host operating system and your security
needs, running Tails in a virtual machine might be dangerous.
</div>
......@@ -2,52 +2,124 @@
[[!toc levels=2]]
Certain users might not want to restart the computer every time they
wish to use the Internet anonymously with Tails. For those, a so
called [virtual machine](http://en.wikipedia.org/wiki/Virtual_machine)
can be used to run Tails inside the "host" operating system
installed on the computer (e.g. Microsoft Windows, Mac OS X, etc.).
Essentially these programs emulate real computers that you can run
"guest" operating systems (in this case Tails) in so they appear in
a window within the host operating system. Using one of these
technologies allows for convenient access to Tails's features in a
protected environment while you at the same time have access to your
normal operation system.
It is sometimes convenient to be able to run Tails without having to
restart your computer every time. This is possible using
[[!wikipedia Virtual_machine desc="virtual machines"]].
Security issues
===============
With virtual machines, it is possible to run Tails inside a *host*
operating system (Linux, Windows, or Mac OS&nbsp;X). A virtual machine
emulates a real computer and its operating system, called *guest* which
appears in a window on the *host* operating system.
There are a few security issues with this approach though.
When running Tails in a virtual machine, you can use most features of
Tails from your usual operating system and use both in parallel
without the need to restart the computer.
When running Tails inside a virtual machine, both the host operating system
and the virtualization software are able to monitor what you are doing in
Tails.
This is how Tails looks like when run in a virtual machine on Debian using *VirtualBox*:
The main issue is if the host operating system is compromised with a software
keylogger or other malware, which Tails does not provide any protection against
– in fact, that is impossible.
[[!img tails-in-jessie.png alt="Tails running in a VirtuaBox window inside a Debian desktop with GNOME 3" link=no]]
Moreover traces are likely to be left on the local hard disk.
<div class="note">
As such, this is only recommended when the other alternative is not an option
or when you are absolutely sure that your host system is clean.
<p>We do not currently provide a solution for running a virtual machine
inside a Tails host. See [[!tails_ticket 5606]].</p>
That's why Tails warns you when you are running it inside a virtual
machine. Do not expect Tails to protect you if you run it in a virtual
machine if you do not trust the host computer, Tails is not magical!
</div>
If you read this warning while you are not aware to be using a virtual
machine: there could be a [[bug|support/found_a_problem]] in the
virtualization detection software Tails uses... or something really
weird is happening.
<a id="security"></a>
If you are unsure, and if you can afford it, run Tails from a DVD,
USB stick or SD card instead.
Security considerations
=======================
Tips and tricks
===============
<div class="caution">
Some [[tips]] can help making the host
operating system and virtualization software a tiny bit more secure.
Running Tails inside a virtual machine has various security
implications. Depending on the host operating system and your security
needs, running Tails in a virtual machine might be dangerous.
In the future, it will be possible to easily start [[Tails within Windows]].
</div>
<a id="trustworthy"></a>
- Both the host operating system and the [[virtualization
software|virtualization#software]] are able to monitor what you are
doing in Tails.
If the host operating system is compromised with a software
keylogger or other malware, then it can break the security features
of Tails.
<div class="caution">
Only run Tails in a virtual machine if the host operating system is
trustworthy.
</div>
<a id="traces"></a>
- Traces of your Tails session are likely to be left on the local hard
disk. For example, host operating systems usually use swapping (or *paging*) which
copies part of the RAM to the hard disk.
<div class="caution">
Only run Tails in a virtual machine if leaving traces on the hard disk
is not a concern for you.
</div>
This is why Tails warns you when it is running inside a virtual machine.
<div class="note">
The Tails virtual machine does not modify the behaviour of the host
operating system and the network traffic of the host is not anonymized. The MAC
address of the computer is not modified by the [[MAC address
spoofing|first_steps/startup_options/mac_spoofing]] feature of Tails
when run in a virtual machine.
</div>
<a id="software"></a>
Virtualization solutions
========================
To run Tails inside a virtual machine, you need to have
virtualization software installed on the host operating system.
Different virtualization software exist for Linux, Windows, and Mac OS&nbsp;X.
<div class="note">
<p>The following list includes only free software as we believe that
this is a necessary condition for it to be trustworthy. See the
[[previous warning|virtualization#trustworthy]] and our statement about
[[free software and public scrutiny|about/trust#free_software]].</p>
<p>Proprietary virtualization software solutions exist such as <span
class="application">VMWare</span> but are not listed here on
purpose.</p>
</div>
- *VirtualBox* is available for Linux, Windows, and Mac. Its
free software version does not include support for USB devices and
does not allow to use a persistent volume.
[[See the corresponding documentation.|virtualbox]]
- *GNOME Boxes* is available for Linux. It has a simple user
interface but does not allow to use a persistent volume.
[[See the corresponding documentation.|boxes]]
- *virt-manager* is available for Linux. It has a more
complex user interface and allows to use a persistent volume, either
by:
- Starting Tails from a USB stick or SD card.
- Creating a virtual USB storage volume saved as a single file on the host
operating system.
[[See the corresponding documentation.|virt-manager]]
[[!meta title="GNOME Boxes"]]
[<span class="application">GNOME Boxes</span>](https://wiki.gnome.org/Boxes) aims at providing a simple
interface to create and use virtual machines for Linux with GNOME.
*GNOME Boxes* does not allow to use a persistent volume.
[[!inline pages="doc/advanced_topics/virtualization.caution" raw="yes"]]
<div class="note">
<p>In Debian Wheezy, Ubuntu 14.04, and earlier,
<span class="application">GNOME Boxes</span> allocates only 512 MiB of
RAM to new virtual machines by default. This is too little to allow
Tails to run smoothly. We recommend you to reconfigure the virtual
machine and allocate at least 1 GiB of RAM.</p>
</div>
Installation
============
To install *GNOME Boxes* in Debian or Ubuntu, execute the following
command:
sudo apt-get install gnome-boxes
Running Tails from an ISO image
===============================
1. Start *GNOME Boxes*.
2. Click on the **New** button on the top of the window.
3. In the **Source Selection** dialog, choose **Select a file** and
browse for the ISO image that you want to start from.
4. In the **Review** dialog, click on the **Create** button on the top
of the window.
Shared clipboard
================
<div class="caution">
<p>The shared clipboard of <span class="application">GNOME Boxes</span>
is enabled by default. This can allow sensitive data to be copied by
mistake from the virtual machine onto the host operating system or vice
versa.</p>
<p>We recommend you to disable the shared clipboard.</p>
</div>
To disable the shared clipboard:
1. Click on the
[[!img preferences-system-symbolic.png alt="Preferences" class=symbolic link=no]]
button on the top-right corner of the window.
2. Select the **Display** screen in the left pane.
3. Deactivate **Share clipboard** in the right pane.
4. Click on the
[[!img go-previous-symbolic.png alt="Previous" class=symbolic link=no]]
button to go back to the display of the virtual machine.
# SOME DESCRIPTIVE TITLE
# Copyright (C) YEAR Free Software Foundation, Inc.
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2011-06-18 22:40+0300\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. type: Plain text
#, no-wrap
msgid "[[!meta title=\"Running Tails from within Microsoft Windows\"]]\n"
msgstr ""
#. type: Plain text
#, no-wrap
msgid ""
"**FIXME**: This section have not been adapted from old incognito documentation\n"
"now so please do not take it into account. It is currently possible to start\n"
"Tails under Windows with QEMU.\n"
msgstr ""
#. type: Plain text
msgid ""
"Thanks to QEMU, Tails can be run within Microsoft Windows without the need to "
"restart the computer. QEMU ships with Tails, and is set up so you only have "
"to insert the media when Windows is running and a menu should appear with the "
"option to start Tails through it. This is especially useful when you are "
"using a computer you are not allowed to shut-down, which can be the case for "
"public computers in certain Internet cafés, libraries or other public "
"computers. Also, for some some general remarks on QEMU and Tails, and some "
"security concerns about this mode of operation, see the above section on "
"[[virtualization]]."
msgstr ""
#. type: Plain text
msgid ""
"Since the Tails developers do not have access to any Windows computers at the "
"moment, any input if this actually works and how it performs etc. is welcome."
msgstr ""
# SOME DESCRIPTIVE TITLE
# Copyright (C) YEAR Free Software Foundation, Inc.
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2011-06-18 22:40+0300\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. type: Plain text
#, no-wrap
msgid "[[!meta title=\"Running Tails from within Microsoft Windows\"]]\n"
msgstr ""
#. type: Plain text
#, no-wrap
msgid ""
"**FIXME**: This section have not been adapted from old incognito documentation\n"
"now so please do not take it into account. It is currently possible to start\n"
"Tails under Windows with QEMU.\n"
msgstr ""
#. type: Plain text
msgid ""
"Thanks to QEMU, Tails can be run within Microsoft Windows without the need to "
"restart the computer. QEMU ships with Tails, and is set up so you only have "
"to insert the media when Windows is running and a menu should appear with the "
"option to start Tails through it. This is especially useful when you are "
"using a computer you are not allowed to shut-down, which can be the case for "
"public computers in certain Internet cafés, libraries or other public "
"computers. Also, for some some general remarks on QEMU and Tails, and some "
"security concerns about this mode of operation, see the above section on "
"[[virtualization]]."
msgstr ""
#. type: Plain text
msgid ""
"Since the Tails developers do not have access to any Windows computers at the "
"moment, any input if this actually works and how it performs etc. is welcome."
msgstr ""
[[!meta title="Running Tails from within Microsoft Windows"]]
**FIXME**: This section have not been adapted from old incognito documentation
now so please do not take it into account. It is currently possible to start
Tails under Windows with QEMU.
Thanks to QEMU, Tails can be run within
Microsoft Windows without the need to restart the computer. QEMU ships
with Tails, and is set up so you only have to insert the media when
Windows is running and a menu should appear with the option to start
Tails through it. This is especially useful when you are using a
computer you are not allowed to shut-down, which can be the case for
public computers in certain Internet cafés, libraries or other public
computers. Also, for some some general remarks on QEMU and Tails,
and some security concerns about this mode of operation, see the above
section on [[virtualization]].
Since the Tails developers do not have access to any Windows
computers at the moment, any input if this actually works and how it
performs etc. is welcome.
# SOME DESCRIPTIVE TITLE
# Copyright (C) YEAR Free Software Foundation, Inc.
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2012-05-17 15:08+0300\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. type: Plain text
#, no-wrap
msgid "[[!meta title=\"Running Tails from within Microsoft Windows\"]]\n"
msgstr ""
#. type: Plain text
#, no-wrap
msgid ""
"**FIXME**: This section have not been adapted from old incognito "
"documentation\n"
"now so please do not take it into account. It is currently possible to "
"start\n"
"Tails under Windows with QEMU.\n"
msgstr ""
#. type: Plain text
msgid ""
"Thanks to QEMU, Tails can be run within Microsoft Windows without the need "
"to restart the computer. QEMU ships with Tails, and is set up so you only "
"have to insert the media when Windows is running and a menu should appear "
"with the option to start Tails through it. This is especially useful when "
"you are using a computer you are not allowed to shut-down, which can be the "
"case for public computers in certain Internet cafés, libraries or other "
"public computers. Also, for some some general remarks on QEMU and Tails, and "
"some security concerns about this mode of operation, see the above section "
"on [[virtualization]]."
msgstr ""
#. type: Plain text
msgid ""
"Since the Tails developers do not have access to any Windows computers at "
"the moment, any input if this actually works and how it performs etc. is "
"welcome."
msgstr ""
# SOME DESCRIPTIVE TITLE
# Copyright (C) YEAR Free Software Foundation, Inc.
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2011-11-20 16:40+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. type: Plain text
#, no-wrap
msgid "[[!meta title=\"Virtualization: tips and tricks\"]]\n"
msgstr ""
#. type: Plain text
#, no-wrap
msgid "[[!toc levels=2]]\n"
msgstr ""
#. type: Plain text
msgid ""
"As explained on the [[virtualization warning page|advanced_topics/"
"virtualization]], using Tails in a Virtual Machine involves you put great "
"trust into the host operating system and the virtualization software."
msgstr ""
#. type: Plain text
msgid "Here are some tips may help hardening (a bit) the host operating system."
msgstr ""
#. type: Title #
#, no-wrap
msgid "Operating systems"
msgstr ""
#. type: Title ##
#, no-wrap
msgid "Microsoft Windows"
msgstr ""
#. type: Plain text
msgid ""
"You should NOT trust Windows to be secure if you use Tails for anything you "
"consider risky. Windows could be made a tiny bit more trustworthy if you "
"installed a HIPS (Host Intrusion Prevention System) with high security "
"settings instantly after installing Windows. If Windows not is installed from "
"a genuine Windows CD/DVD you can not trust it enough, not even if it's a "
"preinstalled copy of Windows (there have been cases of computers being "
"shipped with malware). If you install a HIPS first after using Windows for "
"some time (less then an hour online is enough) you could already have a "
"rootkit that the HIPS can't detect. Even with a HIPS you should not use "
"Windows as a host OS if you risk personal harm for your use of Tails."
msgstr ""
#. type: Title #
#, no-wrap
msgid "Virtualization solutions"
msgstr ""
#. type: Title ##
#, no-wrap
msgid "VirtualBox"
msgstr ""
#. type: Plain text
msgid ""
"Tails runs in [VirtualBox](http://virtualbox.org) without any major "
"configuration necessary. VirtualBox is distributed both as a closed-source "
"and as an open-source (the so called OSE or Open Source Edition), the latter "
"which the Tails developer's encourages (although it currently lacks USB "
"support compared to the closed-source version)."
msgstr ""
# SOME DESCRIPTIVE TITLE
# Copyright (C) YEAR Free Software Foundation, Inc.
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2011-11-20 16:40+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. type: Plain text
#, no-wrap
msgid "[[!meta title=\"Virtualization: tips and tricks\"]]\n"
msgstr ""
#. type: Plain text
#, no-wrap
msgid "[[!toc levels=2]]\n"
msgstr ""
#. type: Plain text
msgid ""
"As explained on the [[virtualization warning page|advanced_topics/"
"virtualization]], using Tails in a Virtual Machine involves you put great "
"trust into the host operating system and the virtualization software."
msgstr ""
#. type: Plain text
msgid "Here are some tips may help hardening (a bit) the host operating system."
msgstr ""
#. type: Title #
#, no-wrap
msgid "Operating systems"
msgstr ""
#. type: Title ##
#, no-wrap
msgid "Microsoft Windows"
msgstr ""
#. type: Plain text
msgid ""
"You should NOT trust Windows to be secure if you use Tails for anything you "
"consider risky. Windows could be made a tiny bit more trustworthy if you "
"installed a HIPS (Host Intrusion Prevention System) with high security "
"settings instantly after installing Windows. If Windows not is installed from "
"a genuine Windows CD/DVD you can not trust it enough, not even if it's a "
"preinstalled copy of Windows (there have been cases of computers being "
"shipped with malware). If you install a HIPS first after using Windows for "
"some time (less then an hour online is enough) you could already have a "
"rootkit that the HIPS can't detect. Even with a HIPS you should not use "
"Windows as a host OS if you risk personal harm for your use of Tails."
msgstr ""
#. type: Title #
#, no-wrap
msgid "Virtualization solutions"
msgstr ""
#. type: Title ##
#, no-wrap
msgid "VirtualBox"
msgstr ""
#. type: Plain text
msgid ""
"Tails runs in [VirtualBox](http://virtualbox.org) without any major "
"configuration necessary. VirtualBox is distributed both as a closed-source "
"and as an open-source (the so called OSE or Open Source Edition), the latter "
"which the Tails developer's encourages (although it currently lacks USB "
"support compared to the closed-source version)."
msgstr ""
[[!meta title="Virtualization: tips and tricks"]]
[[!toc levels=2]]
As explained on the [[virtualization warning
page|advanced_topics/virtualization]], using Tails in a Virtual Machine
involves you put great trust into the host operating system and the
virtualization software.
Here are some tips may help hardening (a bit) the host operating
system.
# Operating systems
## Microsoft Windows
You should NOT trust Windows to be secure if you use Tails for
anything you consider risky. Windows could be made a tiny bit more
trustworthy if you installed a HIPS (Host Intrusion Prevention System)
with high security settings instantly after installing Windows. If
Windows not is installed from a genuine Windows CD/DVD you can not
trust it enough, not even if it's a preinstalled copy of Windows
(there have been cases of computers being shipped with malware). If
you install a HIPS first after using Windows for some time (less then
an hour online is enough) you could already have a rootkit that the
HIPS can't detect. Even with a HIPS you should not use Windows as a
host OS if you risk personal harm for your use of Tails.
# Virtualization solutions
## VirtualBox
Tails runs in [VirtualBox](http://virtualbox.org) without any major configuration
necessary. VirtualBox is distributed both as a closed-source and as an
open-source (the so called OSE or Open Source Edition), the latter which the
Tails developer's encourages (although it currently lacks USB support compared
to the closed-source version).