Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S Snowflake
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 70
    • Issues 70
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Anti-censorship
  • Pluggable Transports
  • Snowflake
  • Issues
  • #40122
Closed
Open
Created Apr 06, 2022 by David Fifield@dcfOwner3 of 5 tasks completed3/5 tasks

Set up a second snowflake bridge site

At #28651, the plan is to run more than one snowflake bridge site. Each bridge site will have one instance of snowflake-server, speaking to a group of tor instances that all have the same identity keys. The identity keys in different bridge sites will be different. Until now, we have had only one bridge site, and have kept the tor identity keys the same through server migrations (#40091 (closed), #40095 (closed), #40110 (closed), #40111 (closed)). This issue is to set up a second bridge site, with its own, independent identity keys.

  • get access to the server hardware
  • decide on a bridge nickname
  • install bridge software (installation guide)
  • set up user accounts #40091 (comment 2768855)
  • point a domain name at the server #28651 (comment 2787394)

/cc @shelikhoo

Edited Apr 21, 2022 by David Fifield
Assignee
Assign to
Time tracking