Changing Template for System Qubes to Kicksecure?

I want to change System Qubes to Kicksecure. Should I clone the whonix-ws TemplateVM and change the name to Kicksecure, or is whonix-gw better?

1 Like

You need to morph a Debian 11 template to Kicksecure:

Also, be aware of this:

At time of writing, Kicksecure ™ is untested in Qubes service VMs such as sys-net, sys-firewall, sys-usb.

2 Likes

I’ve used Kicksecure in the past including for sys- qubes. It worked, but the memory / CPU requirements definitely increased. Personally I decided that it doesn’t add anything substantial in the Qubes OS context and wasn’t worth the performance hit. Your requirements / views might differ.

3 Likes

I’m glad to hear an experienced person’s opinion.
I shouldn’t use Whonix.

1 Like

Edited. I missed context. Please ignore.

1 Like

The statement in chapter Service VMs has been refined:

Kicksecure in Qubes service VMs such as sys-net, sys-firewall, sys-usb are functional. This is classified as unsupported to avoid complex support requests for issues not caused by Kicksecure being directed at Kicksecure support. [1]

1 Like