GUI for CRYPTSETUP.

Retrying. I believe my ticket was closed prematurely.

mercedes508 6 days ago

Comment

Actually we decided to move away from TrueCrypt for several reasons:

https://tails.boum.org/blueprint/replace_truecrypt/
https://tails.boum.org/doc/encryption_and_privacy/truecrypt/
https://tails.boum.org/support/faq/#index36h2

So we probably won’t be doing effort to support TrueCrypt more than what we do now in Tails.

My response:

I think I have been misunderstood. I was suggesting that a GUI be created to allow users to open encrypted containers. A simple UI that translates command line options into something graphical. Many novice users use both tails and encryption. Making it easy for them to open their drives or containers would improve usability regardless of what program they used to create them. As we both know, cryptsetup is able to open luks, truecrypt, veracrypt, and likely many other containers. This isn’t direct support for true or veracrypt. It is support for simplifying what cryptsetup is already capable of. Just because you create a checkbox that informs cryptsetup of the target container type doesn’t tell users to use true/veracrypt. It just means cryptsetup can open it. Users should spend as little time in terminal as possible. Such would only allow the initiated to benefit from the inclusion of cryptsetup. IMO tails and encryption go hand in hand. It would be unwise for a technical novice to be forced (due to difficulty opening containers via terminal) to carry around unencrypted sensitive data just to able to leak them using tails. Not cool.

Related issues

• Is duplicate of #11021 (closed)
• Is duplicate of #6337 (closed)

Original created by @Tonda on 11069 (Redmine)