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

Closed (moved)
Open
Opened Jul 05, 2011 by Damian Johnson@atagar

Move obsolete specs to attic/ subdirectory

The bridge spec [1] suggests that bridges have both... BridgeRelay 1 PublishServerDescriptor bridge

in their torrc. The second is pointless and, according to Roger and Robert, this spec is kinda obsolete:

18:41 < atagar> The 'BridgeRelay 1' and 'PublishServerDescriptor bridge' seems kinda redundant. The bridge spec says to use both but the man page entry for 'BridgeRelay' says... 18:41 < atagar> 'It mainly causes Tor to publish a server descriptor to the bridge database, rather than publishing a relay descriptor to the public directory authorities.' 18:41 < atagar> Is the former just an alias for the second? Is there a reason we suggest that both are used? 18:44 < rransom__> atagar: Use 'BridgeRelay 1'. 18:45 < rransom__> 'PublishServerDescriptor bridge' doesn't make a relay answer directory requests. 18:52 < atagar> thanks - we should change that in the spec 18:52 * atagar will submit a ticket when he's on a connection that doesn't have 40-second-per-character latency 21:57 < armadev> atagar: the bridge spec is not what you should look at to decide how to configure your bridge. it's obsolete in that respect. 21:57 < armadev> for example, you don't need to touch publishserverdescriptor. it will automatically do the right thing. 22:38 < atagar> armadev: you still want to set it to zero for a private bridge, right? 22:39 < rransom__> Yes. 22:40 < atagar> 'not what you should look at to decide how to configure your bridge' -> What is? Is the torrc setup for bridges in an faq? (after a quick search it seemed like the spec was the best description we had) 22:41 < rransom__> bridge-spec.txt is obsolete. 22:42 < atagar> we should lable it as such, then 22:42 < rransom__> https://www.torproject.org/docs/bridges is about how to configure a bridge.

We should correct the spec, label it as being obsolete, or remove it to avoid future confusion.

[1] https://gitweb.torproject.org/torspec.git?a=blob_plain;hb=HEAD;f=bridges-spec.txt

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