Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2025-12-20 10:05:15 -05:00
Code Issues Projects Releases Packages Wiki Activity

pr#1586

Browse source 
Small grammar fixes
https://github.com/QubesOS/qubes-doc/pull/1586
This commit is contained in:
Solène Rapenne 2025-12-16 11:45:01 +01:00
commit 7eb0ac37d4
No known key found for this signature in database
GPG key ID: 8CD42DFD57F0A909
1 changed files with 6 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

12
user/how-to-guides/how-to-enter-fullscreen-mode.rst
View file

@ -13,7 +13,7 @@ This page discusses the security implications of fullscreen mode and alternate s
What is fullscreen mode?
------------------------
Normally, the Qubes GUI virtualization daemon restricts any qube from ”owning” the full screen, ensuring that there are always clearly marked decorations drawn by the trusted Window Manager around each of the qubes windows. This allows the user to easily realize to which domain a specific window belongs.
Normally, the Qubes GUI virtualization daemon restricts any qube from ”owning” the full screen, ensuring that there are always clearly marked decorations drawn by the trusted Window Manager around each of the qubes' windows. This allows the user to easily realize to which domain a specific window belongs.
.. figure:: /attachment/doc/how-to-enter-fullscreen-mode/fullscreen-from-disposable-fail.png
:alt:
@ -36,7 +36,7 @@ Secure use of fullscreen mode
However, it is possible to deal with fullscreen mode in a secure way assuming there are mechanisms that can be used at any time to switch between windows or show the full desktop and that cannot be intercepted by the qube. The simplest example is the use of :kbd:`Alt` + :kbd:`Tab` for switching between windows, which is a shortcut handled by dom0.
Other examples of such mechanisms are the KDE “Present Windows” and “Desktop Grid” effects, which are similar to Mac’s “Expose” effect, and which can be used to immediately detect potential “GUI forgery”, as they cannot be intercepted by any of the qube (as the GUID never passes down the key combinations that got consumed by KDE Window Manager), and so the qube cannot emulate those. Those effects are enabled by default in KDE once Compositing gets enabled in KDE (:menuselection:`System Settings --> Desktop --> Enable Desktop Effects`), which is recommended anyway. By default, they are triggered by the :kbd:`Ctrl` + :kbd:`F8` and :kbd:`Ctrl` + :kbd:`F9` key combinations, but can also be reassigned to other shortcuts.
Other examples of such mechanisms are the KDE “Present Windows” and “Desktop Grid” effects, which are similar to Mac’s “Expose” effect, and which can be used to immediately detect potential “GUI forgery”, as they cannot be intercepted by any of the qube (as the GUID never passes down the key combinations that got consumed by the KDE Window Manager), and so the qube cannot emulate those. Those effects are enabled by default in KDE once Compositing gets enabled in KDE (:menuselection:`System Settings --> Desktop --> Enable Desktop Effects`), which is recommended anyway. By default, they are triggered by the :kbd:`Ctrl` + :kbd:`F8` and :kbd:`Ctrl` + :kbd:`F9` key combinations, but can also be reassigned to other shortcuts.
Safely enabling fullscreen mode for a selected window
-----------------------------------------------------
@ -66,14 +66,14 @@ In the qube's settings, go to the second tab, called :guilabel:`Advanced`. Under
With the command-line, targeting the qube
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
In dom0, run the following command, replacing :samp:`{<QUBE_NAME>}` by the actual name of the qube:
In dom0, run the following command, replacing :samp:`{<QUBE_NAME>}` with the actual name of the qube:
.. code:: console
[user@dom0] $ qvm-features <QUBE_NAME> gui-allow-fullscreen 1
Enabling fullscreen mode for every qubes
----------------------------------------
Enabling fullscreen mode for every qube
---------------------------------------
.. warning:: Be sure to read :ref:`secure-use-of-fullscreen-mode` first.
@ -85,7 +85,7 @@ Open :guilabel:`Qubes Global Config`. In the first tab (called :guilabel:`Genera
.. image:: /attachment/doc/how-to-enter-fullscreen-mode/qubes-global-config-allow-fullscreen.png
:alt:
With the command-line, on dom0
With the command-line, in dom0
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
In dom0, run the following command: