How to copy and paste text
This page is about copying and pasting plain text. If you wish to copy more complex data, such as rich text or images, see copying and moving files between qubes. For dom0, see copying from (and to) dom0.
Qubes OS features a secure inter-qube clipboard that allows you to copy and paste text between qubes.
In order to copy text from qube A to qube B:
Select text from the source app in qube A, then copy it normally (e.g., by pressing Ctrl+C).
With the source app in qube A still in focus, press Ctrl+Shift+C. This copies the text from qube A’s clipboard to the inter-qube clipboard.
Select the target app in qube B and press Ctrl+Shift+V. This copies the text from the inter-qube clipboard to qube B’s clipboard and clears the inter-qube clipboard, ensuring that only qube B will have access to the copied text.
Paste the text in the target app in qube B normally (e.g., by pressing Ctrl+V).
This process might look complicated at first glance, but in practice it is actually very easy and fast once you get used to it. At the same time, it provides you with full control over exactly which qube receives the content of the inter-qube clipboard every time.
The inter-qube clipboard system is secure because it doesn’t allow any qube other than your selected target to steal any contents from the inter-qube clipboard.
Without such a system in place, any password you were to copy from the password manager in your vault qube to another qube, for example, would immediately be leaked to every other running qube in the system, including qubes that are untrusted by default, such as
By giving you precise control over exactly which qube receives the inter-qube clipboard content, then immediately wiping the inter-qube clipboard afterward, Qubes OS protects the confidentiality of the text being copied.
However, one should keep in mind that performing a copy and paste operation from less trusted to more trusted qube is always potentially insecure, since the data that we copy could exploit some hypothetical bug in the target qube. For example, the seemingly-innocent link that we copy from an untrusted qube could turn out to be a large buffer of junk that, when pasted into the target qube’s word processor, could exploit a hypothetical bug in the undo buffer. This is a general problem and applies to any data transfer from less trusted to more trusted qubes. It even applies to copying files between physically separate (air-gapped) machines. Therefore, you should always copy clipboard data only from more trusted to less trusted qubes.
The above discussion assumes that you control which window is focused in dom0 at the time of the paste.
However, if your dom0 window manager is configured to give focus to newly created windows (which, as of Qubes 4.0, is true in the default install with Xfce), then a malicious qube could “steal the focus” by creating a window just before you press Ctrl+Shift+V, and it would receive the data instead of your intended target.
(Focus stealing is a risk any time you are typing confidential data, but a Qubes clipboard paste probably presents the greatest risk of leaking an entire password before you have time to react.)
You may be able to mitigate this risk by changing the window manager configuration.
For example, with Xfce, you could run
xfwm4-settings in dom0, go to the “Focus” tab, and un-check “Automatically give focus to newly created windows”.
However, we have not confirmed whether such settings are sufficient to prevent a malicious qube from stealing the focus in all cases.
Clipboard automatic policy enforcement
The Qubes clipboard RPC policy is configurable in:
You may wish to configure this policy in order to prevent user error. For example, if you are certain that you never wish to paste into your “vault” app qube (and it is highly recommended that you do not), then you should edit the policy as follows:
@anyvm vault deny @anyvm @anyvm ask
The copy/paste shortcuts are configurable in:
If you edit a line in this file, you must uncomment it (by removing the initial
# character), or else it will have no effect.
VMs need to be restarted in order for changes in
/etc/qubes/guid.conf to take effect.