Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #5432

Closed
Open
Opened Mar 20, 2012 by Mike Perry@mikeperry

Improve Panic Button/provide Wipe Button to wipe files and recommend purging with fire

For the TBB Panic Button in #4107 (closed), we decided against extensive efforts to wipe the TBB directory because it would be exceedingly difficult to do it correctly in the face of all adversaries.

However, this doesn't mean that in the happy future, we shouldn't make some attempt to wipe the contents of the TBB dir.

In the face of risk/reward vs time spent on wiping, I think the following OS-agnostic protocol is optimal:

  1. Overwrite each file with ONE PASS of 0's or pseudorandom stream.
  2. Rename each file to pseudorandom name
  3. Rename each directory to pseudorandom name
  4. rm -rf .

For any situation that requires more effort or time than this, we should recommend fire and/or acid. Perhaps we should even tell the user they should consider fire as a backup measure in a nice dialog before or after the wipe is complete.

Otherwise, this should be sufficient to deter a low-funded adversary with access to Norton Utilities Unerase and the like.

This mode probably should be a different option than the Panic Button, because even one pass of zeroes or psuedorandom data will take a while. In some situations (such as those that would require a Panic Button) you might not have that luxury.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#5432