I try to avoid changing more configuration than is absolutely necessary, especially in a browser that's built around the idea of sharing the same fingerprint for all users.
edit: nevermind, it doesn't seem to have any effect on the fingerprint. I'll push an update along with the next version.
Automatic updates can also be disabled by letting the browser know that it's managed by an external package manager. 13.5 added some checks for it, and IIUC it was also supposed to introduce a check for @/system-install (which has been created by this package from the beginning because it's needed for some other things), but it looks like nothing came of it.
Instead, they added a check for @/is-packaged-app. If you're feeling adventurous, run:
# touch /opt/mullvad-browser/is-packaged-app
and see if it helps. It works for me, so I'll test it for a couple more days and then push an update if nothing else breaks.
Pinned Comments
tarball commented on 2025-03-12 18:00 (UTC)
Please discuss bugs here before reporting them upstream, especially if they can't be reproduced with the original tarballs. Some bugs are caused by packaging issues and need to be fixed here. We can always escalate upstream if necessary.
tarball commented on 2024-06-26 08:35 (UTC)
Make sure to fetch the developers' signing key before building the package.
The official instructions are here. The link is also mentioned in the
PKGBUILD.If the site is blocked in your region, you'll have to work around it or trust me that this is what it says:
which (as of 2024-06-26) should also show this fingerprint:
If your gpg says otherwise, you may have been fed garbage.