diff --git a/introduction/getting-started.md b/introduction/getting-started.md index 1ac922d5..4a02083c 100644 --- a/introduction/getting-started.md +++ b/introduction/getting-started.md @@ -18,14 +18,13 @@ Dive right in to [organizing your qubes](/doc/how-to-organize-your-qubes/).) ## The Basics -Qubes OS is an operating system built out of securely-isolated compartments -called [qubes](/doc/glossary/#qube). For example, you might have a work qube, a -personal qube, a banking qube, a web browsing qube, and so on. You can have as -many qubes as you want! Most of the time, you'll be using an [app -qube](/doc/glossary/#app-qube), which is a qube intended for running software +Qubes OS is an operating system built out of securely-isolated compartments, or [qubes](/doc/glossary/#qube). +You can have a work qube, a personal qube, a banking qube, a web browsing qube, a standalone Windows qube and so on. +You can have as many qubes as you want! Most of the time, you'll be using an [app +qube](/doc/glossary/#app-qube), a qube for running software programs like web browsers, email clients, and word processors. Each app qube is based on another type of qube called a [template](/doc/glossary/#template). -More than one qube can be based on the same template. Importantly, a qube +The same template can be a base for various qubes. Importantly, a qube cannot modify its template in any way. This means that, if a qube is ever compromised, its template and any other qubes based on that template will remain safe. This is what makes Qubes OS so secure. Even if an attack is @@ -35,9 +34,8 @@ Suppose you want to use your favorite web browser in several different qubes. You'd install the web browser in a template, then every qube based on that template would be able to run the web browser software (while still being forbidden from modifying the template and any other qubes). This way, you only -have to install the web browser a single time, and updating the template serves -to update all the qubes based on it. This elegant design saves time and space -while enhancing security. +have to install the web browser a single time, and updating the template updates all the qubes based on it. +This elegant design saves time and space while enhancing security. There are also some "helper" qubes in your system. Each qube that connects to the Internet does so through a network-providing [service @@ -54,27 +52,24 @@ corresponding version number. There are many ready-to-use many as you like. Last but not least, there's a very special [admin -qube](/doc/glossary/#admin-qube) which, as the name suggests, is used to -administer your entire system. There's only one admin qube, and it's called -[dom0](/doc/glossary/#dom0). You can think of it as the master qube, holding -ultimate power over everything that happens in Qubes OS. Dom0 is more trusted -than any other qube. If dom0 were ever compromised, it would be "game over." -The entire system would effectively be compromised. That's why everything in -Qubes OS is specifically designed to protect dom0 and ensure that doesn't +qube](/doc/glossary/#admin-qube) used to administer your entire system. +There's only one admin qube, and it's called [dom0](/doc/glossary/#dom0). +You can think of it as the master qube, holding ultimate power over everything that happens in Qubes OS. +Dom0 is the most trusted one of all qubes. If dom0 were ever to be compromised, it would be "game over"- an effective compromise of the entire system. +That's why everything in Qubes OS is specifically designed to protect dom0 and ensure that doesn't happen. Due to its overarching importance, dom0 has no network connectivity and is used only for running the [desktop environment](https://en.wikipedia.org/wiki/Desktop_environment) and [window manager](https://en.wikipedia.org/wiki/Window_manager). Dom0 should never be used for anything else. In particular, you should never run user applications -in dom0. (That's what your app qubes are for!) +in dom0. (That's what your app qubes are for!) In short, be very careful when interacting with dom0. ### Color & Security You'll choose a **color** for each of your qubes out of a predefined set of -colors. Each window on your desktop will have its frame colored according to -the color of that qube. These colored frames help you keep track of which qube -each window belongs to and how trustworthy it is. This is especially helpful -when you have the same app running in multiple qubes at the same time. For +colors. The color of the frame of each window on your desktop will correspond to the color of that cube. +These colored frames help you keep track of which qube you're currently using and how trustworthy it is. This is especially helpful +when you have the same program running in multiple qubes at the same time. For example, if you're logged in to your bank account in one qube while doing some random web surfing in a different qube, you wouldn't want to accidentally enter your banking password in the latter! The colored frames help to avoid such @@ -83,16 +78,16 @@ mistakes. [![snapshot_40.png](/attachment/doc/r4.0-snapshot_40.png)](/attachment/doc/r4.0-snapshot_40.png) Most Qubes users associate red with what's untrusted and dangerous (like a red -light: stop! danger!), green with what's safe and trusted, and yellow and -orange with things in the middle. This color scheme also extends to include -blue and black, which are usually interpreted as indicating progressively more -trusted domains than green, with black being ultimately trusted. Color and -associated meanings are ultimately up to you, however. The system itself does -not treat the colors differently. If you create two identical qubes --- black +stop light signalling danger), green with what's safe and trusted, and yellow and +orange with things in-between. This color scheme also includes +blue and black, commonly interpreted as indicating progressively more +trusted domains than green, with black being ultimately trusted. However, color and +associated meanings are entirely up to you. The system itself does +not treat the colors differently - they're all equally safe on their own. If you create two identical qubes --- black and red, say --- they'll be the same until you start using them differently. -Feel free to use the colors in whatever way is most useful to you. For example, +Feel free to use the colors in the way that best meets your needs. For example, you might decide to use three or four qubes for work activities and give them -all the same color --- or all different colors. It's entirely up to you. +all the same color --- or all different colors depending on the nature of the task they are used for. ### User Interface @@ -104,27 +99,24 @@ the window managers [i3](/doc/i3/) and [AwesomeWM](/doc/awesomewm/). [![r4.0-taskbar.png](/attachment/doc/r4.0-taskbar.png)](/attachment/doc/r4.0-taskbar.png) -The bar at the top of your screen in Qubes 4.0 includes the following XFCE +The bar at the top of your screen in Qubes 4.2 includes the following XFCE component areas: -- The **Tray**, where many functional widgets live. +- The **App Menu**, where you go to open an application within a qube, to open + a dom0 terminal, to access administrative UI tools such as the Qube Manager, + or to access settings panels for your desktop environment. +- The **Task Bar** where buttons for open and hidden windows live. - **Spaces**, an interface for [virtual desktops](https://en.wikipedia.org/wiki/Virtual_desktop). Virtual desktops do not have any inherent security isolation properties, but some users find them useful for organizing things. -- The **Task Bar** where buttons for open and hidden windows live. -- The **App Menu**, where you go to open an application within a qube, to open - a dom0 terminal, to access administrative UI tools such as the Qube Manager, - or to access settings panels for your desktop environment. - -To learn more about how to customize your desktop environment, we recommend you -spend some time going through [XFCE's documentation](https://docs.xfce.org/). +- The **Tray**, where many functional widgets live. There are several tray widgets that are unique to Qubes OS: - The **Whonix SDWDate** allows you to control the Tor connection in your [`sys-whonix`](https://www.whonix.org/wiki/Qubes) qube. -- The **Qubes Clipboard** lets you easily copy text from dom0. +- The **Qubes Clipboard** lets you easily [copy text](https://wwwpreview.qubes-os.org/doc/how-to-copy-and-paste-text/) between various qubes and from dom0. - The **Qubes Devices** widget allows you to attach and detach devices --- such as USB drives and cameras --- to qubes. - The **Qubes Disk Space** widget shows you how much storage you're using. @@ -136,50 +128,57 @@ There are several tray widgets that are unique to Qubes OS: [![r4.1-widgets.png](/attachment/doc/r4.1-widgets.png)](/attachment/doc/r4.1-widgets.png) +To learn more about how to customize your desktop environment, we recommend you +go through [XFCE's documentation](https://docs.xfce.org/). + #### Qube Manager -To see all of your qubes at the same time, you can use the **Qube Manager** (go -to the App Menu → Qubes Tools → Qube Manager), which displays the states of -all the qubes in your system, even the ones that aren't running. +To see all of your qubes at the same time, you can use the **Qube Manager**. +It displays the states of all the qubes in your system, even the ones that aren’t running. + +To access Qube Manager go to: +Qubes Icon (App Menu) → Settings Icon → Qubes Tools → **Qube Manager** [![r4.0-qubes-manager.png](/attachment/doc/r4.0-qubes-manager.png)](/attachment/doc/r4.0-qubes-manager.png) #### Command-line interface -All aspects of Qubes OS can be controlled using command-line tools. Opening a -terminal emulator in dom0 can be done in several ways: +All aspects of Qubes OS can be controlled using command-line tools such as the terminal emulator. +The default terminal emulator in Qubes is Xfce Terminal. +Opening a terminal emulator in dom0 can be done in several ways: -- Go to the App Menu and select **Terminal Emulator** at the top. +- Go to the App Menu, click on the Settings icon, choose Other from the drop-down menu, and select **Xfce Terminal Emulator** at the bottom. - Press `Alt`+`F3` and search for `xfce terminal`. - Right-click on the desktop and select **Open Terminal Here**. -Terminal emulators can also be run in other qubes as normal programs. Various -command-line tools are described as part of this guide, and the whole reference -can be found [here](/doc/tools/). +Various command-line tools are described as part of this guide, and the whole reference can be found [here](/doc/tools/). +Terminal emulators can also be run in other qubes as normal programs. ## First boot When you install Qubes OS, a number of qubes are pre-configured for you: -- **Templates:** `fedora-XX` (`XX` being the version number) +- **App qubes** such as `work`, `personal`, `untrusted`, and `vault` are your "starter pack" qubes to compartmentalize tasks + and types of data to suit most basic needs. (There is nothing special about these pre-configured qubes - they are identical in nature to more specific ones you might wish to create later.) +- **Templates:** `fedora-XX`, `debian-XX` (`XX` being the version number) +- **Service qubes:** `sys-usb`, `sys-net`, `sys-firewall`, and `sys-whonix`) - **Admin qube:** `dom0` -- **Service qubes:** `sys-usb`, `sys-net`, `sys-firewall`, and `sys-whonix` -- **App qubes** configured to prioritize security by compartmentalizing tasks - and types of data: `work`, `personal`, `untrusted`, and `vault`. (There is - nothing special about these qubes. If you were to create a black qube and - name it `vault`, it would be the same as the pre-configured `vault` qube. - They're just suggestions to get you started. ) -A variety of open-source applications such as file managers, command-line -terminals, printer managers, text editors, and "applets" used to configure -different things like audio or parts of the user interface are also installed -by default—most within the templates. Most are bundled with each template. +Other software installed in Qubes OS by default includes open-source applications such as file managers, +command-line terminals, printer managers, text editors, and applets for configuring audio and user interface settings. +Most of these applications are incorporated within each template. ### Adding, removing, and listing qubes -You can easily create a new qube with the **Create Qubes VM** option in the App -Menu. If you need to add or remove qubes, simply use the Qube Manager's **Add** -and **Remove** buttons. You can also add, remove, and list qubes from the +To create a new qube or remove one, use **Create Qubes VM** option in the App Menu. + +Creating a New Qube: +Qubes Icon → Settings → Qubes Tools → Qube Manager → Create Qubes VM → **New Qube** + +Removing a qube: +To remove a qube, use the **Delete qube button** as the final step instead. + +You can also add, remove, and list qubes from the command line using the following tools: - `qvm-create` @@ -188,14 +187,8 @@ command line using the following tools: ### How many qubes do I need? -That's a great question, but there's no one-size-fits-all answer. It depends on -the structure of your digital life, and this is at least a little different for -everyone. If you plan on using your system for work, then it also depends on -what kind of job you do. - -It's a good idea to start out with the qubes created automatically by the -installer: `work`, `personal`, `untrusted`, and `vault`. If and when you start -to feel that some activity just doesn't fit into any of your existing qubes, or +It's a good idea to start out with the pre-installed app qubes: `work`, `personal`, `untrusted`, and `vault`. +If you start to feel that some activity just doesn't fit into any of your existing qubes, or you want to partition some part of your life, you can easily create a new qube for it. You'll also be able to easily [copy any files](/doc/how-to-copy-and-move-files) you need to the newly-created qube. @@ -252,5 +245,5 @@ GitHub](https://github.com/QubesOS). ## Documentation -Peruse our extensive library of [documentation](/doc/) for users and developers +Browse our extensive library of [documentation](/doc/) for users and developers of Qubes OS. You can even [help us improve it](/doc/how-to-edit-the-documentation/)!