Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 938
    • Issues 938
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 27
    • Merge requests 27
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Model experiments
  • 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
  • #8156

Explain that failure of memory wipe is usually no big deal

Originally created by @sajolida on #8156 (Redmine)

We currently mention memory wipe in two places in our documentation:

  • https://tails.boum.org/doc/advanced_topics/cold_boot_attacks/
  • https://tails.boum.org/support/known_issues/#index20h2

Users are sometimes confused by the notion of memory (RAM vs hard disc) and the notion of trace (which are ephemeral in the case of RAM). So we should make it clearer that: a failure of the memory wipe only mean leaving very ephemeral traces on the device and is no big deal is most cases.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking