Bug #17474

opening a Veracrypt volume fails if the passphrase is too long

Added by goupille 2020-02-11 15:33:04 . Updated 2020-05-06 17:59:28 .

Target version:
Start date:
Due date:
% Done:


Feature Branch:
Type of work:

Affected tool:
Deliverable for:


A user reported that if a veracrypt volume is encrypted with a passphrase longer than 64 characters, it is not possible to open it in Tails. Given it is possible to create such volumes outside of Tails, If it is not fixable, the documentation should at least mention that problem.


Related issues

Blocks Tails - Feature #17247: Core work 2020Q1 → 2020Q2: Technical writing Confirmed


#1 Updated by segfault 2020-02-12 17:41:50

  • Status changed from New to Confirmed

Reproduced and reported upstream: https://gitlab.com/cryptsetup/cryptsetup/issues/532

#2 Updated by segfault 2020-02-18 11:10:56

  • Status changed from Confirmed to In Progress
  • Assignee deleted (segfault)
  • Target version set to Tails_5.0
  • Type of work changed from Research to Wait

The issue has now been fixed upstream in commit f18cd7ae813cb6732362956565cd1584aa4fe4e9, which should be included in the next cryptsetup release. The most recent version is 2.3.0, so once we get a cryptsetup > 2.3.0 via Debian repos, this will be fixed in Tails (I guess that will be Tails 5.0 based on Bullseye).

#3 Updated by intrigeri 2020-03-25 08:38:58

… and the cryptsetup 2.3.1 Release Notes read:

> * Support VeraCrypt 128 bytes passwords.
> VeraCrypt now allows passwords of maximal length 128 bytes
> (compared to legacy TrueCrypt where it was limited by 64 bytes).


#4 Updated by sajolida 2020-04-14 01:10:33

  • Status changed from In Progress to Needs Validation
  • Assignee set to cbrownstein
  • Target version changed from Tails_5.0 to Tails_4.6
  • Feature Branch set to web/17474-veracrypt-64-char-passphrase

@cbrownstein: This was super quick to document, so I added it to our view as well.

Here is a branch. Please have a look!

#5 Updated by sajolida 2020-04-14 01:17:04

  • blocks Feature #17247: Core work 2020Q1 → 2020Q2: Technical writing added

#6 Updated by cbrownstein 2020-04-15 19:44:17

  • Status changed from Needs Validation to In Progress
  • Assignee changed from cbrownstein to sajolida

Looks good!

#7 Updated by sajolida 2020-04-21 16:02:07

  • Status changed from In Progress to Resolved
  • Assignee deleted (sajolida)

@cbrownstein: Merged, thanks!

#8 Updated by sajolida 2020-05-06 17:59:28

  • Status changed from Resolved to Confirmed
  • Target version changed from Tails_4.6 to Tails_5.0

Documenting is not fixing. Let’s keep this ticket open until it’s actually fixed in 5.0.