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 .. 55 56 57 58 59 60 61 62 63 64 65 .. 77 Next › Last »

qwerty12 commented on 2014-08-29 13:07 (UTC)

Dirty hack that should allow you to keep the majority of your profile (bookmarks and extensions, at least) when updating: http://slexy.org/view/s2RQIMTuFp You'll need customizepkg-scripting installed (and an AUR helper that makes use of it). To those of you (if anyone) considering using this, it goes without saying that you'll possibly make yourself more identifiable by using a previous profile and extra extensions atop the TBB.

Marcel_K commented on 2014-07-31 17:56 (UTC)

Just add the public key to your private keyring, like so: $ gpg --recv-keys 416F061063FEE659

rbellamy commented on 2014-07-31 16:40 (UTC)

==> Verifying source file signatures with gpg... tor-browser-linux64-3.6.3_en-US.tar.xz ... FAILED (unknown public key 416F061063FEE659)

odp commented on 2014-07-22 10:29 (UTC)

#makepkg Verifying source file signatures with gpg... tor-browser-linux64-3.6.2_en-US.tar.xz ... FAILED (unknown public key 416F061063FEE659) ==> WARNING: Warnings have occurred while verifying the signatures. Please make sure you really trust them. #sudo pacman -U tor-browser-linux64-3.6.2_en-US.tar.xz loading packages... error: missing package metadata in tor-browser-linux64-3.6.2_en-US.tar.xz error: 'tor-browser-linux64-3.6.2_en-US.tar.xz': invalid or corrupted package

<deleted-account> commented on 2014-06-16 19:47 (UTC)

Hi Mélodie, First of all, I’m deeply sorry to answer this late, your message went to my spam folder for an unknown reason… Actually, this is a really good question. The signature is not checked this way for tor-browsers packages, please read this very interesting page coming from TorProject website: https://www.torproject.org/docs/verifying-signatures.html.en So as you can see, signatures are provided in ".asc" file, but this is not the way security is ensured by the PKGBUILD. Here, Tor Browser is controlled via its sha256sum (https://www.torproject.org/docs/verifying-signatures.html.en#BuildVerification) Sha256sum are found there: https://www.torproject.org/dist/torbrowser/ (click on the version you want - at this moment, "3.6.2" - , then on "sha256sums.txt") Then, your humble servant copy/paste them to the PKGBUILD, run the program "mkaurball" and submit it to AUR. For your namcap's remarks: - "any" isn’t right here: you can only have 32 or 64 bit package on tor website, - we do not want to update MIME types' database for tor-browser, - same as previous answer. I hope I've clearly answered your questions. Regards, acaccia

melodie commented on 2014-06-14 12:01 (UTC)

Hi, I get: "==> Verifying source file signatures with gpg... tor-browser-linux64-3.6.2_fr.tar.xz ... FAILED (unknown public key 416F061063FEE659) " It seems this message has not appeared in the comments since a while. What can I do to fix it? Else, the namcap check command shows: ***** tor-browser-fr W: No ELF files and not an "any" package tor-browser-fr E: Mime type handler found. Add "update-desktop-database -q" to the install file tor-browser-fr E: Dependency desktop-file-utils detected and not included (needed for update-desktop-database) ***** I'll be waiting for answers here, especially regarding the unknown public key message. Regards, Mélodie

deusstultus commented on 2014-06-11 18:36 (UTC)

The dependencies list is incomplete. Browser aspect requires additional libraries to be installed on the machine. From firefox (Note this is 30.0 not ESR on which TBB is built): http://www.mozilla.org/en-US/firefox/30.0/system-requirements/ I'm getting additional flags indicating dependencies as built on alsa, etc. as well, recommend cloning dependencies from extra/firefox package.

GordonGR commented on 2014-06-11 10:45 (UTC)

I'm sure there's a sense of the word “normal” that applies to such a situation. Somewhere… Thank you.