Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
T
tails
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 967
    • Issues 967
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 21
    • Merge Requests 21
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #12428

Closed
Open
Opened Apr 05, 2017 by intrigeri@intrigeriMaintainer

Ensure disk caches and aufs read-write branch are emptied during emergency shutdown

Originally created by @intrigeri on #12428 (Redmine)

… so that they are overwritten by kernel memory poisoning. “Emergency” shutdown = when one unplugs the boot device.

This needs to be done in a way that’s as reliable as possible: in particular, the storage medium may host the persistent filesystem. If unmounting doesn’t work well enough (or just as an additional safeguard), we should probably echo 3 > /proc/sys/vm/drop_caches at some point during the shutdown process.

Writing an automated test for the “Tails with persistent volume unlocked” and “aufs read-write branch” usecases would help confirming it actually works. It probably requires implementing a /lib/systemd/system-shutdown/ hook that pauses for a while when debug=wipemem is passed on the kernel command line, so that we can dump memory after we’ve tried unmounting the filesystems.

Feature Branch: bugfix/12354-drop-kexec-memory-wipe

Parent Task: #12354 (closed)

Edited May 15, 2020 by intrigeri
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tails_3.0~rc1
Milestone
Tails_3.0~rc1 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: tails/tails#12428