Package Details: tor-browser-bin 14.0.3-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: jugs
Votes: 1280
Popularity: 0.98
First Submitted: 2023-09-24 17:45 (UTC)
Last Updated: 2024-12-06 14:48 (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 .. 52 53 54 55 56 57 58 59 60 61 62 .. 77 Next › Last »

mudrii commented on 2015-01-05 11:54 (UTC)

No fix for the issue ?

palasso commented on 2015-01-02 09:58 (UTC)

@yar I did some cleanup in the PKGBUILD http://pastie.org/private/emg2wzh9whwhfn9jes89jq It doesn't use anymore _pkgarch, _realpkgver, _realpkgver_i686 and instead uses a new feature from pacman 4.2. I'm not sure what was the use of _realpkgver_i686. Also fixed indentation. I noticed that in tor-browser-en.sh, line 27: PKGARCH="REPL_ARCH" isn't being used anywhere. I also noticed that tor-browser-en.sh extracts the (installed from pacman) tar.xz from /opt/$pkgname to home at first run while there are rm -rf commands in $pkgname.install for when updating/removing. It's a hacky solution. Why isn't the extraction and packaging of files left on makepkg so that it'll be properly installed by pacman?

Marcel_K commented on 2015-01-01 23:17 (UTC)

Indeed. To be clear: the Arch Linux keyring and your local keyring have nothing in common, you should not add keys of AUR packages to the Arch keyring, unless you want to install packages signed by that user. When issuing makepkg, your local keyring is checked, not the Arch one.

blackhole commented on 2015-01-01 21:53 (UTC)

It seem solved now. I had to run gpg --recv-keys 0x63FEE659 as USER!

blackhole commented on 2015-01-01 21:48 (UTC)

I don'have a ~/.gnupg/gpg.conf. I have added it with "keyring /etc/pacman.d/gnupg/pubring.gpg" inside The output of gpg --list-keys /root/.gnupg/pubring.gpg ------------------------ pub rsa2048/63FEE659 2003-10-16 uid [ unknown] Erinn Clark <erinn@torproject.org> uid [ unknown] Erinn Clark <erinn@debian.org> uid [ unknown] Erinn Clark <erinn@double-helix.org> sub rsa2048/EB399FD7 2003-10-16 but I cannot install this package

kylebofh commented on 2015-01-01 21:43 (UTC)

Perfectly installed after issuing gpg --recv-keys 0x63FEE659 and adding the line keyring /etc/pacman.d/gnupg/pubring.gpg to ~/.gnupg/gpg.conf as Minbari mentioned earlier.

AnbuBlack commented on 2015-01-01 16:20 (UTC)

Do you have: keyring /etc/pacman.d/gnupg/pubring.gpg in ~/.gnupg/gpg.conf?! See more at: https://wiki.archlinux.org/index.php/Makepkg#Signature_checking

blackhole commented on 2015-01-01 15:01 (UTC)

Not in my case

AnbuBlack commented on 2015-01-01 12:55 (UTC)

gpg --recv-keys 0x63FEE659 - Solve the problem.

« First ‹ Previous 1 .. 52 53 54 55 56 57 58 59 60 61 62 .. 77 Next › Last »