|
|
## 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 by running `GITHUB_AUTH=$token ./scripts/update_github` where $token is a github authentication token generated for the github user account that hosts our GetTor repository.
|
|
|
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]` |
|
|
\ No newline at end of file |
|
|
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:
|
|
|
```e) Edit existing remote
|
|
|
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:
|
|
|
```Already have a token - refresh?
|
|
|
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. |
|
|
\ No newline at end of file |