zulucrypt (LUKS container GUI / CLI)

Development
21

Just to curious why exactly do you want to remove zulucrypt from whonix ? Just because that vulnerability didnt get patched yet ?

Also pls confirm if you intend on removing zulucrypt from kicksecure aswell (i hope not) because that would mean i’d need to rewrite almost a third of my blogposts on clientside deniability, due to how dependent they are on kicksecure having zulucrypt installed on it by default.

Here are the relevant tutorials that depend on both kicksecure, whonix and zulucrypt combined if you’re curious:
http://blog.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/opsec/livemode/
http://blog.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/opsec/veracrypt/
http://blog.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/opsec/sensitivevm/
http://blog.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/opsec/plausiblydeniabledataprotection/

For whonix specifically what do you recommend for people that want to use zulucrypt ? Just using it from the sysmaint session without removing the user / sysmaint split ? Or somehow git cloning it, compiling it and using it like that ?

22

Can still be manually installed.

For reasons refer to my previous posts. No other reasons on top of that.

23

I don’t have any additional recommendations on top of what’s documented in the wiki.

Same.
No differences.
Will also be removed.

24

ok i’ll have to adjust my tutorials accordingly in that case. Will zulucrypt still be available to be installed via the repositories ? or do we need to git clone it and manually compile it ?

25

Yes. From packages.debian.org as usual as per:

Because:

Also:

No Intentional User Freedom Restrictions

Possible but not required.