| Git Clone URL: | https://aur.archlinux.org/mullvad-vpn-beta.git (read-only, click to copy) |
|---|---|
| Package Base: | mullvad-vpn-beta |
| Description: | The Mullvad VPN client app for desktop (beta channel) |
| Upstream URL: | https://www.mullvad.net |
| Licenses: | GPL-3.0-or-later |
| Conflicts: | mullvad-vpn |
| Provides: | mullvad-vpn |
| Submitter: | None |
| Maintainer: | yochananmarqos |
| Last Packager: | yochananmarqos |
| Votes: | 11 |
| Popularity: | 0.000923 |
| First Submitted: | 2019-08-09 21:46 (UTC) |
| Last Updated: | 2024-05-07 13:55 (UTC) |
Right, which brings me back to the question: is the only way of fixing this is to add my user to the wheel group? That feels like kinda beating the purpose and gives any process running as my user even greater privileges than now.
I'll have to check if I can run only the GUI in the wheel group.
@sdht0: Here's how @kubrick explained it:
By default, the mullvad management socket is opened to the world and any user or process on the system can issue commands to it. By setting this parameter, only users in the wheel group can control the mullvad daemon, in line with arch existing polices (ie polkit)
Sorry I should have started from the beginning. The GUI is unable to contact the daemon, likely for the same reason that $ mullvad status does not work (needs a sudo):
Error: Management interface error
Caused by: Management RPC server or client error
Caused by: transport error: error trying to connect: Permission denied (os error 13)
Caused by: error trying to connect: Permission denied (os error 13)
Caused by: Permission denied (os error 13)
The GUI's process user needs to be in the wheel/admin group as well, no?
@sdht0: It's only related to the system service, not the GUI.
After "restrict management socket access to wheel group", is there a recommended way to run the GUI except the obvious? Adding my user to wheel would enable other admin privileges that I'd prefer not to.
@SecT0uch: This is the beta channel which includes stable versions so one is always up to date. Besides, 2021.1 is identical to 2021-beta2, see the changelog.
@yochananmarqos Why changing the package from beta2 to stable ? This is quite misleading.
I didn't seem to have the DNS issue with the beta build before. I'll test with the previous PKGBUILD and report here.
EDIT: Never mind my comment, same isssue with the beta2
@AustinSHend: Thanks for the heads up. I've implemented the change.
@yochananmarqos and others: For the new mullvad-exclude binary, it needs to have its setuid permission bit changed per the conversation here: https://github.com/mullvad/mullvadvpn-app/issues/781#issuecomment-646032454
This will eventually also need to happen for the regular stable AURs and etc when the feature makes it there.
@Zeioth: I will only be using pre-release beta builds, not test builds. A new beta should be coming soon.
Pinned Comments
yochananmarqos commented on 2022-10-05 15:33 (UTC) (edited on 2022-11-13 19:21 (UTC) by yochananmarqos)
PSA: Upstream does not support building natively for ARM64, only cross-compiling. You can use
mullvad-vpn-beta-bininstead.yochananmarqos commented on 2019-12-07 17:44 (UTC) (edited on 2020-02-26 18:30 (UTC) by yochananmarqos)
--> ALWAYS DO A CLEAN BUILD <--
This package will verify the signature of the git tag. Developer keys are available here and instructions are here. See the PKGBUILD to determine which developer key you need.