tor-browser.mdwn 1.49 KB
Newer Older
1
2
3
4
5
6
[[!meta title="Releasing the Tor Browser"]]

[[!toc levels=1]]

Have a look at

7
8
9
10
* https://archive.torproject.org/tor-package-archive/torbrowser/
* https://www.torproject.org/dist/torbrowser/
* https://people.torproject.org/~mikeperry/builds/
* https://people.torproject.org/~linus/builds/
11
12
13

and see if the desired version is available. We prefer
`archive.torproject.org` since the other sources periodically cleans
14
15
up old releases. Set `DIST_URL` to the chosen url, and set `VERSION`
to the desired TBB version, for example:
16

17
18
19
20
21
22
23
24
25
26
    DIST_URL=https://people.torproject.org/~mikeperry/builds/
    VERSION=4.0

Fetch the version's `sha256sums.txt` and `sha256sums.txt.asc` and
verify with `gpg`:

    wget ${DIST_URL}/${VERSION}/sha256sums.txt{,.asc} && \
    gpg --verify sha256sums.txt.asc

Filter the tarballs we want and make them available at build time,
Tails developers's avatar
Tails developers committed
27
when the tarballs are fetched:
28

29
30
    grep "\<tor-browser-linux32-.*\.tar.xz$" sha256sums.txt > \
         config/chroot_local-includes/usr/share/tails/tbb-sha256sums.txt
31

32
Then update the url to the one chosen above:
33

34
    echo "${DIST_URL}" | sed "s,^https://,http://," > \
35
36
37
38
39
40
         config/chroot_local-includes/usr/share/tails/tbb-dist-url.txt

NOTE: We must use http (not http**s**) due to limitations/bugs in
`apt-cacher-ng`, which often is used in Tails build
environments. However, it is of no consequence since we verify the
checksum file.
41
42
43

Lastly, commit:

Tails developers's avatar
Tails developers committed
44
    git commit config/chroot_local-includes/usr/share/tails/tbb-*.txt \
45
        -m "Upgrade TBB to ${VERSION}."