Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • C Collector
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • 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
  • The Tor Project
  • Network Health
  • Metrics
  • Collector
  • Issues
  • #20983
Closed
Open
Created Dec 15, 2016 by cypherpunks@cypherpunks

Stop sanitizing contact information from bridge descriptors

context: https://lists.torproject.org/pipermail/tor-dev/2016-December/011756.html

Why does CollecTor remove ContactInfo from bridge descriptors? Publishing the ContactInfo should not (directly) reveal the bridge location?

use-case for that data: bridge group detection

If plain publishing is not acceptable how about generating a random string replacement for a given ContactInfo string. https://lists.torproject.org/pipermail/tor-dev/2016-December/011761.html

That mapping contactInfo -> random id should remain static for at least 24 hours.

Assignee
Assign to
Time tracking