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
  • #8747

Closed (moved)
Open
Opened Apr 20, 2013 by Karsten Loesing@karsten

Add transports field to Onionoo's details documents

Bridges announce their pluggable transports in their extra-info descriptors. We scrub most of that information in the sanitizing process, but at least the transport names survive this process:

@type bridge-extra-info 1.2
extra-info ec2bridgercf30a0b4 7C86C0E30E2E267BB508B7B78A375D740E72B07D
[...]
dirreq-v3-tunneled-dl complete=0,timeout=0,running=0
transport obfs2
bridge-stats-end 2013-04-07 06:43:24 (86400 s)
[...]

Onionoo could add a new field transports to include transport names in its details documents. That would allow bridge operators to at least check whether their bridge announces the configured transports.

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#8747