Package Details: tor-browser-bin 14.0.2-1

Git Clone URL: https://aur.archlinux.org/tor-browser-bin.git (read-only, click to copy)
Package Base: tor-browser-bin
Description: Tor Browser Bundle: anonymous browsing using Firefox and Tor
Upstream URL: https://www.torproject.org/projects/torbrowser.html
Licenses: MPL-2.0
Conflicts: tor-browser
Provides: tor-browser
Submitter: FabioLolix
Maintainer: grufo (jugs)
Last Packager: grufo
Votes: 1282
Popularity: 1.91
First Submitted: 2023-09-24 17:45 (UTC)
Last Updated: 2024-11-17 05:13 (UTC)

Pinned Comments

grufo commented on 2019-08-15 02:22 (UTC)

Before running makepkg, you must do this (as normal user):

$ gpg --auto-key-locate nodefault,wkd --locate-keys torbrowser@torproject.org

If you want to update tor-browser from AUR without AUR helpers you can run in a terminal:

$ tor-browser -u

Latest Comments

« First ‹ Previous 1 .. 37 38 39 40 41 42 43 44 45 46 47 .. 77 Next › Last »

yar commented on 2016-11-16 02:12 (UTC)

Calling gpg from the build script would be a careless hack at best. makepkg should have better error messages and AUR should recognize the validpgpkeys value and give clear instructions when it's non-empty. Ideally every package should be using validpgpkeys and every user should know how to handle it.

aereaux commented on 2016-11-15 23:27 (UTC)

@jugs @itsme, I definitely think it's a bad idea to do that. I don't want a script adding keys to my keyring, that should be an action I do deliberately myself.

jugs commented on 2016-11-15 23:21 (UTC)

@itsme, I'm not sure if we should automate the key retrieval, what do you think @yar?

itsme commented on 2016-11-15 17:30 (UTC)

please, add 'gpg --keyserver pool.sks-keyservers.net --recv-keys 2E1AC68ED40814E0' to PKGBUILD

pille1842 commented on 2016-10-27 15:54 (UTC)

lino16, you need to import the PGP key first, then sign it locally. Run this command: gpg --recv-keys 93298290 You can find this key ID here: https://www.torproject.org/docs/signing-keys.html.en After that, run: gpg --edit-key 93298290 And enter: lsign Then save it with: save After that, you can install the package.

lino16 commented on 2016-10-09 20:46 (UTC) (edited on 2016-10-09 20:51 (UTC) by lino16)

tor-browser-linux64-6.0.5_de.tar.xz ... FEHLGESCHLAGEN (Unbekannter öffentlicher Schlüssel 2E1AC68ED40814E0) ==> FEHLER: Eine oder mehrere PGP-Signaturen konnten nicht überprüft werden! ==> FEHLER:Makepkg konnte tor-browser-de nicht erstellen. I have imported key by: gpg --keyserver keys.gnupg.net --recv-keys 2E1AC68ED40814E0 This is the message now: tor-browser-linux64-6.0.5_de.tar.xz ... FEHLGESCHLAGEN ==> FEHLER: Eine oder mehrere PGP-Signaturen konnten nicht überprüft werden! ==> FEHLER:Makepkg konnte tor-browser-de nicht erstellen.

HeavyRain commented on 2016-09-30 21:06 (UTC)

Sorry for the delay in updating to version 6.0.5!

choman commented on 2016-09-19 19:29 (UTC)

if files do not exist in the update and restore functions; such as search.json the copy errors out and the script exits. recommend a "|| :" after the cp commands or a file exist check prior to cp.

ewtoombs commented on 2016-09-19 09:11 (UTC) (edited on 2016-09-19 09:13 (UTC) by ewtoombs)

Also, I just tested tor-browser-en on arguments with spaces, and it seems to have been fixed, which is what the bug report claims as well. Our script's help text should probably be modified accordingly.

ewtoombs commented on 2016-09-19 09:02 (UTC)

I found a problem. The package's tor-browser-hardened.sh isn't passing the arguments to Browser/start-tor-browser right. This line is the problem: cd $INSTALL_DIRECTORY/Browser && ./start-tor-browser --class Tor\ Browser "${args[@]}" start-tor-browser stops processing switches at the first unknown switch, which is --class, which was meant for firefox. This fixes that problem: cd $INSTALL_DIRECTORY/Browser && ./start-tor-browser "${args[@]}" --class Tor\ Browser That got the tor switches working again, particularly --verbose / --debug. If for some reason --class needs to come before the user-specified firefox arguments, you'll still have a problem with my fix. I just tested it on a URL, though, and it seems to work ok.