Kicksecure for Qubes

Kicksecure for Qubes OS.
Distribution Morphing[edit]
In dom0.
1. Install debian-12
as per Qubes Debian Template documentation which is unspecific to Kicksecure.
2. Clone Template debian-12
into template kicksecure-17
.
3. Start the kicksecure-17
Template.
Inside the kicksecure-17
Template.
1. Follow the instructions Install Kicksecure inside Debian, choose meta package kicksecure-qubes-cli
or kicksecure-qubes-gui
.
2. Shutdown the Template.
3. Done.
Distribution morphing of Debian into Kicksecure is complete.
4. Change Template.
Optional: The user may change the Template for any App Qube from Debian to Kicksecure as per the usual Qubes way.
5. Create new app Qubes.
Optional: The user may create new App Qubes based on the kicksecure-17
Template as per the usual Qubes way.
Template[edit]
There is no ready-made template yet.
Future: This wiki page will be updated once available.
It shouldn't be hard to fork qubes-template-whonix into
kicksecure-qubes-template
. Please contribute to Kicksecure and Qubes OS by creating and maintaining a kicksecure-17
Qubes Template.
Service VMs[edit]
At time of writing, Kicksecure is untested in Qubes service VMs such as sys-net
, sys-firewall
, sys-usb
.
Unfinished: This wiki is a work in progress. Please do not report broken links until this notice is removed, use Search Engines First and contribute improving this wiki.

We believe security software like Kicksecure needs to remain open source and independent. Would you help sustain and grow the project? Learn more about our 10 year success story and maybe DONATE!