Package Details: mullvad-browser-bin 13.0.14-1

Git Clone URL: https://aur.archlinux.org/mullvad-browser-bin.git (read-only, click to copy)
Package Base: mullvad-browser-bin
Description: Privacy-focused web browser developed by Mullvad VPN and the Tor Project
Upstream URL: https://mullvad.net/en/browser
Keywords: browser firefox mullvad privacy private
Licenses: MPL-2.0, GPL-3.0-or-later
Conflicts: mullvad-browser
Provides: mullvad-browser
Submitter: tarball
Maintainer: tarball
Last Packager: tarball
Votes: 27
Popularity: 4.50
First Submitted: 2023-04-03 14:58 (UTC)
Last Updated: 2024-04-16 17:48 (UTC)

Dependencies (14)

Required by (0)

Sources (4)

Latest Comments

1 2 3 Next › Last »

pospeselr commented on 2024-04-15 17:42 (UTC)

(Presuming updating mullvad-browser is left up to Arch's package manager and not the browser's self updater)

You all may be interested in following https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/41083 and its associated issues and MRs. With respect to ignoring the updater, the 'right' way to do this is to add a particular file in the install directory. See this comment for specifics: - https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42482#note_3019228

This will be the supported way for downstream packagers to disable the updater and manage their own updates from the 13.5 series on.

tarball commented on 2024-04-15 17:36 (UTC) (edited on 2024-04-15 17:46 (UTC) by tarball)

edit: looks like system-install will be enough pretty soon, see @pospeselr's comment for more info. That file is already being created by the PKGBUILD.


Thanks, I'll look into that shortly and add it if it helps.

The usual place for this is policies.json (see this nix config for an example), but I tried that (along with all the other options that have any relation to updates) and it didn't make any difference.

deron commented on 2024-04-15 17:30 (UTC) (edited on 2024-04-15 17:30 (UTC) by deron)

Disabling auto-updates (about:config > app.update.auto) fixed the UpdateInfo issue for me (so far).

texer22 commented on 2024-02-29 10:44 (UTC) (edited on 2024-02-29 10:45 (UTC) by texer22)

After an update it does not update the file in /user/UpdateInfo/updates/.. It still shows "pending". https://github.com/mullvad/mullvad-browser/issues/229 "@foter @Giger22 Please note that the packages from the aur are community provided, and we don't offer support for it.

Could you please contact the mullvad-browser-bin maintainer and pass your comments directly to them?"

tarball commented on 2024-01-19 16:26 (UTC) (edited on 2024-01-23 15:55 (UTC) by tarball)

edit: GitHub releases lag behind the official CDN for about an hour, but I think it's worth it to cover the less fortunate among us (myself included).


Hmm... the browser targets the privacy-conscious audience which might not appreciate sending their requests to Microsoft.

I've been having the same problem actually, so I understand your pain completely. Mullvad's servers are partially blocked and the rest is throttled here for providing a VPN service, which forces me to use a (trusted) proxy.

Let's see if anyone else cares enough to vote for or against this.

If not, I'll probably change the URL when 13.0.9 is released (which is likely to happen in a couple of days).

The binary is signed anyway.

rearwindowtaxidr commented on 2024-01-19 16:13 (UTC)

Could you please change the source URL to GitHub? The cdn.mullvad.net server is very poor and downloading from East Asia always fails.

<deleted-account> commented on 2023-11-06 11:28 (UTC)

When I download the source tarball with paru, it always fails with a timeout; when I download it with Firefox, it succeeds. Is this a problem with curl options?

PortableAlgebra commented on 2023-07-10 07:48 (UTC)

If you're getting the PGP/GPG error, just refer directly to Mullvad's website for the command to run for the current signing key. Slug's comment is probably fine too, but I prefer using the method from Mullvad.

https://mullvad.net/en/help/verifying-mullvad-browser-signature/

Download the Tor Browser Developers signing key

The fingerprint of the code signing key is EF6E 286D DA85 EA2A 4BA7 DE68 4E2C 6E87 9329 8290 and it can be downloaded from TOR:

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

Slug commented on 2023-06-22 16:30 (UTC) (edited on 2023-06-22 16:32 (UTC) by Slug)

I had a problem with a missing public PGP key ; trying to import it failed. It was necessary to specify a server to import the key.

I was recommended the following line to be able to import it :

gpg --keyserver hkps://keys.openpgp.org --recv-keys E53D989A9E2D47BF  ✔

gpg: key 4E2C6E8793298290: public key "Tor Browser Developers (signing key) torbrowser@torproject.org" imported

gpg: Total number processed: 1

gpg: imported: 1

ZorinArch commented on 2023-04-25 04:37 (UTC)

@kaivai thank you, i fix that issue.