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

Closed (moved)
Open
Opened Jan 19, 2019 by Colin Childs@colin

Place complete obfs4 bridge line in accessible location

Currently operators wanting to distribute or use personal obfs4 bridges must follow 5 steps:

  1. Determine their bridge's IP address
  2. Check logs for their bridge's fingerprint
  3. Check logs for which port obfs4 is running on
  4. Retrieve their obfs4 cert from /var/lib/tor/pt_state/obfs4_bridgeline.txt
  5. String the above together in the following format:
Bridge obfs4 <IP ADDRESS>:<PORT> <FINGERPRINT> cert=$FROMSTEP4 iat-mode=0

This can be a confusing process, and is only fully explained upon opening /var/lib/tor/pt_state/obfs4_bridgeline.txt; however it leaves filling in the fields (with the exception of the cert) to the user.

Having the complete bridge line placed somewhere accessible would make this process much less painful for operators.

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