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

Add prompts to all code blocks with bash session

Browse source
This commit is contained in:
qubedmaiska 2025-08-15 16:49:01 -04:00
parent b0395e618c
commit 2d2bcb06a6
No known key found for this signature in database
GPG key ID: 204BCE0FD52C0501
72 changed files with 513 additions and 497 deletions
Download patch file Download diff file Expand all files Collapse all files

2
user/security-in-qubes/anti-evil-maid.rst
View file

@ -25,7 +25,7 @@ In Dom0 install ``anti-evil-maid``:
.. code:: console
sudo qubes-dom0-update anti-evil-maid
$ sudo qubes-dom0-update anti-evil-maid

4
user/security-in-qubes/ctap-proxy.rst
View file

@ -106,8 +106,8 @@ If your USB qube is named differently than ``sys-usb``, then do the following in
.. code:: console
systemctl enable qubes-ctapproxy@USB_QUBE.service
systemctl disable qubes-ctapproxy@sys-usb.service
$ systemctl enable qubes-ctapproxy@USB_QUBE.service
$ systemctl disable qubes-ctapproxy@sys-usb.service

8
user/security-in-qubes/firewall.rst
View file

@ -63,7 +63,7 @@ Normally Qubes doesn’t let the user stop a NetVM if there are other qubes runn
.. code:: console
qvm-prefs <vm> netvm <netvm>
$ qvm-prefs <vm> netvm <netvm>
@ -71,7 +71,7 @@ Normally qubes do not connect directly to the actual NetVM (sys-net by default)
.. code:: console
qvm-prefs sys-firewall netvm sys-net
$ qvm-prefs sys-firewall netvm sys-net
@ -123,7 +123,7 @@ In order to allow networking from qube A (client) to qube B (server) follow thes
.. code:: console
sudo nft add rule ip qubes custom-forward ip saddr <IP address of A> ip daddr <IP address of B> ct state new,established,related counter accept
$ sudo nft add rule ip qubes custom-forward ip saddr <IP address of A> ip daddr <IP address of B> ct state new,established,related counter accept
@ -133,7 +133,7 @@ In order to allow networking from qube A (client) to qube B (server) follow thes
.. code:: console
sudo nft add rule qubes custom-input ip saddr <IP address of A> ct state new,established,related counter accept
$ sudo nft add rule qubes custom-input ip saddr <IP address of A> ct state new,established,related counter accept

12
user/security-in-qubes/firewall_4.1.rst
View file

@ -111,7 +111,7 @@ In order to allow networking between qubes A and B follow these steps:
.. code:: console
sudo iptables -I FORWARD 2 -s <IP address of A> -d <IP address of B> -j ACCEPT
$ sudo iptables -I FORWARD 2 -s <IP address of A> -d <IP address of B> -j ACCEPT
@ -121,7 +121,7 @@ In order to allow networking between qubes A and B follow these steps:
.. code:: console
sudo iptables -I INPUT -s <IP address of A> -j ACCEPT
$ sudo iptables -I INPUT -s <IP address of A> -j ACCEPT
@ -380,7 +380,7 @@ Once you have confirmed that the counters increase, store these command in ``/rw
.. code:: console
sudo nano /rw/config/rc.local
$ sudo nano /rw/config/rc.local
@ -485,7 +485,7 @@ Once you have confirmed that the counters increase, store these command in ``/rw
.. code:: console
sudo nano /rw/config/qubes-firewall-user-script
$ sudo nano /rw/config/qubes-firewall-user-script
@ -550,7 +550,7 @@ Finally make this file executable (so it runs at every Firewall VM update)
.. code:: console
sudo chmod +x /rw/config/qubes-firewall-user-script
$ sudo chmod +x /rw/config/qubes-firewall-user-script
@ -562,7 +562,7 @@ Here no routing is required, only filtering. Proceed in the same way as above bu
.. code:: console
sudo nano /rw/config/rc.local
$ sudo nano /rw/config/rc.local

20
user/security-in-qubes/mfa.rst
View file

@ -27,7 +27,7 @@ As the name implies, this generates authentication code that is time-dependent.
.. code:: console
sudo qubes-dom0-update google-authenticator
$ sudo qubes-dom0-update google-authenticator
@ -86,7 +86,7 @@ Now we are going to add the authenticator as a login requirement:
.. code:: console
sudo authselect select custom/mfa
$ sudo authselect select custom/mfa
@ -110,7 +110,7 @@ The following assumes you haven’t restarted your computer since setting up TOT
.. code:: console
sudo authselect select sssd
$ sudo authselect select sssd
@ -170,7 +170,7 @@ All these requirements are described below, step by step, for the YubiKey and Ni
.. code:: console
sudo dnf install ykpers
$ sudo dnf install ykpers
@ -180,7 +180,7 @@ All these requirements are described below, step by step, for the YubiKey and Ni
.. code:: console
sudo apt-get install yubikey-personalization
$ sudo apt-get install yubikey-personalization
@ -204,7 +204,7 @@ All these requirements are described below, step by step, for the YubiKey and Ni
.. code:: console
sudo qubes-dom0-update qubes-yubikey-dom0
$ sudo qubes-dom0-update qubes-yubikey-dom0
@ -291,7 +291,7 @@ All these requirements are described below, step by step, for the YubiKey and Ni
.. code:: console
echo -n "$password" | openssl dgst -sha1 | cut -f2 -d ' '
$ echo -n "$password" | openssl dgst -sha1 | cut -f2 -d ' '
@ -363,7 +363,7 @@ In dom0:
.. code:: console
sudo chmod +x /etc/qubes-rpc/custom.LockScreen
$ sudo chmod +x /etc/qubes-rpc/custom.LockScreen
@ -400,7 +400,7 @@ In your USB VM:
.. code:: console
sudo chmod +x /rw/config/rc.local
$ sudo chmod +x /rw/config/rc.local
@ -408,7 +408,7 @@ In your USB VM:
.. code:: console
sudo /rw/config/rc.local
$ sudo /rw/config/rc.local