Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
rdsys
rdsys
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 16
    • Issues 16
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • 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.

  • The Tor Project
  • Anti-censorship
  • rdsysrdsys
  • Issues
  • #1

Closed
Open
Opened Sep 26, 2019 by Philipp Winter@phwMaintainer

Implement the Salmon bridge distribution mechanism

BridgeDB currently has three bridge distribution mechanisms: Email, HTTPS, and moat. Email is problematic because its interaction mechanism is complicated, not everyone has a Gmail or Riseup address, and it's easy to crawl. HTTPS is problematic because bridges.torproject.org is blocked in most places that matter and our CAPTCHA is good at keeping out users (legacy/trac#29695 (moved)) but not so good at keeping out bots (legacy/trac#31252 (moved)). Moat remains relatively useful because it uses domain fronting but it also relies on a CAPTCHA to fight off bots.

It's time to think about new and/or significantly improved bridge distribution methods. How can we get bridges into the hands of users while making it difficult for adversaries to get them all? How can we make BridgeDB's CAPTCHA more resistant against bots and easier for users?

The Salmon bridge distribution system (first presented in a PETS'16 paper) is promising. Let's use this issue to build a prototype and fill in the missing pieces to get Salmon deployed.

Edited Jun 23, 2020 by Philipp Winter
Assignee
Assign to
Sponsor 30 - Objective 2.3
Milestone
Sponsor 30 - Objective 2.3
Assign milestone
Time tracking
None
Due date
None
Reference: tpo/anti-censorship/rdsys#1