Skip to content
GitLab
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 971
    • Issues 971
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 26
    • Merge requests 26
  • 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
  • #6621
Closed
Open
Issue created Jan 21, 2014 by Ghost User@ghost0 of 1 checklist item completed0/1 checklist item

Allow creating persistent volume onto a separate device

Originally created by @porcino999 on #6621 (Redmine)

For added plausible deniability I suggest adding the option of being able to install the persistent volume on a separate device other than the one running the OS.

This way Tails OS mass storage device 1 is physically different from Tails User Data mass storage 2. User data may be stored on easily concealable/disposable/hidable MicroSD card ; if properly concealed an oppponent cannot prove nor disprove whether Tails was used with or without persistent user data.

Boot sequence could look for external /home directory then revert to internal temporary /home if none are found.

Related issues

  • Blocked by #8935
Edited Sep 21, 2022 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