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 983
    • Issues 983
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 38
    • Merge requests 38
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • 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
  • #5362
Closed
Open
Issue created Jul 18, 2013 by import-from-Redmine@import-from-Redmine

Evaluate web fingerprint

Originally created by Tails on #5362 (Redmine)

Now that we use Torbrowser patches (#5798 (closed)), we can reconsider the browser fingerprinting issue.

We should evaluate the Tails web browser fingerprint.

  • Extensions: FoxyProxy, Cookie Monster, You tube video downloader, download manager (not implemented yet), Adblock.
  • Would we be ready to stick to or synchronize our add-ons with Torbrowser? (e.g Adblock is useful)
  • "Tor Browser disabling Javascript anonymity set reduction" thread on tor-talk

team: jvoisin, spriver?

Related issues

  • Related to #5706 (closed)
Edited May 15, 2020 by import-from-Redmine
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking