Fork 0
My Scripts for template VMs
Go to file
Tommy ea308830c1
Fix 990-security-misc path
Signed-off-by: Tommy <contact@tommytran.io>
2023-11-15 14:21:33 -07:00
fedora Fix 990-security-misc path 2023-11-15 14:21:33 -07:00
fedora-minimal Fix 990-security-misc path 2023-11-15 14:21:33 -07:00
kicksecure Add Apache license header 2023-09-27 00:58:33 -07:00
whonix Add Apache license header 2023-09-27 00:58:33 -07:00
.gitignore Create .gitignore 2023-01-16 00:39:37 -05:00
LICENSE Initial commit 2022-02-03 02:57:15 -05:00
README.md Fix 2022-05-28 07:24:27 -04:00
dom0.sh Add Apache license header 2023-09-27 00:58:33 -07:00



My scripts for setting up QubesOS.

Running these scripts should be very straight forward. For the default Fedora template, run fedora.sh to trim it down first. For the Debian template, run kicksecure.sh to trim them down and convert them to KickSecure.

After you are done running those scripts, any other script can be used in a different template based on those trimmed down templates to create their respective virtual machines.

I have a script to create a Brave VM based on the normal Fedora template. The idea behind this is that you would want to use a disposable Brave VM for web browsing most of the time, and have it seperated from your AppVM. If you try to visit a link inside of an AppVM without a browser, qubes will launch a browser inside of a disposable VM for you. Of course, for VMs where you want the browser to stay persistent, you can just base it on the Brave template instead.

If you want to install Flatpak packages, install them inside of an AppVM as a user Flatpak and enable the update-user-flatpaks.service as a user systemd service for automatic updates.

It is recommended that you follow the docs here to make a prompt for root access on non-minimal VMs. dom0.sh already takes care dom dom0 so you only need to worry about the guests.