Autor: Charlie Hustle Data: A: tails-dev@boum.org Assumpte: [Tails-dev] Tails default encryption app - Zulucrypt an option?
Hi there,
Firstly sincere apologies if this is the wrong way to go about this.
I wasn't able to create a Gitlab account anonymously to post a request there.
I have a feature request for Tails 6.0 (or roadmap) I hope merits discussion:
It would be ideal for Tails to replace the "Unlock Veracrypt Volumes" application with another app already offered in the package manager - Zulucrypt, OR a analagous app that offers similar features.
My main reasons are:
* Functionality. The "Unlock Veracrypt Volumes" only allows you to unlock volumes first created on other systems. I believe this creates a potential security threat for users who might use an insecure, non-amensiac platform to create this volume and leave traces behind. Zulucrypt allows both the creation AND unlocking of many types of encryption volumes, not just Veracrypt - enhancing the OOTB usefulness of Tails without adding large filesize or a steep learning curve for most features.
* Stenanography (and plausible deniability). An popular encryption method of hiding in plain sight, steganography is great (though not a silver bullet) - however in the current versions of Tails, you have to manually install Zulucrypt in order to use it (that is, unless you invest the time into becoming a CLI expert, most users won't). The mere existence of Zulucrypt being installed on a user's Tails today can alert an adversary to the potential existence of a hidden container created via steganography. By having Zulucrypt installed for all users by default (like Parrot OS has) in place of the current app, everyone benefits from the potential to use steganography in addition to other encryption formats, without raising suspicion from the adversary. If they can force you to unlock your persistent storage, that doesn't necessarily have to be the end of your defenses against prying eyes - in fact the appearance of compliance might be useful.
It appears the last time I could see this discussed was in 2016-17.
Could this be reviewed afresh and considered for a future Tails update?
