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

Closed (moved)
Open
Opened Dec 14, 2018 by Alexander Færøy@ahf🍍Developer

Document Snowflake broker implementation

We should document how the current Snowflake implementation distributes Snowflake proxies to clients that is in need of them.

Once we have specified how the current implementation works, we should figure out if there are things we would like to change before we can start shipping Snowflake in an alpha state to users.

  1. Look at broker code in the Snowflake repository.
  2. Document current behavior with long-polling clients waiting to get handed a proxy.
  3. Let's discuss if this design have any weaknesses we would like to address.

One weakness here could be that currently the broker nor client DOES NOT pass information about which bridge/relay to connect to, but this bridge/relay host is hardcoded in both the Go and JS proxy code.

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