Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 927
    • Issues 927
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 18
    • Merge requests 18
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #17474

Closed
Open
Created Feb 11, 2020 by goupille@goupille2 of 2 tasks completed2/2 tasks

opening a Veracrypt volume fails if the passphrase is too long

Originally created by @goupille on #17474 (Redmine)

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.

To-Do

  • Test that it's indeed fixed on Bullseye
    • suggestion: locally patch our test suite to use a long passphrase
  • Remove the doc about this problem
Edited Dec 10, 2021 by intrigeri
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking