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

small formatting fixes in markdown

Browse source
This commit is contained in:
qubedmaiska 2025-01-22 13:29:16 -05:00
parent e7385e96b5
commit 2d3bfcb39f
No known key found for this signature in database
GPG key ID: 204BCE0FD52C0501
5 changed files with 5 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

2
developer/services/dom0-secure-updates.md
View file

@ -33,7 +33,7 @@ Keeping Dom0 not connected to any network makes it hard, however, to provide upd
The update process is initiated by [qubes-dom0-update script](https://github.com/QubesOS/qubes-core-admin-linux/blob/release2/dom0-updates/qubes-dom0-update), running in Dom0. The update process is initiated by [qubes-dom0-update script](https://github.com/QubesOS/qubes-core-admin-linux/blob/release2/dom0-updates/qubes-dom0-update), running in Dom0.
Updates (`*.rpm` files) are checked and downloaded by UpdateVM, which by default is the same as the firewall VM, but can be configured to be any other, network-connected VM. This is done by [qubes-download-dom0-updates.sh script](https://github.com/QubesOS/qubes-core-agent-linux/blob/release2/misc/qubes-download-dom0-updates.sh) (this script is executed using qrexec by the previously mentioned qubes-dom0-update). Note that we assume that this script might get compromised and fetch maliciously compromised downloads -- this is not a problem as Dom0 verifies digital signatures on updates later. The downloaded rpm files are placed in a ~~~/var/lib/qubes/dom0-updates~~~ directory on UpdateVM filesystem (again, they might get compromised while being kept there, still this isn't a problem). This directory is passed to yum using the ~~~--installroot=~~~ option. Updates (`*.rpm` files) are checked and downloaded by UpdateVM, which by default is the same as the firewall VM, but can be configured to be any other, network-connected VM. This is done by [qubes-download-dom0-updates.sh script](https://github.com/QubesOS/qubes-core-agent-linux/blob/release2/misc/qubes-download-dom0-updates.sh) (this script is executed using qrexec by the previously mentioned qubes-dom0-update). Note that we assume that this script might get compromised and fetch maliciously compromised downloads -- this is not a problem as Dom0 verifies digital signatures on updates later. The downloaded rpm files are placed in a `/var/lib/qubes/dom0-updates` directory on UpdateVM filesystem (again, they might get compromised while being kept there, still this isn't a problem). This directory is passed to yum using the `--installroot=` option.
Once updates are downloaded, the update script that runs in UpdateVM requests an RPM service [qubes.ReceiveUpdates](https://github.com/QubesOS/qubes-core-admin-linux/blob/release2/dom0-updates/qubes.ReceiveUpdates) to be executed in Dom0. This service is implemented by [qubes-receive-updates script](https://github.com/QubesOS/qubes-core-admin-linux/blob/release2/dom0-updates/qubes-receive-updates) running in Dom0. The Dom0's qubes-dom0-update script (which originally initiated the whole update process) waits until qubes-receive-updates finished. Once updates are downloaded, the update script that runs in UpdateVM requests an RPM service [qubes.ReceiveUpdates](https://github.com/QubesOS/qubes-core-admin-linux/blob/release2/dom0-updates/qubes.ReceiveUpdates) to be executed in Dom0. This service is implemented by [qubes-receive-updates script](https://github.com/QubesOS/qubes-core-admin-linux/blob/release2/dom0-updates/qubes-receive-updates) running in Dom0. The Dom0's qubes-dom0-update script (which originally initiated the whole update process) waits until qubes-receive-updates finished.

2
user/security-in-qubes/firewall.md
View file

@ -14,7 +14,7 @@ title: Firewall
Introduction Introduction
---------------------------------- ----------------------------------
This page explains use of the firewall in Qubes 4.2, using `nftables`. This page explains use of the firewall in Qubes 4.2, using `nftables`.
In Qubes 4.1, all firewall components used `iptables`. For details of that usage see [here](../firewall_4.1/) In Qubes 4.1, all firewall components used `iptables`. For details of that usage see [here](../firewall_4.1/).
Understanding firewalling in Qubes Understanding firewalling in Qubes

6
user/templates/fedora/fedora-upgrade.md
View file

@ -121,11 +121,7 @@ The same general procedure may be used to upgrade any template based on the stan
If this attempt is successful, proceed to step 4. If this attempt is successful, proceed to step 4.
* `dnf` may complain: * `dnf` may complain: `At least X MB more space needed on the / filesystem.`
`
At least X MB more space needed on the / filesystem.
`
In this case, one option is to [resize the template's disk image](/doc/resize-disk-image/) before reattempting the upgrade process. In this case, one option is to [resize the template's disk image](/doc/resize-disk-image/) before reattempting the upgrade process.
(See [Additional Information](#additional-information) below for other options.) (See [Additional Information](#additional-information) below for other options.)

4
user/troubleshooting/gui-troubleshooting.md
View file

@ -26,9 +26,7 @@ Similarly, while working, the XScreenSaver dialog may pop up (indicating the scr
If you are experiencing the any of the above symptoms, try disabling the window compositor: If you are experiencing the any of the above symptoms, try disabling the window compositor:
` `Q → System Tools → Window Manager Tweaks → Compositor → uncheck “Enable display compositing”`
Q → System Tools → Window Manager Tweaks → Compositor → uncheck “Enable display compositing”
`
## Post installation, screen goes black and freezes following LUKS decryption ## Post installation, screen goes black and freezes following LUKS decryption