ZuluCrypt issues after updating the Whonix-Workstation-17 template

As you know, sysmaint has now been added to the new templates whonix-workstation-17, which limits a lot of things. Now, for example, zuluCrypt does not open from the user. I will be very grateful if someone writes detailed instructions on how to use zuluCrypt from the user now. For example, what do I need, what privleap custom actions do I need to do.

This isn’t what you asked for (and I don’t know the answer anyway), but why not utilize another qube (say, based on Debian, Arch, or Fedora) to unlock your volume? After all, we’ve got Qubes for a reason. And if it’s sensitive data, use an offline VM, like Vault.

1 Like

I got your point, but I’m already using an offline qube, it’s just based on the Workstation 17 template.

1 Like

Duplicate: