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
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

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

Closed (moved)
Open
Opened Aug 25, 2015 by proper@proper

allow Tor to parse bridge information copied and pasted verbatim from bridges.torproject.org

Currently bridges.torproject.org returns replies for copy and paste in the following form.

obfs4 ip:port fingerprint

This is easy for copied into tor-launcher. But one who wanted to copy this into its /etc/tor/torrc would have to modify it to.

Bridge obfs4 ip:port fingerprint

This is a usability issue. Therefore, could you make for example /etc/tor/torrc config option obfs4 a shortcut to Bridge obfs4 etc.?

Ideally, pluggable transports once they plugged into Tor using ClientTransportPlugin would be responsible for running the code for setting up these shortcuts themselves so you don't have to maintain a static/outdated list of shortcuts within the Tor core.

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