There is a Parrot 6 template for Qubes 4.2.1 and is very good. i2p ONLY
i2p Snark magnet:
magnet:?xt=urn:btih:0d235202c5b85fdff6e933a3bb3154c5b9036fbe&dn=Parrot6+Template+4+Qubes+4.2.1&tr=http://tracker2.postman.i2p/announce.php
i2p address:
http://tracker2.postman.i2p/index.php?view=TorrentDetail&id=78445&start=0&limit=20
Parrot 6 template and dvm:
qubes-backup-2024-07-03T114232
4.3 GB (4342620160 bytes)
sha256sum c74bce066e06f1df97e08a9c7f560daafe1fd3d6a1354e3281a474bc1cc1958e
sha512sum
2b59fd56c9091ce276f9e2f44b6b52d9176cf50e3fe94cfef867cc74b8e250dd648fec355ce0e82ed747842b36c4602674d0540b8bad058e36f5f2c30181b0b4
Restore from backup password: a
Restored from backup Sizes:
ParrotT (black): 10827.78 MiB
Parrot-Surf-dvm (blue): 2715.65 MiB
parrot-dvm: 0
I don’t tell anybody what to do or not do. This is a Parrot 6 Qubes 4.2.1 template and dvm. It was updated 2024-07-03.
I use similar on ALL my new Qubes OS installs BEFORE I go online. I also use a USB GPS for accurate time. I was hacked hundred of times for clock offsets greater than 0.2 seconds. Key-servers, Update-Servers and Network-Bootstrap are notorious for time attacks.
Some explanations:
OpenSnitch: If you don’t want to learn how to use it, click on the icon with a cloud and 2 arrows and Pause it. It is an awsome program.
Updates: I don’t update often… because I don’t want to be attacked on updates. Your choice.
If you have a USB-GPS hardware dongle and it has position the command ./gpstimeT1.sh should set the time for the attached VM to 0.0* offset. Maximum retries per minute is 3.
AnonSurf: type into a terminal anonsurf and you get the instructions.
Icecat has some snags… and does not show in the menu but nothing major.
Min is a very good browser.
On a new install I use parrot-dvm for sys-net, sys-firewall, with almost no adjustments. For sys-usb I use Parrot-Surf-dvm because I have 2 options to display cgps and 2 options to set gpstime.
1./home/user/gpsd-gp/opt/gnu/bin/cgps
2. cgps (with a large terminal window)
3. ./gpstimeT1.sh or ./gpstimeT2.sh will set your time offset of 0.0*seconds.
After I set the time in sys-usb, in Dom0 terminal: sudo qvm-sync-clock. sys-usb is my clock VM and if I set my Qubes firewall for sys-usb to allow only udp on port 123, I SOMETIMES connected to sys-firewall. You can set a cron job to run gpstimeT1.sh
bla…bla…bla…
Most of i2p people can run circles around me and spit, and I would think it’s raining. On Qubes Forum the situation is reversed. I did NOT include i2p to leave doubt of my stupidity.
This is a “polished” not Polish or French template. It will take Qubes developers/maintainers another generation to achive this type of detail. Maybe in the next life I’ll do a Kaisen or Guix which currently have problems.