mirror of https://github.com/tommytran732/QubesOS-Scripts synced 2024-11-04 18:11:34 -05:00

My Scripts for template VMs

Go to file

Tommy ee379fab2c Create .gitignore		2023-01-16 00:39:37 -05:00
fedora	Create ente.sh	2022-12-06 17:13:42 -05:00
fedora-minimal	Remove NetworkManager systemd-sandbox-exec	2022-12-06 04:49:38 -05:00
kicksecure	Delete vlc.sh	2022-11-15 18:25:09 -05:00
mirageos	Update MirageOS build	2022-11-15 18:03:49 -05:00
whonix	Update whonix-ws.sh	2022-07-11 03:43:42 -04:00
.gitignore	Create .gitignore	2023-01-16 00:39:37 -05:00
dom0.sh	Enabling discard and fstrim	2022-10-31 20:32:22 -04:00
kali.sh	Minor fixes	2022-08-14 18:57:12 -04:00
LICENSE	Initial commit	2022-02-03 02:57:15 -05:00
README.md	Fix	2022-05-28 07:24:27 -04:00

README.md

QubesOS-Scripts

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.