mirror of
https://0xacab.org/anarsec/anarsec.guide.git
synced 2025-07-27 16:45:40 -04:00
fix .onion img src
This commit is contained in:
parent
ec6fb8110b
commit
7e7fbd3bc1
8 changed files with 54 additions and 49 deletions
|
@ -31,13 +31,13 @@ Qubes OS is not quite another version of Linux. Rather, it is based on many "[vi
|
|||
|
||||
What is a virtual machine? [Virtualization](/glossary/#virtualization) is the process of running a virtual computer *inside* your computer. The virtual machine thinks it's a computer running on real hardware, but it's actually running on abstracted hardware (software that mimics hardware). Qubes OS uses a special program called a hypervisor to manage and run many of these virtual machines simultaneously, on the same physical computer. To simplify things, virtual machines are referred to as qubes. Different operating systems such as Debian, Whonix, Fedora, Windows, etc. can all run together at the same time in their own qubes. The hypervisor strongly isolates each of the qubes from one another.
|
||||
|
||||

|
||||

|
||||
|
||||
At the risk of overwhelming you, here is an overview of how Qubes OS is structured. You don't need to memorize any of this to actually use Qubes OS, but it may be helpful to understand the outline of the system before you get started. Each rectangle represents a qube (i.e. a virtual machine). Let's break it down.
|
||||
|
||||
## General Usage
|
||||
|
||||

|
||||

|
||||
|
||||
Ignore the greyed-out parts of the diagram for now. Daily use of Qubes OS primarily involves interaction with two components:
|
||||
|
||||
|
@ -53,7 +53,7 @@ A Disposable qube is a type of App qube that self-destructs when its originating
|
|||
|
||||
## Management Qubes
|
||||
|
||||

|
||||

|
||||
|
||||
Two more components are needed to complete the Qubes OS system:
|
||||
|
||||
|
@ -140,20 +140,20 @@ There is a special tool for moving files and directories (folders) between qubes
|
|||
From the [docs](https://www.qubes-os.org/doc/how-to-copy-and-move-files/):
|
||||
|
||||
>1. Open a file manager in the qube containing the file you wish to copy (the source qube), right-click on the file you wish to copy or move, and select **Copy to Other AppVM**... or **Move to Other AppVM**....
|
||||

|
||||

|
||||
>2. A dialog box will appear in dom0 asking for the name of the target qube (qube B). Enter or select the desired destination qube name.
|
||||

|
||||

|
||||
>3. If the target qube is not already running, it will be started automatically, and the file will be copied there. It will show up in this directory (which will automatically be created if it does not already exist): `/home/user/QubesIncoming/<source_qube>/<filename>`. If you selected Move rather than Copy, the original file in the source qube will be deleted. (Moving a file is equivalent to copying the file, then deleting the original.)
|
||||
>
|
||||
>4. If you wish, you may now move the file in the target qube to a different directory and delete the `/home/user/QubesIncoming/` directory when no longer needed.
|
||||
|
||||
# How to Shutdown Qubes
|
||||
|
||||

|
||||

|
||||
|
||||
Click on the Domains widget to see which Qubes are currently running and how much memory (RAM) and processing power (CPU) they are using. Each qube uses memory, so when you are done with a qube, you should shut it down to free up the memory it is using. Closing windows isn't enough - you need to shut down the qube when you're done with it.
|
||||
|
||||

|
||||

|
||||
|
||||
# How to Install Software
|
||||
|
||||
|
@ -186,7 +186,7 @@ To install new software, as described in the [docs](https://www.qubes-os.org/doc
|
|||
>
|
||||
>6. (Recommended) In the relevant qubes’ **Settings → Applications** tab, select the new application(s) from the list, and press **OK**. These new shortcuts will appear in the Applications Menu. (If you encounter problems, see [here](https://www.qubes-os.org/doc/app-menu-shortcut-troubleshooting/) for troubleshooting.)
|
||||
|
||||

|
||||

|
||||
|
||||
Remember that you should not run `apt update` or `dnf update`.
|
||||
|
||||
|
@ -202,7 +202,7 @@ After installation, a number of qubes will already exist by default. Click on th
|
|||
|
||||
How the App qubes will be organized, without displaying service qubes or Templates:
|
||||
|
||||

|
||||

|
||||
|
||||
* **A vault qube**. This is used for all data storage because you don't need internet to store files. This qube can be reassigned to the `debian-12-documents` Template so that trusted files can be opened there.
|
||||
|
||||
|
@ -261,7 +261,7 @@ Once you close all the windows of a disposable, the whole disposable is shut dow
|
|||
|
||||
In contrast, an App qube must be shut down manually (using the Qubes Domains widget), and will persist data in the `/home`, `/usr/local`, and `/rw/config` directory. The next time an App qube boots, all locations in its file system other than these three directories will reflect the state of its Template. See how [inheritance and persistence](https://www.qubes-os.org/doc/templates/#inheritance-and-persistence) works for Templates, App qubes, and disposables for more information.
|
||||
|
||||

|
||||

|
||||
|
||||
In the file manager of an App qube, right-clicking on certain fle types gives you the **Edit In DisposableVM** and **View In DisposableVM** options. This is how we want to open any untrusted files. It will use the default disposable that we set earlier, which is offline. As soon as you close the viewing application, the disposable is reverted to its prior state. If you have edited the file and saved the changes, the changed file will be saved back to the original app qube, overwriting the original. In contrast, viewing in a disposable is read-only, so if the file does something malicious, it can't write to the App qube you launched it from - this is preferable for files you don't need to edit.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue