1 [[!meta title="Releasing the Tor Browser"]]
5 * <https://archive.torproject.org/tor-package-archive/torbrowser/>
6 * <https://www.torproject.org/dist/torbrowser/>
7 * <https://people.torproject.org/~mikeperry/builds/>
8 * <https://people.torproject.org/~linus/builds/>
10 and see if the desired version is available. We prefer
11 `archive.torproject.org` since the other sources periodically cleans
12 up old releases. Set `DIST_URL` to the chosen url, and set `VERSION`
13 to the desired TBB version, for example:
15 DIST_URL=https://people.torproject.org/~mikeperry/builds/
18 Fetch the version's `sha256sums.txt` and `sha256sums.txt.asc` and
21 wget ${DIST_URL}/${VERSION}/sha256sums.txt{,.asc} && \
22 gpg --verify sha256sums.txt.asc sha256sums.txt
24 Filter the tarballs we want and make them available at build time,
25 when the tarballs are fetched:
27 grep --color=never "\<tor-browser-linux32-.*\.tar.xz$" sha256sums.txt > \
28 config/chroot_local-includes/usr/share/tails/tbb-sha256sums.txt
30 Then update the url to the one chosen above:
32 echo "${DIST_URL}" | sed "s,^https://,http://," > \
33 config/chroot_local-includes/usr/share/tails/tbb-dist-url.txt
35 NOTE: We must use http (not http**s**) due to limitations/bugs in
36 `apt-cacher-ng`, which often is used in Tails build
37 environments. However, it is of no consequence since we verify the
42 git commit config/chroot_local-includes/usr/share/tails/tbb-*.txt \
43 -m "Upgrade TBB to ${VERSION}."