Git-Mirrors/tommytran732-QubesOS-Scripts
1
0
Fork 0
mirror of https://github.com/tommytran732/QubesOS-Scripts.git synced 2024-10-01 00:55:37 -04:00
Code Issues Packages Projects Releases Wiki Activity
Scripts for setting up QubesOS
187 Commits 1 Branch 0 Tags 9.5 MiB
Shell 100%
43643ff3c9
Go to file
Tommy 43643ff3c9
Update element.sh
2022-05-27 00:03:09 -04:00
fedora Fixes 2022-05-26 22:31:56 -04:00
fedora-brave Fixes 2022-05-26 22:31:56 -04:00
kicksecure Update element.sh 2022-05-27 00:03:09 -04:00
kicksecure-minimal Typos 2022-05-26 18:09:59 -04:00
dom0.sh Fixes 2022-05-26 22:31:56 -04:00
LICENSE Initial commit 2022-02-03 02:57:15 -05:00
README.md Fixes 2022-05-26 19:43:44 -04:00
whonix-hardening.sh kickseucre 2022-05-26 13:50:11 -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 Debian templates, run kicksecure.sh to trim them down and convert them to KickSecure. Note that there are 2 different kicksecure.sh, one for the minimal template, and one for the normal one.

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 KickSecure and Fedora templates. 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.