PrivSec-dev/privsec.dev
1
0
Fork 0
mirror of https://github.com/PrivSec-dev/privsec.dev synced 2024-11-16 19:41:35 -05:00
Code

Add redirects

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

53
content/posts/qubes/Using IVPN on Qubes OS.md
View File

@ -1,53 +0,0 @@
---
title: "Using IVPN on Qubes OS"
date: 2022-09-30
tags: ['Applications', 'Linux', 'Container', 'Security']
author: Tommy
---
![IVPN](/images/ivpn-1.png)
IVPN is a fairly popular and generally trustworthy VPN provider and is one of my favorites. In this post, I will walk you through how to use the official IVPN client in a ProxyVM on Qubes OS.
## Preparing your TemplateVM
I recommend that you make a new TemplateVM based on latest Fedora template and remove all unnecessary packages that you might not use. This way, you can minimize the attack surface while not having to deal with missing dependencies like on a minimal template. With that being said, if you do manage to get the minimal template to fully work with IVPN, feel free to [open a discussion on GitHub](https://github.com/orgs/PrivSec-dev/discussions) or [contact me directly](https://tommytran.io/contact) and I will update the post accordingly.
This is what I run on my template to trim it down:
```bash
sudo dnf remove firefox thunderbird totem gnome-remote-desktop gnome-calendar gnome-disk-utility gnome-calculator gnome-connections gnome-weather gnome-contacts gnome-clocks gnome-maps gnome-screenshot gnome-logs gnome-characters gnome-font-viewer gnome-color-manager simple-scan keepassxc cheese baobab yelp evince* httpd mozilla* cups rygel -y
sudo dnf autoremove -y
```
Next, you need to create the bind directories for IVPN's configurations:
```bash
sudo mkdir -p /etc/qubes-bind-dirs.d
sudo tee /etc/qubes-bind-dirs.d/50_user.conf << EOF > /dev/null
binds+=( '/etc/ivpn' )
EOF
```
## Installing the IVPN App
Inside of the TemplateVM you have just created, do the following:
```bash
sudo dnf config-manager --add-repo https://repo.ivpn.net/stable/fedora/generic/ivpn.repo
sudo dnf install ivpn-ui
sudo shutdown now
```
## Creating the ProxyVM
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)
## Notes
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 IVPN or some other apps may interfere with its firewall handling.
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 IVPN 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)

2
static/_redirects
View File

@ -1,8 +1,10 @@
/os/android-tips/ /posts/android/android-tips/ 301
/os/android-vpn-leakage* /posts/android/android-vpn-leakage-with-secondary-user-profiles/ 301
/apps/banking* /posts/android/banking-applications-compatibility-with-grapheneos/ 301
/banking* /posts/android/banking-applications-compatibility-with-grapheneos/ 301
/os/choosing-your-android* /posts/android/choosing-your-android-based-operating-system/ 301
/apps/f-droid* /posts/android/f-droid-security-issues/ 301
/f-droid* /posts/android/f-droid-security-issues/ 301
/knowledge/badness-enumeration/ /posts/knowledge/badness-enumeration/ 301
/knowledge/commercial-vpn-use-cases/ /posts/proxies/commercial-vpn-use-cases/ 301