Package Details: tor-browser-en 8.0.6-1

Git Clone URL: (read-only)
Package Base: tor-browser-en
Description: Tor Browser Bundle: anonymous browsing using Firefox and Tor
Upstream URL:
Keywords: tor
Licenses: GPL
Submitter: Maxr
Maintainer: yar (jugs)
Last Packager: jugs
Votes: 719
Popularity: 3.474890
First Submitted: 2011-10-14 19:30
Last Updated: 2019-02-13 01:03

Pinned Comments

yar commented on 2017-01-25 09:14

Before running makepkg, you must do this:

gpg --keyserver --recv-keys EB774491D9FF06E2

See below for details.

Latest Comments

1 2 3 4 5 6 ... Next › Last »

iyanmv commented on 2019-02-04 17:10

@yar @jugs: It would be nice if you could answer to @caleb and @nTia89 questions. I also don't understand the reason to use three different hashes so iff there is one, I'd love to know it. Otherwise, just delete the extra hashes.

r381581 commented on 2019-01-29 10:36

tor-browser 8 is based on firefox60, which uses the Photon UI and is gtk3+ only. For me, tor-browser works fine without gtk2 installed. So, the gtk2 dependency should be removed and a gtk3 dependency added.

yar commented on 2018-11-17 18:30

@l0b0 it's a git repo, so just mirror it somewhere and ask me to pull from it :)

l0b0 commented on 2018-11-16 08:40

I'd like to fix some shellcheck issues in How do I submit a patch to a file which is not part of upstream?

kevung commented on 2018-10-26 14:53

Hello everybody, I have the same issue as "zilvervos commented on 2018-03-19 16:02" when I try yaourt -S tor-browser:

% Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 curl: (51) SSL: no alternative certificate subject name matches target host name '' ==> ERREUR : Erreur lors du téléchargement de Abandon… ==> ERREUR : Makepkg n'a pas pu construire tor-browser. ==> Relancer la compilation de tor-browser ? [o/N] ==> ----------------------------------------------

I tried to replace 8.0.3 into in PKGBUILD without success. I did also gpg --keyserver --recv-keys EB774491D9FF06E2 as adviced by yar.

Does anybody encounter the same issue? Take care

eguillot commented on 2018-09-17 09:54

[newbie comment] add the key as simple user, not for the root user (no sudo...) The command that finally worked for me: $ gpg --recv-keys EB774491D9FF06E2 (no need to specify the key server)

yar commented on 2018-09-06 16:57

An updated history of relevant keys for my own benefit (and maybe others):

1) 8738A680B84B3031A630F2DB:416F0610:63FEE659 Erinn Clark's personal key - 4.0.3 [2015-01-14] and earlier were signed by this

2) EF6E286DDA85EA2A4BA7DE68:4E2C6E87:93298290 A master key created on 2014-12-15 for the purpose of signing other Tor Browser Developer keys

3) BA1EE421BBB45263180E1FC7:2E1AC68E:D40814E0 signed by #2, 4.0.4 [2015-02-25] through 6.0.8 [2016-12-13] were signed by this

4) A4300A6BC93C0877A4451486:D1483FA6:C3C07136 signed by #2, 6.5 [2017-01-24] through 7.5.6 [2018-06-26] were signed by this

5) 110775B5D101FB36BC6C911B:EB774491:D9FF06E2 signed by #2, 8.0 [2018-09-05] is signed by this

jugs commented on 2018-09-05 17:41

New signing key for 8.0+:

gpg --keyserver --recv-keys 0x4E2C6E8793298290

See the torproject blog post regarding the 8.0 release for key info.

caleb commented on 2018-07-07 11:00

I seriously came here to ask the same thing as @nTia89 — what is the deal with using three hash functions? This is just silly antics that make it harder to manage manually, clutter the diff history, and all without providing any benefit. One of the SHA mechanisms is sufficient, if that doesn't completely solve the problem adding another one is not going to solve the problem, much less adding MD5. Please revert 5df1ca8a986e and use just GPG signature validation plus one set of SHA512 checksums.

nTia89 commented on 2018-06-24 10:26

@yar Why do you use three hash functions (md5sums, sha256sums and sha512sums)?