Skip to content

GitLab

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

  • The Tor Project
    • A
      Anti-censorship
  • GetTor Project
  • gettor
  • Wiki
  • Gettor Service Operator HowTo

Last edited by Philipp Winter Sep 17, 2020
Page history

Gettor Service Operator HowTo

Updating Tor Browser binaries

We aim to update the Tor Browser binaries distributed by GetTor as soon as a new version is available. This can be done by running a series of scripts to upload the new versions to each of our providers and update the database of links to these uploads that are distributed by our responders.

  1. Log into the GetTor machine
  2. Change to the GetTor user by running sudo -u gettor -s
  3. Upload the new binaries to Google Docs and Internet Archive by running ./scripts/update_files from the main gettor directory
  4. Upload the new binaries to Github and Gitlab by running GITHUB_AUTH=$github_token GITLAB_AUTH=$gitlab_token ./scripts/update_git where the provided tokens are authentication token generated for the github and gitlab user accounts, respectively, that host our GetTor repositories.
  5. Update the links in the gettor database by running ./scripts/export_stats

Starting and Restarting gettor

  1. Log into GetTor's machine
  2. Change to the GetTor user by running sudo -u gettor -s
  3. Run /home/gettor/gettor/bin/gettor_service [start|restart]

Troubleshooting issues

GetTor logs

All logs are located in the log directory on the GetTor host: /srv/gettor.torproject.org/home/gettor/log

Refreshing the rclone OAuth token

If in step (3) you receive error messages of the form: oauth2: cannot fetch token: 401 Unauthorized, you will need to refresh the OAuth token used by rclone to update the Google Docs distributor. To do so, run rclone config and answer the prompts as follows:

n) New remote
d) Delete remote
r) Rename remote
c) Copy remote
s) Set configuration password
q) Quit config
e/n/d/r/c/s/q> e
Choose a number from below, or type in an existing value
 1 > gdrive
remote> 1

answer n) No to all edit questions until you get to the prompt

y) Yes this is OK
e) Edit this remote
d) Delete this remote
y/e/d> y

You will then be prompted to refresh the token:

y) Yes
n) No
y/n> y
Use auto config?
 * Say Y if not sure
 * Say N if you are working on a remote or headless machine or Y didn't work
y) Yes
n) No
y/n> n

Follow the instructions and enter the verification code to refresh the token.

Clone repository
  • Gettor Service Operator HowTo
  • Home