Skip to content

GitLab

Last edited by Cecylia Bocovich
Page history

BridgeDB Survival Guide

BridgeDB survival guide

SSH fingerprints:

  • 1024 SHA256:wDAIdh3zEKYYdQMLIHwR19spLPiKjVvRAmAoB6irnjs root@polyanthum (DSA)
  • 256 SHA256:ydK14UKPpV7sv5PdrLjczPSETUvXwb9gcYm+gZiYDzY root@polyanthum (ECDSA)
  • 256 SHA256:+ZMJU/Nidg9P89tiRWNEeSWa3wIpzzKCzOReAfzIrF0 root@polyanthum (ED25519)
  • 2048 SHA256:x8vgDvdkeSuz8Wa9idjFCR8mT61DGe8SVDYsUi0BpCQ root@polyanthum (RSA)

(Re)starting BridgeDB

  1. Log into BridgeDB's machine.
  2. Change to the BridgeDB user by running sudo -u bridgedb -s
  3. Kill the existing BridgeDB process by running kill $(pgrep -f /home/bridgedb/virtualenvs/bridgedb/bin/bridgedb)
  4. Start BridgeDB by running ~/bridgedb-admin/bin/run-bridgedb which should result in the following output: Starting BridgeDB... [OK].

Inspecting log files

BridgeDB's log file is located at /srv/bridges.torproject.org/log/bridgedb.log

Changing BridgeDB's configuration file

BridgeDB's configuration file (and admin scripts) is maintained in the bridgedb-admin repository. On polyanthum, BridgeDB's host, this repository is located at /srv/bridges.torproject.org/home/bridgedb-admin. and the configuration file is located at /srv/bridges.torproject.org/home/bridgedb-admin/etc/bridgedb.conf.

Deploying a new version of BridgeDB

BridgeDB is run from a local clone of the BridgeDB repository. Once a new version has been tagged and pushed to the repository it's ready to be deployed.

  1. Log into BridgeDB's machine
  2. Change to the BridgeDB user by running sudo -u bridgedb -s
  3. Checkout the version tag you want to deploy 
    git fetch origin
git checkout bridgedb-0.x.y
  4. Kill the existing BridgeDB process by running kill $(pgrep -f /home/bridgedb/virtualenvs/bridgedb/bin/bridgedb)
  5. Reinstall BridgeDB by running ~/bridgedb-admin/bin/deploy-production. If rust is not available you might want to pass CRYPTOGRAPHY_DONT_BUILD_RUST=1 as environment variable to avoid python's cryptography library to use it.
  6. If BridgeDB fails to start, start BridgeDB by running ~/bridgedb-admin/bin/run-bridgedb which should result in the following output: Starting BridgeDB... [OK].

(Re)starting moat

See https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Survival-Guides/Moat-Survival-Guide

(Re)starting wolpertinger

The wolpertinger binary is also located in /srv/bridges.torproject.org/bin/. Its source code is available here. To restart wolpertinger, kill the existing process and then run the script run-wolpertinger located in /srv/bridges.torproject.org/bin/. To deploy a new binary, build it on your local machine and scp it onto polyanthum.