mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2024-10-01 01:25:40 -04:00
change applicable images to 4.1 screenshots
This commit is contained in:
hackerncoder
parent
c6b9f6cdfa
commit
ef890d4253
@ -186,8 +186,8 @@ redirect_from:
|
|||||||
</p>
|
</p>
|
||||||
</div>
|
</div>
|
||||||
<div class="col-lg-6 col-md-6">
|
<div class="col-lg-6 col-md-6">
|
||||||
<a href="/attachment/wiki/GettingStarted/r2b1-qubes-manager-2.png">
|
<a href="/attachment/wiki/GettingStarted/r4.1-qubes-manager-2.png">
|
||||||
<img src="/attachment/wiki/GettingStarted/r2b1-qubes-manager-2.png"
|
<img src="/attachment/wiki/GettingStarted/r4.1-qubes-manager-2.png"
|
||||||
class="center-block more-bottom" alt="Qube Manager">
|
class="center-block more-bottom" alt="Qube Manager">
|
||||||
</a>
|
</a>
|
||||||
</div>
|
</div>
|
||||||
@ -268,8 +268,8 @@ redirect_from:
|
|||||||
</p>
|
</p>
|
||||||
</div>
|
</div>
|
||||||
<div class="col-lg-6 col-md-6">
|
<div class="col-lg-6 col-md-6">
|
||||||
<a href="/attachment/wiki/GettingStarted/snapshot12.png">
|
<a href="/attachment/wiki/GettingStarted/r4.1-snapshot12.png">
|
||||||
<img src="/attachment/wiki/GettingStarted/snapshot12.png"
|
<img src="/attachment/wiki/GettingStarted/r4.1-snapshot12.png"
|
||||||
class="center-block more-bottom" alt="Qubes desktop screenshot">
|
class="center-block more-bottom" alt="Qubes desktop screenshot">
|
||||||
</a>
|
</a>
|
||||||
</div>
|
</div>
|
||||||
|
|||||||
@ -11,19 +11,19 @@ redirect_from:
|
|||||||
Select Qubes OS Screenshots
|
Select Qubes OS Screenshots
|
||||||
===========================
|
===========================
|
||||||
|
|
||||||
[](/attachment/wiki/QubesScreenshots/r32-xfce-desktop.png)
|
[](/attachment/wiki/QubesScreenshots/r4.1-xfce-desktop.png)
|
||||||
|
|
||||||
The default desktop environment is Xfce4.
|
The default desktop environment is Xfce4.
|
||||||
|
|
||||||
* * * * *
|
* * * * *
|
||||||
|
|
||||||
[](/attachment/wiki/QubesScreenshots/r2b2-kde-start-menu.png)
|
[](/attachment/wiki/QubesScreenshots/r4.1-xfce-start-menu.png)
|
||||||
|
|
||||||
Starting applications from different domains (AppVMs) is very easy.
|
Starting applications from different domains (AppVMs) is very easy.
|
||||||
|
|
||||||
* * * * *
|
* * * * *
|
||||||
|
|
||||||
[](/attachment/wiki/QubesScreenshots/r2b2-kde-three-domains-at-work.png)
|
[](/attachment/wiki/QubesScreenshots/r4.1-xfce-three-domains-at-work.png)
|
||||||
|
|
||||||
In this example, the word processor runs in the “work” domain, which has been assigned the “green” label. It is fully isolated from other domains, such as the “untrusted” domain (assigned the “red” label -- “Watch out!”, “Danger!”) used for random Web browsing, news reading, as well as from the "work-web" domain (assigned the "yellow" label), which is used for work-related Web browsing that is not security critical. Apps from different domains run in different AppVMs and have different X servers, filesystems, etc. Notice the different color frames (labels) and VM names in the titlebars. These are drawn by the trusted Window Manager running in Dom0, and apps running in domains cannot fake them:
|
In this example, the word processor runs in the “work” domain, which has been assigned the “green” label. It is fully isolated from other domains, such as the “untrusted” domain (assigned the “red” label -- “Watch out!”, “Danger!”) used for random Web browsing, news reading, as well as from the "work-web" domain (assigned the "yellow" label), which is used for work-related Web browsing that is not security critical. Apps from different domains run in different AppVMs and have different X servers, filesystems, etc. Notice the different color frames (labels) and VM names in the titlebars. These are drawn by the trusted Window Manager running in Dom0, and apps running in domains cannot fake them:
|
||||||
|
|
||||||
@ -41,61 +41,61 @@ Windows AppVMs are fully integrated with the rest of the Qubes OS system, which
|
|||||||
|
|
||||||
* * * * *
|
* * * * *
|
||||||
|
|
||||||
[](/attachment/wiki/QubesScreenshots/r2b2-xfce4-programmers-desktop-2.png)
|
[](/attachment/wiki/QubesScreenshots/r4.1-xfce-programmers-desktop.png)
|
||||||
|
|
||||||
Here we see Xfce4.10 Window Manager running in Dom0 (instead of KDE as on previous screens). Qubes supports customized Xfce4 in dom0 beginning with R2 Beta 2!
|
Here we see Xfce4.10 Window Manager running in Dom0 (instead of KDE as on previous screens). Qubes supports customized Xfce4 in dom0 beginning with R2 Beta 2!
|
||||||
|
|
||||||
* * * * *
|
* * * * *
|
||||||
|
|
||||||
[](/attachment/wiki/QubesScreenshots/password-prompt.png)
|
[](/attachment/wiki/QubesScreenshots/r4.1-password-prompt.png)
|
||||||
|
|
||||||
It is always clearly visible to which domain a given window belongs. Here it’s immediately clear that the passphrase-prompting window belongs to some domain with the “green” label. When we look at the titlebar, we see “[work]”, which is the name of the actual domain. Theoretically, the untrusted application (here, the “red” Firefox) beneath the prompt window could draw a similar looking window within its contents. In practice, this would be very hard, because it doesn’t know, e.g., the exact decoration style that is in use. However, if this is a concern, the user can simply try to move the more trusted window onto some empty space on the desktop such that no other window is present beneath it. Or, better yet, use the Expose-like effect (available via a hot-key). A malicious application from an untrusted domain cannot spoof the whole desktop because the trusted Window Manager will never let any domain “own” the whole screen. Its titlebar will always be visible.
|
It is always clearly visible to which domain a given window belongs. Here it’s immediately clear that the passphrase-prompting window belongs to some domain with the “green” label. When we look at the titlebar, we see “[work]”, which is the name of the actual domain. Theoretically, the untrusted application (here, the “red” Firefox) beneath the prompt window could draw a similar looking window within its contents. In practice, this would be very hard, because it doesn’t know, e.g., the exact decoration style that is in use. However, if this is a concern, the user can simply try to move the more trusted window onto some empty space on the desktop such that no other window is present beneath it. Or, better yet, use the Expose-like effect (available via a hot-key). A malicious application from an untrusted domain cannot spoof the whole desktop because the trusted Window Manager will never let any domain “own” the whole screen. Its titlebar will always be visible.
|
||||||
|
|
||||||
* * * * *
|
* * * * *
|
||||||
|
|
||||||
[](/attachment/wiki/QubesScreenshots/r2b2-kde-tray-icons.png)
|
[](/attachment/wiki/QubesScreenshots/r4.1-xfce-tray-icons.png)
|
||||||
|
|
||||||
Qubes is all about seamless integration from the user’s point of view. Here you can see how it virtualizes tray icons from other domains. Notice the network icon in a red frame. This icon is in fact managed by the Network Manager running in a separate NetVM. The notes icon (with the green frame around it) has been drawn by the note-taking app running in the work domain (which has the "green" label).
|
Qubes is all about seamless integration from the user’s point of view. Here you can see how it virtualizes tray icons from other domains. Notice the network icon in a red frame. This icon is in fact managed by the Network Manager running in a separate NetVM. The notes icon (with the green frame around it) has been drawn by the note-taking app running in the work domain (which has the "green" label).
|
||||||
|
|
||||||
* * * * *
|
* * * * *
|
||||||
|
|
||||||
[](/attachment/wiki/QubesScreenshots/r2b2-manager-and-netvm-network-prompt.png)
|
[](/attachment/wiki/QubesScreenshots/r4.1-manager-and-sysnet-network-prompt.png)
|
||||||
|
|
||||||
All the networking runs in a special, unprivileged NetVM. (Notice the red frame around the Network Manager dialog box on the screen above.) This means that in the event that your network card driver, Wi-Fi stack, or DHCP client is compromised, the integrity of the rest of the system will not be affected! This feature requires Intel VT-d or AMD IOMMU hardware (e.g., Core i5/i7 systems).
|
All the networking runs in a special, unprivileged NetVM. (Notice the red frame around the Network Manager dialog box on the screen above.) This means that in the event that your network card driver, Wi-Fi stack, or DHCP client is compromised, the integrity of the rest of the system will not be affected! This feature requires Intel VT-d or AMD IOMMU hardware (e.g., Core i5/i7 systems).
|
||||||
|
|
||||||
* * * * *
|
* * * * *
|
||||||
|
|
||||||
[](/attachment/wiki/QubesScreenshots/r2b2-software-update.png)
|
[](/attachment/wiki/QubesScreenshots/r4.1-software-update.png)
|
||||||
|
|
||||||
Qubes lets you update all the software in all the domains all at once, in a centralized way. This is possible thanks to Qubes' unique TemplateVM technology. Note that the user is not required to shut down any AppVMs (domains) for the update process. This can be done later, at a convenient moment, and separately for each AppVM.
|
Qubes lets you update all the software in all the domains all at once, in a centralized way. This is possible thanks to Qubes' unique TemplateVM technology. Note that the user is not required to shut down any AppVMs (domains) for the update process. This can be done later, at a convenient moment, and separately for each AppVM.
|
||||||
|
|
||||||
* * * * *
|
* * * * *
|
||||||
|
|
||||||
[](/attachment/wiki/QubesScreenshots/copy-paste-1.png) [](/attachment/wiki/QubesScreenshots/copy-paste-2.png)
|
[](/attachment/wiki/QubesScreenshots/r4.1-copy-paste.png)
|
||||||
|
|
||||||
Qubes supports secure copy-and-paste operations between AppVMs. Only the user can initiate a copy or paste operation using a special key combination (Ctrl-Shift-C/V). Other AppVMs have no access to the clipboard buffer, so they cannot steal data from the clipboard. Only the user decides which AppVM should be given access to the clipboard. (This is done by selecting the destination AppVM’s window and pressing the Ctrl-Shift-V combination.)
|
Qubes supports secure copy-and-paste operations between AppVMs. Only the user can initiate a copy or paste operation using a special key combination (Ctrl-Shift-C/V). Other AppVMs have no access to the clipboard buffer, so they cannot steal data from the clipboard. Only the user decides which AppVM should be given access to the clipboard. (This is done by selecting the destination AppVM’s window and pressing the Ctrl-Shift-V combination.)
|
||||||
|
|
||||||
* * * * *
|
* * * * *
|
||||||
|
|
||||||
[](/attachment/wiki/QubesScreenshots/r2b2-copy-to-other-appvm-1.png) [](/attachment/wiki/QubesScreenshots/r2b2-copy-to-other-appvm-3.png)
|
[](/attachment/wiki/QubesScreenshots/r4.1-copy-to-other-appvm-1.png) [](/attachment/wiki/QubesScreenshots/r4.1-copy-to-other-appvm-2.png)
|
||||||
|
|
||||||
Qubes also supports secure file copying between AppVMs.
|
Qubes also supports secure file copying between AppVMs.
|
||||||
|
|
||||||
* * * * *
|
* * * * *
|
||||||
|
|
||||||
[](/attachment/wiki/QubesScreenshots/r2b2-open-in-dispvm-1.png) [](/attachment/wiki/QubesScreenshots/r2b2-open-in-dispvm-3.png)
|
[](/attachment/wiki/QubesScreenshots/r4.1-open-in-dispvm-1.png) [](/attachment/wiki/QubesScreenshots/r4.1-open-in-dispvm-2.png)
|
||||||
|
|
||||||
Qubes' unique DisposableVMs (DispVMs) allow the user to open any file in a disposable VM in a matter of seconds! A file can be edited in a disposable VM, and any changes are projected back onto the original file. Currently, there is no way to mark files to be automatically opened in a disposable VM (one needs to right-click on the file and choose the "Open in DisposableVM" option), but this is planned for the R2 Beta 3 release.
|
Qubes' unique DisposableVMs (DispVMs) allow the user to open any file in a disposable VM in a matter of seconds! A file can be edited in a disposable VM, and any changes are projected back onto the original file. Currently, there is no way to mark files to be automatically opened in a disposable VM (one needs to right-click on the file and choose the "Open in DisposableVM" option), but this is planned for the R2 Beta 3 release.
|
||||||
|
|
||||||
* * * * *
|
* * * * *
|
||||||
|
|
||||||
[](/attachment/wiki/QubesScreenshots/r2b2-convert-to-trusted-pdf-3.png) [](/attachment/wiki/QubesScreenshots/r2b2-converting-pdf-2.png)
|
[](/attachment/wiki/QubesScreenshots/r4.1-convert-to-trusted-pdf.png) [](/attachment/wiki/QubesScreenshots/r4.1-converting-pdf.png)
|
||||||
|
|
||||||
Qubes provides an advanced infrastructure for programming inter-VM services, such as a PDF converter for untrusted files (which is described in [this article](https://blog.invisiblethings.org/2013/02/21/converting-untrusted-pdfs-into-trusted.html)).
|
Qubes provides an advanced infrastructure for programming inter-VM services, such as a PDF converter for untrusted files (which is described in [this article](https://blog.invisiblethings.org/2013/02/21/converting-untrusted-pdfs-into-trusted.html)).
|
||||||
|
|
||||||
* * * * *
|
* * * * *
|
||||||
|
|
||||||
[](/attachment/wiki/QubesScreenshots/r2b1-manager-firewall.png)
|
[](/attachment/wiki/QubesScreenshots/r4.1-manager-firewall.png)
|
||||||
|
|
||||||
Qubes provides a dedicated firewall that itself runs in an isolated FirewallVM.
|
Qubes provides a dedicated firewall that itself runs in an isolated FirewallVM.
|
||||||
|
|
||||||
@ -103,9 +103,9 @@ Qubes provides a dedicated firewall that itself runs in an isolated FirewallVM.
|
|||||||
|
|
||||||
And some more screenshots:
|
And some more screenshots:
|
||||||
|
|
||||||
[](/attachment/wiki/QubesScreenshots/r2b2-xfce4-start-menu-3.png)
|
[](/attachment/wiki/QubesScreenshots/r4.1-xfce-start-menu.png)
|
||||||
|
|
||||||
[](/attachment/wiki/QubesScreenshots/r2b2-kde-red-and-green-terminals.png)
|
[](/attachment/wiki/QubesScreenshots/r4.1-xfce-red-and-green-terminals.png)
|
||||||
|
|
||||||
[](/attachment/wiki/QubesScreenshots/r2b3-windows-seamless-2.png)
|
[](/attachment/wiki/QubesScreenshots/r2b3-windows-seamless-2.png)
|
||||||
|
|
||||||
|
|||||||
@ -30,7 +30,7 @@ Increasing the size of Disk Images
|
|||||||
There are several disk images which can be easily extended, but pay attention to the overall consumed space of your sparse/thin disk images.
|
There are several disk images which can be easily extended, but pay attention to the overall consumed space of your sparse/thin disk images.
|
||||||
In most cases, the GUI tool Qube Settings (available for every qube from the Start menu, and also in the Qube Manager) will allow you to easily increase maximum disk image size.
|
In most cases, the GUI tool Qube Settings (available for every qube from the Start menu, and also in the Qube Manager) will allow you to easily increase maximum disk image size.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
In case of standalone qubes and templates, just change the Disk Storage settings above.
|
In case of standalone qubes and templates, just change the Disk Storage settings above.
|
||||||
In case of template-based qubes, the private storage (the /home directory and user files) can be changed in the qube's own settings, but the system root image is [inherited from the template](/getting-started/), and so it must be changed in the template settings.
|
In case of template-based qubes, the private storage (the /home directory and user files) can be changed in the qube's own settings, but the system root image is [inherited from the template](/getting-started/), and so it must be changed in the template settings.
|
||||||
|
|||||||
@ -95,7 +95,7 @@ This app is running in its own dedicated VM -- a DisposableVM created for the pu
|
|||||||
Once you close the viewing application the whole DisposableVM will be destroyed.
|
Once you close the viewing application the whole DisposableVM will be destroyed.
|
||||||
If you have edited the file and saved the changes, the changed file will be saved back to the original AppVM, overwriting the original.
|
If you have edited the file and saved the changes, the changed file will be saved back to the original AppVM, overwriting the original.
|
||||||
|
|
||||||
 
|
 
|
||||||
|
|
||||||
|
|
||||||
## Opening a fresh web browser instance in a new DisposableVM ##
|
## Opening a fresh web browser instance in a new DisposableVM ##
|
||||||
@ -105,7 +105,7 @@ This can be done easily using the Start Menu: just go to **Application Menu -\>
|
|||||||
Wait a few seconds until a web browser starts.
|
Wait a few seconds until a web browser starts.
|
||||||
Once you close the viewing application the whole DisposableVM will be destroyed.
|
Once you close the viewing application the whole DisposableVM will be destroyed.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Opening a file in a DisposableVM via command line (from AppVM) ##
|
## Opening a file in a DisposableVM via command line (from AppVM) ##
|
||||||
|
|||||||
@ -45,7 +45,7 @@ For example, you could use the colors to show that qubes belong to the same doma
|
|||||||
You might use three or four qubes for work activities and give them all the same distinct color label, for instance.
|
You might use three or four qubes for work activities and give them all the same distinct color label, for instance.
|
||||||
It's entirely up to you.
|
It's entirely up to you.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
In addition to qubes and templates, there's one special domain called [dom0], where many system tools and the desktop manager run.
|
In addition to qubes and templates, there's one special domain called [dom0], where many system tools and the desktop manager run.
|
||||||
This is where you log in to the system.
|
This is where you log in to the system.
|
||||||
@ -77,7 +77,7 @@ Alternatively, you can use a suite of GUI tools, most of which are available thr
|
|||||||
- The **Disk Space Widget** will notify you if you're ever running out of disk space.
|
- The **Disk Space Widget** will notify you if you're ever running out of disk space.
|
||||||
- The **Updates Widget** will inform you when template updates are available.
|
- The **Updates Widget** will inform you when template updates are available.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
For an overview of the entire system, you can use the **Qube Manager** (go to the Application Launcher → System Tools → Qube Manager), which displays the states of all the qubes in your system.
|
For an overview of the entire system, you can use the **Qube Manager** (go to the Application Launcher → System Tools → Qube Manager), which displays the states of all the qubes in your system.
|
||||||
|
|
||||||
@ -91,9 +91,9 @@ You can start apps directly from the Application Launcher or the Application Fin
|
|||||||
Each qube has its own menu directory under the scheme `Domain: <name>`.
|
Each qube has its own menu directory under the scheme `Domain: <name>`.
|
||||||
After navigating into one of these directories, simply click on the application you'd like to start:
|
After navigating into one of these directories, simply click on the application you'd like to start:
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
By default, each qube's menu contains only a few shortcuts.
|
By default, each qube's menu contains only a few shortcuts.
|
||||||
If you'd like to add more, enter the qube's **Qube Settings** and add them on the Applications tab.
|
If you'd like to add more, enter the qube's **Qube Settings** and add them on the Applications tab.
|
||||||
|
|||||||
@ -14,7 +14,7 @@ Managing shortcuts to applications in AppVMs
|
|||||||
For ease of use Qubes aggregates shortcuts to applications that are installed in AppVMs and shows them in one "start menu" in dom0.
|
For ease of use Qubes aggregates shortcuts to applications that are installed in AppVMs and shows them in one "start menu" in dom0.
|
||||||
Clicking on such shortcut runs the assigned application in its AppVM.
|
Clicking on such shortcut runs the assigned application in its AppVM.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
To make applications newly installed via the OS's package manager show up in the menu, use the `qvm-sync-appmenus` command (Linux VMs do this automatically):
|
To make applications newly installed via the OS's package manager show up in the menu, use the `qvm-sync-appmenus` command (Linux VMs do this automatically):
|
||||||
|
|
||||||
@ -22,7 +22,7 @@ To make applications newly installed via the OS's package manager show up in the
|
|||||||
|
|
||||||
After that, select the *Add more shortcuts* entry in the VM's submenu to customize which applications are shown:
|
After that, select the *Add more shortcuts* entry in the VM's submenu to customize which applications are shown:
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
The above image shows that Windows HVMs are also supported (provided that Qubes Tools are installed).
|
The above image shows that Windows HVMs are also supported (provided that Qubes Tools are installed).
|
||||||
|
|
||||||
|
|||||||
@ -30,7 +30,7 @@ How to edit rules
|
|||||||
|
|
||||||
In order to edit rules for a given qube, select it in the Qubes Manager and press the "firewall" button:
|
In order to edit rules for a given qube, select it in the Qubes Manager and press the "firewall" button:
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
*R4.0 note:* ICMP and DNS are no longer accessible in the GUI, but can be changed via `qvm-firewall` described below.
|
*R4.0 note:* ICMP and DNS are no longer accessible in the GUI, but can be changed via `qvm-firewall` described below.
|
||||||
Connections to Updates Proxy are no longer made over network so can not be allowed or blocked with firewall rules (see [R4.0 Updates proxy](https://www.qubes-os.org/doc/software-update-vm/) for more detail.
|
Connections to Updates Proxy are no longer made over network so can not be allowed or blocked with firewall rules (see [R4.0 Updates proxy](https://www.qubes-os.org/doc/software-update-vm/) for more detail.
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user