Project

General

Profile

Bug #17474

opening a Veracrypt volume fails if the passphrase is too long

Added by goupille about 2 months ago. Updated 6 days ago.

Status:
In Progress
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
Due date:
% Done:

0%

Feature Branch:
Type of work:
Wait
Blueprint:
Starter:
Affected tool:

Description

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.

History

#1 Updated by segfault about 2 months ago

  • Status changed from New to Confirmed

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

#2 Updated by segfault about 1 month ago

  • 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 6 days ago

… 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).

\o/

Also available in: Atom PDF