PrivSec-dev/privsec.dev
1
0
Fork 0
mirror of https://github.com/PrivSec-dev/privsec.dev synced 2024-12-22 04:41:33 -05:00
Code

Typo Fixes

Browse Source 
Signed-off-by: Tommy <contact@tommytran.io>
This commit is contained in:
Tommy 2022-09-04 05:59:16 -04:00
parent a137e68a4e
commit c2e42859a6
No known key found for this signature in database
GPG Key ID: 060B29EB996BD9F2
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
content/apps/Using Mullvad VPN on Qubes OS.md
View File

@ -49,7 +49,7 @@ sudo shutdown now
## Creating the ProxyVM ## Creating the ProxyVM
Create an AppVM based on the TemplateVM you have just created. Set `sys-firewall` (or whatever Firewall VM you have connected to your `sys-net`) as the net qube. If you do not have such Firewall VM, use `sys-net` as the net qube. Next, go to the advanced tab and tick the `provides network access to other qubes` box. Create an AppVM based on the TemplateVM you have just created. Set `sys-firewall` (or whatever FirewallVM you have connected to your `sys-net`) as the net qube. If you do not have such FirewallVM, use `sys-net` as the net qube. Next, go to the advanced tab and tick the `provides network access to other qubes` box.
![Provides Network](/images/provides-network.png) ![Provides Network](/images/provides-network.png)
@ -66,6 +66,6 @@ You can now use this ProxyVM as the net qube for other qubes!
With this current setup, the ProxyVM you have just created will be responsible for handling Firewall rules for the qubes behind it. This is not ideal, as this is still a fairly large VM, and there is a risk that Mullvad or some other apps may interfere with its firewall handling. With this current setup, the ProxyVM you have just created will be responsible for handling Firewall rules for the qubes behind it. This is not ideal, as this is still a fairly large VM, and there is a risk that Mullvad or some other apps may interfere with its firewall handling.
Instead, I highly recommend that you [create a minimal Mirage Firewall VM](/os/firewalling-with-mirageos-on-qubes-os/) and use it as a firewall **behind** the Mullvad ProxyVM. Other AppVMs then should use the Mirage Firewall as the net qube instead. This way, you can make sure that firewall rules are properly enforced. Instead, I highly recommend that you [create a minimal Mirage FirewallVM](/os/firewalling-with-mirageos-on-qubes-os/) and use it as a firewall **behind** the Mullvad ProxyVM. Other AppVMs then should use the Mirage Firewall as the net qube instead. This way, you can make sure that firewall rules are properly enforced.
![MirageOS](/images/mirageos.png) ![MirageOS](/images/mirageos.png)

4
content/os/Firewalling with MirageOS on Qubes OS.md
View File

@ -86,9 +86,9 @@ qvm-features your_disposable_template_name no-default-kernelopts 1
Your disposable templates should now launch and shutdown properly. Your disposable templates should now launch and shutdown properly.
### Disposable Firewall VMs ### Disposable FirewallVMs
You can now create disposable firewall VMs based on your disposable template. I recommend replacing `sys-firewall` with a disposable Mirage firewall. If you use ProxyVMs like `sys-whonix`, I recommend that you add a disposable Mirage firewakk after the ProxyVM as well, and use it as the net qube for your AppVMs. You can now create disposable FirewallVMs based on your disposable template. I recommend replacing `sys-firewall` with a disposable Mirage firewall. If you use ProxyVMs like `sys-whonix`, I recommend that you add a disposable Mirage Firewall after the ProxyVM as well, and use it as the net qube for your AppVMs.
```bash ```bash
qvm-create \ qvm-create \