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: 1281
Popularity: 1.97
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 .. 63 64 65 66 67 68 69 70 71 72 73 .. 77 Next › Last »

Maxr commented on 2013-08-10 06:20 (UTC)

In fact I consider the complete rewrite of ~/.tor-browser-en as a privacy feature. Nevertheless, I will have a look into this in two weeks after my vacation. The closing misbehaviour persists since AFAIK the start of this package. No idea why. I do not think it is really a problem. Feel free to investigate if you want to.

DaveCode commented on 2013-08-09 22:22 (UTC)

1. App closure is misbehaved - Vidalia stays open - fails to obey tor-browser-en/INSTALL/Docs/README-TorBrowserBundle "To exit, close Firefox. Vidalia will automatically clean up and exit." 2. Package updates wrongly overwrite customized torrc, vidalia.conf, and prefs.js (use *.pacnew for updated files). 3. To Boskote: Put it the other way. Personal keyrings are for personal keys. So dropping AUR keys in personal rings is wrong. There is vastly more justification/rationale to have AUR keys mixed with dev packager keys. I think we're just looking at a default situation that has fallen out of previous inertia. Nobody sat down and thought about it. Any dev intentions causing this situation should change -- I see none -- though I haven't looked beyond my last post. A keyring can serve more than one need. AUR/Arch packages are close relatives, neighbors; all their keys belong on the same ring. If devs want separation, then they should create an AUR keyring just for AUR packages, as they made a package keyring for official packages. Personally the amount of research needed to understand the matter tells me it's messed up. An experienced user should not need so much effort and I wasn't alone. Lastly, and most importantly, any AUR helper tool that installs non-passing packages defeats the entire purpose. Pacaur emits a warning, but still installs, unless your fingers are really quick with Ctrl-C. I don't know about others. - thanks -

ZaZam commented on 2013-08-07 14:13 (UTC)

Thanks Boskote. I got it working.

Maxr commented on 2013-08-07 08:17 (UTC)

Thanks for explanation. Just to clarify: It should be possible to use any browser with tor (providing you do the proxy configuration right). However, there are many ways to miss some important privacy/security related options when not using the builtin fixes provided by Torbutton (see https://www.torproject.org/torbutton/) which is only available within TBB, unfortunately.

Boskote commented on 2013-08-07 07:27 (UTC)

The tor project no longer supports using tor through any browser other than the tor browser bundle, including regular firefox (TBB uses a patched version of firefox ESR): https://www.torproject.org/docs/faq.html.en#TBBOtherBrowser The standalone tor and vidalia packages still exist "for use by experts and relay operators". ZaZam, you can use Tor Browser from the TBB with your already installed versions of tor and vidalia with a simple change to the ~/.tor-browser-en/INSTALL/start-tor-browser script: https://trac.torproject.org/projects/tor/wiki/doc/TorifyHOWTO/WebBrowsers#UseTorBrowserwithalocallyinstalledTorVidaliaNIXONLY However, as Maxr explained in his comment on 2012-03-11, the contents of ~/.tor-browser-en get rewritten with the first call of TBB after each update. So you may need to redo the change to the start-browser-script with every update of the package.

Maxr commented on 2013-08-07 06:30 (UTC)

The package is distributed by the tor team as is for all those who don't want to install 3 software packages and configure them to work together. If you do not need the whole package, why don't you just install firefox in addition to your tor setup?

ZaZam commented on 2013-08-06 21:09 (UTC)

Could this be made to use tor and vidalia packages from the Arch repository? I have those packages already installed for running a Tor relay. I don't see the point of having them installed twice. And I don't see why this all has to be in a single package.

Maxr commented on 2013-08-04 16:31 (UTC)

Thanks for the hint, .install file is up to date now (didn't bump pkgrel).

Boskote commented on 2013-08-03 05:26 (UTC)

Maxr, From what DaveCode is saying, I think the command in the pre_install message should be changed from "pacman-key -r <keyid>"to "gpg --recv-keys <keyid>". Because the default for makepkg is to use the ~/.gnupg keyring. DaveCode, I agreed with you until I read that the keyring for pacman-key is intended for signatures of Arch developers for official packages, which makes sense: https://bbs.archlinux.org/viewtopic.php?pid=1297793#p1297793 Verifying source signatures for AUR builds is really different. There should be better info on the AUR wiki page about possibly needing to use gpg --recv-keys <keyid> in order to verify signed source.

« First ‹ Previous 1 .. 63 64 65 66 67 68 69 70 71 72 73 .. 77 Next › Last »