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 .. 32 33 34 35 36 37 38 39 40 41 42 .. 77 Next › Last »

Plexcon commented on 2017-04-26 09:15 (UTC)

Actualización 6.5.2-1, please.

grufo commented on 2017-04-24 23:57 (UTC)

@TrialnError Thanks! I think now it should be fine. Could you please have a look at the PKGBUILD?

TrialnError commented on 2017-04-24 17:36 (UTC)

No? Those releases are signed with a pgp key (therefore the validpgpkeys entry). The filename itself is the same + an added .sig/.asc (see https://gist.github.com/Narrat/0fc7efa2db50309201640c8261551eed#file-01_32bit_build-patch-L93 ). If the checksum entry is set to SKIP (as it is usually done for sigfiles), it would download the source and its respective signature file and use the validpgpkeys entry to check if the downloaded file is valid (you only need this key in your local gnupg keyring, else it will fail with an error message). No need to keep a massive source/checksum entry?

grufo commented on 2017-04-23 21:55 (UTC)

@TrialnError Thanks for your contribution. Now I added both architectures (32 and 64 bit). The problem with signatures however is that this is a language-agnostic PKGBUILD, and therefore there would be needed as many signatures as the languages are, or am I wrong?

TrialnError commented on 2017-04-10 22:50 (UTC)

My proposal for changes would look like this https://gist.github.com/Narrat/0fc7efa2db50309201640c8261551eed

grufo commented on 2017-04-10 19:36 (UTC)

@TrialnError > Still imo the source check via the provided signature files should be done + providing the 32bit version. Yes, you are right about nearly all your points. I released this PKGBUILD after seeing the mess with the language specific packages, and based the PKGBUILD on one of them in order to simplify the mess. The real problem is that I don't have time for writing down an array of md5sums + dealing with the signature files. But if you want to help I will be happy to use your contributions!

TrialnError commented on 2017-04-10 00:56 (UTC) (edited on 2017-04-10 01:26 (UTC) by TrialnError)

What does it make different from tor-browser-bin? In general? Imo the naming scheme isn't fitting, as this is still the binary version and not compiled from source. And with the use of architecture specific PKGBUILD variables (source_i686, noextract_i686 and else) it could also provide the i686 version. Another point is the signature checking you mention in the pre_install section of the install file. Those key-ids could be added to the PKGBUILD (validpgpkeys) and the respective signature files to the source, to do the checking while creating the package (and removing the pre_install comment) Edit: What a mess with the tor-browser packages. Didn't saw the language specific versions. And tor-browser-bin has its own problems. I see now, this is a case of one PKGBUILD for all (like the descriptions states). Still imo the source check via the provided signature files should be done + providing the 32bit version.

Plexcon commented on 2017-04-02 15:52 (UTC)

Muchas gracias por la actualización. "tor-browser-linux64-6.5.1_es-ES.tar.xz ... HA FALLADO (clave pública desconocida D1483FA6C3C07136) ==> ERROR: ¡Una o más firmas PGP no pudieron ser verificadas!" Instalado correctamente gracias a la key que menciona Bitl0rd: gpg --recv-keys 2E1AC68ED40814E0 Poner en terminal antes de instalar

« First ‹ Previous 1 .. 32 33 34 35 36 37 38 39 40 41 42 .. 77 Next › Last »