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 944
    • Issues 944
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 13
    • Merge Requests 13
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • tails
  • tails
  • Issues
  • #17882

Closed
Open
Opened Aug 21, 2020 by sajolida@sajolidaMaintainer

Rewrite "Tails doesn't magically separate your different contextual identities"

As a start:

  • "contextual identities" sounds a bit like jargon to me.
    • Maybe our example in the 1st paragraph could be improved.
    • Maybe we could find a better title for this section.
    • Maybe we should talk about activitites that you really don't want to be related if things go bad.
  • "First, because Tor tends to reuse the same circuits, for example, within the same browsing session" could be improved.
    • Nowadays Tor Browser has top-level isolation: visits to different websites are forced to use different circuits.
    • We should either be more precise or drop this.
  • "browsing requests" is jargon.
  • "If you are facing a global adversary as described above, it might then also be in a position to do this correlation." is already covered elsewhere. See also #17869 (closed) for ongoing work.
  • "security hole" → "security vulnerability". See https://tails.boum.org/contribute/how/documentation/style_guide/#vulnerability.
  • "information about your session could be leaked": could we find an example to make this more clear?
  • "shutdown and restart Tails": That's not enough to protect from the second thread is the user has a Persistent Storage.
    • We should update the entire section to take into account the Persistent Storage: if people are using the Persistent Storage, they should have different Tails USB sticks for each identity or activity.
Edited Aug 25, 2020 by sajolida
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: tails/tails#17882